I want to update my software without elevation, and then run my software as a standard user. I followed the directions to "How to handle updates without elevation?" so that I can update my software without any UAC prompts. I then want to restart my software after the update as a standard user, but it was restarting as the "Local System" user because the "Local System" user is the account that runs the updater service (making my software not visible). I read that the RunAsUser command can not be called from the Local System account.
To get it working properly I had to add a custom action to call a ".NET Installer Class action" that would use a WMI query to find the user that is logged-in, and then add a task to Task Scheduler (as the logged-in user) that runs once (right after the installation finishes), and then the task deletes itself after it expires.
Is there a better way to accomplish this, or is this the best/only way?
Thanks,
Jeff Becker
FOLLOW US
Get the latest news in Application Packaging