I've never seen this behavior and there's not enough information here to reproduce this problem. Does this error happen when you use our build of wyUpdate? If so, tell me how to reproduce it.
I have a custom built wyBuild (only so that it doesn't try to find updates on the internet) and an app with the automatic updater control. I deploy updates to the server, the user (non-admin) gets notice of that, and it downloads the updates, and tells them to restart the app to apply them.
When they restart, wyUpdate get stuck in a loop, apparently starting, launching another instance of itself, and closing. It's hard to tell or debug this since by the time you could attach or suspend the process, it's already terminated.
If that same user runs wyUpdate.exe directly, they're instructed, correctly, that they need admin privileges.
If I then run wyUpdate (remotely, over windows share), it updates the app and reports success.
Then that user still gets the 'loop' of wyBuild processes when they try to run my app again.
What might I be doing wrong here?
I've never seen this behavior and there's not enough information here to reproduce this problem. Does this error happen when you use our build of wyUpdate? If so, tell me how to reproduce it.
The problem is, I can't use your build of wyUpdate, as it hangs when trying to check for SelfUpdate. Our proxy isn't letting the request though and I don't recall if that it was a timeout issue or a the proxy's response confusing it.
I'm not sure how else I could explain the problem. What I'm doing now is I rebuilt wyUpdate to always return false from "NeedsElevation". (20 machines shared by 30 people, so I didn't want to install to UserDocuments folder)
If that fails, it's likely a strange GroupPolicy problem that I have no control over.
I'll report back what I find.