Message: wyUpdate ended before the current update step...

Let me ask you a few questions. If you run wyUpdate.exe alone, does it properly check & update? What's the version of wyUpdate.exe (right click, click properties, the click the details tab). Was the AutomaticUpdater & wyUpdate working before?

If I were to guess I would say this problem is caused because the "client.wyc" file isn't included with wyUpdate.exe. When you build wyUpdate make sure you include both the wyUpdate.exe and client.wyc files with your app.

Hello. I'm receiving the same exact error, under the same conditions.

I do have both the client.wyc and the wyUpdate.exe files in the same directory as my executable, but I'm getting the error anyway.

The version of wyBuild that we have is 2.6.14.0

It works just fine if I run wyUpdate.exe alone.

Thank you.

ps... I have tried the following advice, but the problem still persists.

I deleted all files and folders in the "%userprofile%\wc" also deleted all files and folders in the "%appdata%\wyUpdate AU" folder.

I tried running my app again.

There aren't any other instances of wyBuild, wyUpdate, or my app running.

Try setting the "wyUpdateLocation" property of the AutomaticUpdater to the explicit path your you wyUpdate executable. Tell me if this helps.

Hello and thank you for responding.

I put in the explicit path to wyUpdate.exe as suggested, but the same error occurs.

One thing I should note is that I have the following code in the Me_Load() method on a Visual Basic.NET form. And this form is the first form that's loaded:

If _wyUpdateAutomaticUpdaterComponent.ForceCheckForUpdate() Then _wyUpdateAutomaticUpdaterComponent.InstallNow() End If

The error occurs when it invokes the InstallNow() method.

Also, I'm using the .NET 4.0 version of the autoupdater component.

Ok, that code snippet is wrong. But this is a more common error than we'd like. The ForceCheckForUpdate() function does not return whether there's an update or not. What it returns is whether the checking has begun or not.

If you want the result -- i.e. whether there's an update or not -- then you should use the UpdateAvailable and UpToDate events.

That being said, it's almost always better to just use the "UpdateType" property set to UpdateType.Automatic and let the AutomaticUpdater handle the updating for you.

Thanks so much for the explanation!

As a developer, i want to *make sure* that the check for updates are happening each time the app is loaded, so it *felt better* to run that code (or something similar) each time the app is run.

Also, I want to force the update to happen, if there is one. I do not want the users to have the option of "skipping" an update. Will the Automatic setting of the UpdateType property force the update without allowing the user to opt out of it?

As a developer, i want to *make sure* that the check for updates are happening each time the app is loaded, so it *felt better* to run that code (or something similar) each time the app is run.

This is a bad idea. If a user starts your app 50 times a day, do you really need the user to check for updates 50 times? Will you be releasing a new version multiple times a day? Just use the "DaysBetweenChecks" property.

Also, I want to force the update to happen, if there is one. I do not want the users to have the option of "skipping" an update. Will the Automatic setting of the UpdateType property force the update without allowing the user to opt out of it?

By default there's no way for a user to opt-out of updates -- that is, the AutomaticUpdater does exactly what you want it to "out of the box". However, you should expose an option somewhere that mirrors the "UpdateType" property options.