PROBLEM: I have a “Launch EXE with working folder” custom action for uninstall. When an admin user goes to control panel | Programs and Features and tries to uninstall my application, the uninstall tries to run my exe, but fails with Access Denied. I grabbed a procmon trace when this occurs and msiexec is trying to execute my exe but fails with ACCESS DENIED.
DETAILS:
In my custom action originally the “Execution Time” setting was “Immediately”, and thus the “Execution Options” setting for “Run under the LocalSystem account with full privileges (no impersonation)” was grayed out. So, impersonation was expected I guess. This caused the uninstaller to fail with access denied.
But, following the suggestions I have seen for other folks with this problem I changed the “Execution Time” to “When the system is being modified (deferred)” and selected the “Run under the LocalSystem account with full privileges (no impersonation)” option under “Execution Options”
“Wait for custom action to finish before proceeding” was checked under “Execution Options” in both cases. Using these new settings I tried again and captured the uninstall with procmon. Msiexec is still trying to impersonate and still fails with ACCESS DENIED?? I have tried this several times to make sure I have everything set the way I expect.
It would be fine if it tried to elevate, as my user on this machine is an administrator. But, it doesn’t try to elevate or whatever to get past the UAC, and it still impersonates even though I set it not to?
One other point: My custom action for uninstall is in the "Install Execution Stage".
How can I get the installer to stop impersonating or otherwise use the correct privs?
Any help would be appreciated!!
FOLLOW US
Get the latest news in Application Packaging