wyUpdate fails to update system32 files

I have an app that installs and uses several dll and (registered) ocx components in the windows system32 folder.

Under Windows 7 with UAC turned off, wyUpdate complains that access is denied and bombs.

Don't turn UAC off. wyUpdate is rightfully failing and rolling back an update when it can't access the files/folders and has no way to elevate the process.

You're backing wyUpdate into a corner with no options. Thus it shows an error. Don't back it into a corner.

The bigger problem here is that it then fails to relaunch my main app (which is set to get launched when the update completes which it never does) which leave my entire app belly up.

See the -startonerr="<filename>" commandline switch on how to start your app even if there's an error.

Wyatt,

Sorry to butt in on this thread, but the UAC portion interests me. Correct me if I'm wrong, but if UAC is disabled, then wyUpdate already has elevated access it wants (assuming the user account has the proper privileges) but the user has no way of preventing the the elevated operations (ala "No" to the UAC prompt).

Doesn't UAC only prevent elevated operations from taking place if it's enabled, and not provide the user with elevated privileges their user account doesn't have. If the user running wyUpdate doesn't already have administrative privileges, UAC won't allow them to elevate themselves to something they don't have, will it?

Again, I may very well me 100% misunderstanding UAC, which is why I'm asking. The answer is important to projects I'm working on going forward.

Thanks!

I agree...with UAC off it should have no problem.

If UAC is on, I have my app prompt before launching wyUpdate to actually do the update (assuming it will get tripped up if it does) but if UAC is off, I expect it to have no problems.

System files might be in use no doubt, but it needs to be smart enough to know how to get the job done (i.e require reboot if necessary). Not positive this is the problem but it sure smells like it.

I will implement the start on error option for sure...at least then it won't leave the entire system belly up.

Let me know about the UAC thing....it just doesn't seem right at all.