Starting with Windows Vista back in 2007, Microsoft made the very smart decision to limit the ability of applications to make key changes to a user’s PC. Only applications with administrator privileges could access important parts of Windows, and users had to specifically enable these apps to “run as administrator.”
This new policy, which continues today in Windows 8.1, wasn’t perfect, but it greatly increased the security of Windows as a whole. Unfortunately, it also caused problems with many software applications, especially older apps that were written at a time when administrator privileges could be assumed in most cases.
As a result, some applications require that users employ the “run as administrator” option in order to function properly, or at all. This is easy enough to do on an ad hoc basis with a simple right-click on an application’s executable, and a selection of the “run as administrator” command.
But if you frequently run a certain application that requires administrator privileges, it can be annoying to launch it with a right-click every time. Here are two ways to enable an application to always run with administrator privileges (or in “administrator mode”) in Windows. We’ll be using Windows 8.1 in our screenshots, but this tip applies to Windows Vista and Windows 7 as well.
Always Start an Application with Administrator Privileges
If you want all instances of a particular app to run in administrator mode, you can change the app’s compatibility settings. Navigate to the location on your hard drive where the application is installed (usually located in the applicable subfolder of the Program Files directory). Find the app’s primary executable. In our example, we’re using the video conversion software RipBot264, and its executable is RipBot264.exe.
Right-click on the app’s executable and select Properties, then click on the Compatibility tab. Here, you’ll find a number of options that may enable older software to run on modern versions of Windows. The feature we’re interested in, however, is Run this program as an administrator. This produces the same result as the option found in the right-click menu, but it makes the setting permanent, so that the app will always run in administrator mode regardless of how it’s launched.
Check the box and then click Apply. Click OK to close the properties window. Note that this change will only be enabled for the current user. If you have multiple users on your PC and want all of them to be able to run the application in administrator mode by default, click the Change settings for all users button before closing the properties window.
Start an Application with Administrator Privileges Only with a Special Shortcut
The steps above enable administrator mode across the board. But what if you want to enable it only in certain situations? For this scenario, you can create a unique shortcut that will launch an application with administrator privileges, but have the app launch with default privileges in every other instance.
To create a custom administrator mode shortcut, once again navigate to the application’s executable. Right-click and select Create shortcut. By default, the new shortcut will appear in the same directory as the source executable. Now right-click on the shortcut and select Properties.
In the Properties window, make sure you’re on the Shortcut tab and click the Advanced button. In the Advanced Properties window that pops up, check the box labeled Run as administrator. Click OK to close the Advanced Properties window, and OK again to close the shortcut Properties window. Now copy your shortcut to a convenient place and give it an appropriate name, which in our case might be “RipBot264 Admin.”
Whenever you run this shortcut, the application will run with administrator privileges, but if you launch the application through another shortcut that hasn’t been modified, or via the app’s executable itself, it will only run with standard privileges.
While these tips can make running apps that require administrator privileges easier, they can also expose your PC to greater risk. Applications with administrator privileges gain access to critical Windows locations and settings. If you allow a malicious application to run as administrator, you risk infecting your computer with malware, losing your data, or both. So, in short, be careful and only apply the tips above to applications that you know and trust.
Want news and tips from TekRevue delivered directly to your inbox? Sign up for the TekRevue Weekly Digest using the box below. Get tips, reviews, news, and giveaways reserved exclusively for subscribers.
still not working… i m using 8.1 but stil i always need to right click and then click on run as administrator
I’ve accomplished it before, but had to search to find the solution.
There’s a way to use a batch file, as windows startup doesn’t honor/acknowledge that “run as admin” setting, but auto-running said batch file gets around it…. If I find it I’ll let you know, as i’m currently hunting for the instructions (which is how I happened upon this discussion).
I do believe it’s exactly the solution you guys are needing…
-cheers, andy
(this is not a duplicate comment, as i replied to the wrong person, then deleted it…. hopefully this text is enough to make reply unique…..)
Yeah, this doesn’t seem to work in Windows 8.1. Still have to right-click to launch as admin, manually, every time. If I’m the only person to ever use this computer (heck, the only person to enter this room), there should be a “I am always the admin” setting for the whole damn computer.
It can’t be done that way. If you disable UAC, or set your user profile to Administrator, then you have no real protection against viruses. Once you really understand that, you will want any new program that suddenly appears protected, so it won’t be able to do admin actions.
Thanks for the reply. Clearly, I don’t know enough about programming to argue the point. I just know it worked that way on older versions — my last computer for example, which ran XP. I was able to update programs without resorting to “run as admin”, which is what I have to do now.
(Fortunately, this isn’t an issue most days, just once a month or so.)
These tips are interesting, but they are only claimed to work with EXE files and shortcuts to EXE files. What about a command file that may contain “internal commands” that require Administrative rights? Please extend these tips to provide automatic administrator access to specific shortcuts to command files (this also works).
Also, here is an explanation for why people are claiming that your tips don’t work: yes, your tips allow running programs as Administrator, but the UAC check and dialog box still occur (this can be considered a bug in Windows). There are more complicated solutions using task scheduling or other features that skip the UAC warning entirely, which is what one wants, especially for a user-written command file (because it is not likely to replaced by a virus). Such UAC workarounds are safe, particularly when the user is knowledgeable and careful concerning viruses.
I’ve accomplished it before, but had to search to find the solution.
There’s a way to use a batch file, as windows startup doesn’t honor/acknowledge that “run as admin” setting, but auto-running said batch file gets around it…. If I find it I’ll let you know, as i’m currently hunting for the instructions (which is how I happened upon this discussion).
I do believe it’s exactly the solution you guys are needing…
-cheers, andy
All well and good. But with the increasing use of Standard Users it’s not enough. One would want a Standard User to launch the app with “run as Administrator” AND to not have the Administrator User password. How to best do that?
The “Always Run as Administrator” worked perfectly and is a wonderful tip. Very useful and easy to implement. Thanks.
Doesn’t work for me, it still asks me for my password every time…
I have Windows 7. I’ve tried the the “Always Run As Administrator” option, and it doesn’t work. HALP!
I am having the same issue here. One of our employees uses InfoMaker 9.0 and running Windows 10, but it will only run in Administrator mode. We just want him to have admin rights to InfoMaker, nothing else. Help! Thanks.