There are applications that need administrative permission in order to work properly. Some applications might need access to special system resources, some may have been designed only for Windows XP and do not work that well on Windows Vista, or some may have different bugs and problems. Running them as an administrator will help these applications run without problems. However, each time you start such an application you will see an UAC (User Account Control) prompt asking for your permission to launch it.
This is the reason why many people choose to disable UAC. However, by eliminating the annoying UAC prompts they also lower the security of their system. Fortunately, there is a way to keep UAC turned on and, at the same time, eliminate the prompts for certain applications. In this guide we will show you how to do the following: set an application to always run as an administrator (if needed), create a UAC fix for it that turns off the prompts for that application and install/uninstall the fix.
How to run an application as an administrator
To run an application as an administrator you can right click on it's shortcut or main executable and select Run as administrator from the right click menu. However, doing this can be quite annoying if you use this application very often. The second and better option is to edit it's properties and set it to always run as an administrator.
To do this, select it's shortcut or main executable, right click on it and select Properties.

In the Properties window, go to the Compatibility tab. Check the option that says Run this program as an administrator and click on OK.

Every time you will launch this application an UAC prompt will show up asking for your approval.
How to create the UAC fix
First, download and install the Microsoft Application Compatibility Toolkit.

Then, search for the Compatibility Administrator shortcut, right click on it and select Run as administrator. The shortcut ca be found in the Start Menu under Microsoft Application Compatibility Toolkit.

When you are in the Compatibility Administrator window, go to Custom Databases -> New Database. Right click on the new database and select Create New -> Application Fix.

The Create new Application Fix wizard will now start. Type the application name, the vendor (optional) and browse to the location of the main application executable. When done, click on Next.

When you are in the Compatibility Modes window, scroll down the list of available modes until you find RunAsInvoker. Check this mode and click on Next.

Now click on Next without changing anything.

When you are in the Matching Information window click on Finish.

Now you will return to the Compatibility Administrator window. Here, go to the File menu and click on Save or Save As.

In the Database Name window type a name for the fix you just created and click on OK.

Now, browse to the location where you want to save the database, type the file name and click on Save.

How to apply the UAC fix
To apply the fix you need to start the Command Prompt as administrator. Find it's shortcut, right click on it and select Run as administrator.

Type the following command: "sdbinst [path]\filename.sdb", where [path] is the location of the file you created using the Compatibility Administrator, and then press on Enter.

The application for which you have created and applied the fix should now start without any UAC prompts. If the fix doesn't work and you just want to uninstall it, start the Command Prompt again and type the command: "sdbinst [path]\filename.sdb -u".
Related applications:
How to disable UAC
Tweak the User Account Control (UAC)
Recommended articles:
4 Ways to Make UAC Less Annoying on Windows Vista
Comments
Doesn't work for me
OS= Vista Home Premium
All went fine until the step for "dbinst." It gave this error message:
'dbinstall' is not recognized as an internal or external command,
operable program or batch file.
Correction
it is working fine but he made a typing mistake...
it should be: "sdbinst [path]\filename.sdb"
it is sdbinstall NOT dbinstall
Sdbinst
Thanks... We corrected the mistake. I don't know how that slipped into the final article. :(
Run with admin privileges?
The RunAsInvoker parameter makes sure that an application runs with the same privileges as its parent process. Therefore, your UAC fix won't be helpful if you want that the application runs with admin privileges. You don't see the UAC prompts anymore because the application will only run with standard user rights. This is also the case if you configure the application to run with admin privileges. You can try it with notepad. Follow the procedure above and then try to save a file in the programs folder.
not quite
For some reason my Vista Home Premium decided yesterday - after some other issues - not to run the latest Microsoft Office if the User Account Control is on. (I get a message that Word, for example, is not installed for this user - when I'm the only user and running as administrator.) After reinstalls, tweaks, calls to Microsoft, etc., I gave up. I'd like to run UAC, but I'm not willing to give up Word. I tried your fix - didn't quite work. If I change it to run as administrator rather than run as invoker, it at least lets me run Word after responding to the UAC prompt.
Doesn't work on ProTools
When I installed this for ProTools LE, ProTools immediately emitted "ProTools Application has stopped working." I uninstalled the fix and the app started normally.
Too bad. This is a constant annoyance.
Post new comment