Checking for updates doesn't always find the update

The downloaded *.wys file shouldn't be cached after an update is installed. I'll investigate this.

I am having the same issue now on my testing VM. I have installed multiple versions of the app and performed a few updates in the last week.

Now I have uninstalled everything and downloaded the latest released version of the app (1.21.1, 10 versions back) and I wanted to test if it updates correctly to the build I am going to publish (1.21.10). It keeps saying that I already have the latest version installed, which is not true.

Where is this information kept? How do I remove it?

NOTE: restarting the machine helped - the update is now found.

I would love to edit the previous post but can't so please excuse frequent posting.

Now the issue reappered on a different VM (this time WinXP, previously W7) and does not go away after restart.

I would love to edit the previous post but can't so please excuse frequent posting.

If you register in this forum you can edit your posts. Guest accounts aren't allowed to edit.

Now the issue reappered on a different VM (this time WinXP, previously W7) and does not go away after restart.

Can you reproduce this problem? We can't replicate it here.

To clear the cached data, delete the folder "C:\Users\YOUR USERNAME\wc". The "wc" folder is a system folder. Click Tools->Folder Options... then uncheck this checkbox to see the folder:

[attachment=0]Folder-Options.png[/attachment]

Also delete the folder "%appdata%\wyUpdate AU". It should also be hidden.

I have now debugged the issue using the wyUpdate source code to open the client.wyc files that were part of the deployment and found out that there was probably an error in my deployment script.

When I was initially testing wyBuild, I have created many versions up to 3.4.

Somehow the released 1.21.1 version had the client.wyc file from the testing 3.4 version.This is most probably an error in my build/deployment process....I guess the users will be stuck with their 1.21.1 (aka 3.4) unless I will publish something higher than 3.4. Or do I have another option to force them "downgrade" to 1.21.10?

Thanks for wyupdate being open source. Keep up the good work 🙂

...I guess the users will be stuck with their 1.21.1 (aka 3.4) unless I will publish something higher than 3.4. Or do I have another option to force them "downgrade" to 1.21.10?

You could get the users to download your installer and overwrite the installation. Or your next version could be 3.4.1.

Thanks for wyupdate being open source. Keep up the good work 🙂

It's our pleasure.

I've got a case with a customer that is running 2.0.1 of my software. This version is saying it's the latest version, but if he runs wyUpdate.exe, then it find the newest version which is 2.0.3.

This is on an extra machine, so there's no rush to update. What can we try or what files could we share with you that would help solve this problem?

Would sending you the cached files be helpful?

Yes, the cached files would be a help. But even better would be a step-by-step process of how to reproduce this problem.

I'm going to be digging around in the code to see if I can find any reason why it would keep stale cached files.

Did your user install 2.0.1 of your program over v2.0?

I am also having this issue.

Am i correct in saying that when i do a new version all i have to drag to my files folder in wybuild is my exe and the autoupdater.dll?

I am also having this issue.

Try updating by just double click wyUpdate.exe. Does it update, or is it also not finding the updates?

Am i correct in saying that when i do a new version all i have to drag to my files folder in wybuild is my exe and the autoupdater.dll?

Yes. And whatever additional resources and .dlls you have. See the FAQ about when you need to include the client.wyc within your updates.

Yes running wyupdate finds them no problem. Its just the auto update .net control that doesnt. I has worked but seems to have stopped now

Yes running wyupdate finds them no problem. Its just the auto update .net control that doesnt. I has worked but seems to have stopped now

Try clearing the cache files manually (see: viewtopic.php?f=1&t=275#p1054 ). Can you then reproduce the problem? (That is, step-by-step to get the AutomaticUpdater to stop finding the latest updates).

We are investigating this - we could get to the source of the problem quicker if we had an example.

Sorry I don't have a step-by-step solution. If I can come up with one, I'll let you know.

I've emailed you the cached files that were preventing the update, as once they were deleted the update worked as expected.

Thanks Dan. This will help us close in on the problem faster.