Updating for 15 hoursSolved

Unfortunately this was a bug with wyUpdate when it self updated. Tell him to click cancel / quit. After wyUpdate has closed, tell him to open a cmd window (Click Start, type "cmd", press enter). Then have him paste in the following lines:

rmdir /s /q "%userprofile%\wc"rmdir /s /q "%appdata%\wyUpdate AU"

Then have him press the Enter key on his keyboard. This will delete the update cache folder (thus solving this unfortunate wyupdate bug).

After that he can re-run the update and it will succeed. I truly apologize for this problem. We should've caught it in our tests. We're making sure nothing like this happens again.

Is this correct?

Step 1: Cancel the Update.Step 2: Close the softwareStep 3: Click Start, type "cmd", press enterStep 4: Paste in the following rmdir /s /q "%userprofile%\wc"Step 5: Hit enterStep 6: Open up the software and re-run the updater.

Yes.

Ok...

I have sent these instructions and I am getting some similarreplies back.

Here is an example.-==========================Tried that - no joy.

Typing the stuff in to the cmd box did allow me to open up the software.

It then downloaded an update and said it would be installed next time the software was opened.

So I closed it down and re-opened it. Then it gave me the same problem as I orginally raised the ticket about. It stalls on extracting the files as per the attached screenshot.

What else can we try?==========================

You must make sure no wyUpdate instance is running when you do this. Tell them to restart their computer, and not start your software.

Them tell him to open a cmd window (Click Start, type "cmd", press enter). Then have him paste in the following line:

rmdir /s /q "%userprofile%\wc"rmdir /s /q "%appdata%\wyUpdate AU"

Then have him press the Enter key on his keyboard. This will delete the update cache folder (thus solving this unfortunate wyupdate bug).

Is this going to happen continually?

How do I prevent this from happening to future clients?

Michael

Is this going to happen continually?

No, this was a specific bug when a particular bad behaving old version of wyUpdate updated to wyUpdate 2.6.18.0. We've fixed the bug in wyUpdate 2.6.18.2 so that it can upgrade from bad behaving old versions of wyUpdate.

How do I prevent this from happening to future clients?

This particular problem won't happen to future clients. If they haven't got the problem they won't get it.

If you're talking about the possibility of other bugs in wyUpdate popping up in the future, then you have a couple of choices. You can continue to use our self-hosted version of wyUpdate (hosted on ours & google's servers) and know that we're all extremely embarassed by this bug and we're doing everything in our power to make sure nothing so stupid slips by our tests ever again.

The second choice is to host self-update on your own servers. That way you can deploy the new version of wyUpdate after we've done our testing and you've done your testing.