0
I have composed a fix for an x64 program under Windows7. It's really simple, it should start the app with "runasinvoker" rights.
When testing with the toolkit (clicking on the fix in the left pane, selecting "run" from the top menu and stating the right path to the EXE) gives exactly the wanted result: the app starts with elevated rights.
Saving and installing the fix from the Compatibility Tool itself (clicking on the custom DB's name in the left pane, selecting "install" from the right click menu) or installing the fix via sdbinst does not.
In both cases the fix is shown as installed by the Compatibility Tool and "Remove Programs" menu but the application still starts without elevated rights.
I can't see why this happens. It must be a severe case of PEBKAC but can't see myself what I'm missing here. Can anyone point me into the right direction, please?
beerbear
Posted 2018-01-06T16:28:33.127
Reputation: 55
asInvoker means start without admin rights. that is the point. – magicandre1981 – 2018-01-07T17:22:36.513
It's obviously not the point when the fix does work when started from the compatibility tool. – beerbear – 2018-01-07T23:35:29.773
you run into XY issue. you want prevent UAC prompt but use wrong way and get issue. Use Task Scheduler to workaround the UAC prompt – magicandre1981 – 2018-01-08T16:33:30.933