That suggests that the updater is irrelevant and that the program has been set to run as admin separately. Right-click on the executable in Explorer and go to Properties>Compatibility to check whether the Privilege Level is set for Run As Admin.
<https://lh6.googleusercontent.com/-cXfkjEbspjg/T9dNePteWFI/AAAAAAAAABw/_n0JkAYcX7Y/s1600/prop.gif> On Monday, 11 June 2012 17:19:11 UTC+1, jtaylor wrote: > > We have a separate updater program to update our application. The updater > runs as admin but the application should not. When the updater restarts > the application (via Shell), the application is running as admin. I've > been looking around, I can find talk about how to upgrade authority to > admin but nothing on how to downgrade to standard user. > > On Saturday, June 9, 2012 10:22:10 AM UTC-5, Barry Etheridge wrote: >> >> If Update Program A updates Program B and then launches Program B as an >> entirely separate process surely Program B is by default not Run as >> Administrator? If Update Program A updates itself and then relaunches it >> won't be possible to run other than as Run as Administrator. >> >> On Wednesday, June 6, 2012 10:55:27 PM UTC+1, jtaylor wrote: >>> >>> I have a VB.NET software update app that is manifested to run as >>> admin. When it finishes the update process, I need it to launch the >>> production app as the non admin user. I cannot seem to find anything >>> on this. Can anyone give any pointers or suggestions? >>> >>> Thanks >> >> -- You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to dotnetdevelopment@googlegroups.com To unsubscribe from this group, send email to dotnetdevelopment+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en or visit the group website at http://megasolutions.net
