I have a VB.NET application that interfaces with MS-Outlook and, to do it, it must run without ADMIN priviledges. Everything is OK.
The problem occurs after the "LiveUpdate" module, a separated application running with ADMIN priviledges, ends its update and loads again the main application. This load is performed using:
Process.Start(MyApp.exe)
but when "MyApp" loads, it cannot interface anymore with MS-Outlook, which refuse that interface sending a typical message of programs running at different UAC priviledges. I guess when LiveUpdate executes the Process.Start, the command goes with its same priviledge (ADMIN).
Facts:
- The Liveupdate MUST run in ADMIN but MyApp MUST run in NORMAL way.
- Both has its own MANIFEST, but it seems the call above bypass the Manifest of MyApp - which is set "as Invoke" as default.
- If I close MyApp and run it again manually, everything goes OK.
- Some clients has USER/PASSWORD, others do not have it (Windows loads automatically with no User/Password dialog).
5.The application runs in Windows Vista, 7, 8, 8.1 and 10.
So, is there some way to "Process.Start" an application discarding the ADMIN priviledge from the caller (LiveUpdate)?
The usage of User/Password during this call is not an option I guess... Thanks!