GUI when running in interactive mode

When running with a GUI in interactive mode and a limited user account I see that there are a number of rather short replies that suggest running the GUI as administrator.

OK so its easy to do

1). Use task manager to kill the egui.exe process
2). start the gui and run as administrator.

The problem with this is that the GUI is started via the registry and the above is one way to overcome the issue but when you gain access to your limited user account there may already be prompts that you cannot accept and configured and when you do the above those are lost never to return if it is another start-up program requesting the access.

So what is the recommended way to do this:

Run with a limited access account in interactive mode with access to the GUI that allows access requests to be actioned as required - without loosing any of them?

Why is there no exit option on the GUI if I can kill the process there might justr as well be an exit - it cannot lower the security any further?

Why is this not catered for when the program is installed and options configured appropriately to allow the limited user to achieve the desired result?

 

I am not a specialist in Vista (I am not running it) but you can try to make both EGUI.exe and EKRN.exe run as Administrator permanently (if ekrn.exe is not running as such already)

 

So how do you do that - it is not a property on the exe as far as I can see.

 

Very easily:

http://technet2.microsoft.com/Windo...8514-4c9e-ac08-4c21f5c6c2d91033.mspx?mfr=true
Scenario 2: Configure an application to always run elevated

 

Thanks for that link - useful. I had not noticed that option before I was not expecting to find it under the compatibility tab.

So now all I require is to avoind having to run the blocked program as that is what happens when you log into the limited user account.

I see that this comment is on this page:

"However, in this scenario you want to run an application that has not been marked by the developer or identified by the operating system as an administrative application."

which probably means you cant avoid it. All that remains now is to see what is misses. I assume as it has not run during this session any prompts will be queued up until it is started.

IMHO There has to be a better way to do this.