visual-studio - without - visual studio run program as administrator
Can you force Visual Studio to always run as an Administrator in Windows 8? (8)
- On Windows 8 Start Menu select All Apps
- Right click on Visual Studio 2010 Icon
- Select Open File Location
- Right click on Visual Studio 2010 shortcut icon
- Click Advanced button
- Check the Run as Administrator checkbox
- Click OK
In Windows 7, you could go into a programs compatibility settings and check off to always run as an Administrator. Is there a similar option in Windows 8?
I've always disabled UAC on my machines, and did the same after my Windows 8 upgrade, or so I thought. It turns out there is no
off option, only turning off the notifications.
This means nothing is run as an Administrator despite being in the Administrator group. I need to keep closing and reopening my consoles\Visual Studio when I try to debug (attach to process, not F5), which is very frustrating.
It's really annoying that I need to either remember to take extra steps to open it as an Administrator or tell it to close and re-open when I go to debug for the first time.
NOTE in recent VS versions (2015+) it seems this extension no longer exists/has this feature.
You can also download VSCommands for VS2012 by Squared Infinity which has a feature to change it to run as admin (as well as some other cool bits and pieces)
One can install the commands from the Visual Studio menu bar using
Extensions and Updates selecting
Online and searching for
vscommands where then one selects
VSCommands for Visual Studio 20XX depending on whether using 2012 or 2013 (or greater going forward) and download and install.
I found a simple way to do this on EightForums (Option 8), create a string value under HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers. Set the name to the path to the program and the value to ~RUNASDMIN. Next time you open the program it will open as an administrator
[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers] "C:\\Program Files (x86)\\Microsoft Visual Studio 12.0\\Common7\\IDE\\devenv.exe"="~RUNASADMIN"
I know this is a little late, but I just figured out how to do this by modifying (read, "hacking") the manifest of the devenv.exe file. I should have come here first because the stated solutions seem a little easier, and probably more supported by Microsoft. :)
Here's how I did it:
- Create a project in VS called "Exe Manifests". (I think any version will work, but I used 2013 Pro. Also, it doesn't really matter what you name it.)
- "Add existing item" to the project, browse to the Visual Studio exe, and click Okay. In my case, it was "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe".
- Double-click on the "devenv.exe" file that should now be listed as a file in your project. It should bring up the exe in a resource editor.
- Expand the "RT_MANIFEST" node, then double-click on "1" under that. This will open up the executable's manifest in the binary editor.
- Find the requestedExecutionLevel tag and replace "asInvoker" with "requireAdministrator". A la:
<requestedExecutionLevel level="requireAdministrator" uiAccess="false"></requestedExecutionLevel>
- Save the file.
You've just saved the copy of the executable that was added to your project. Now you need to back up the original and copy your modified exe to your installation directory.
As I said, this is probably not the right way to do it, but it seems to work. If anyone knows of any negative fallout or requisite wrist-slapping that needs to happen, please chime in!
In Windows 8 & 10, you have to right-click
devenv.exe and select "Troubleshoot compatibility".
- Select "Troubleshoot program"
- Check "The program requires additional permissions"
- Click "Next"
- Click "Test the program..."
- Wait for the program to launch
- Click "Next"
- Select "Yes, save these settings for this program"
- Click "Close"
If, when you open Visual Studio it asks to save changes to devenv.sln, see this answer to disable it:
Just find the program in Program Files directory (or in other location). Right click on the EXE file, on the second tab at the bottom check the checkbox of forcing running that program with administration privileges. From now all shortcuts of the exe file will be fired with administration privileges :)
This is a copy of my answer to a similar post on SuperUser:
Option 1 - Set VSLauncher.exe and DevEnv.exe to always run as admin
To have Visual Studio always run as admin when opening any .sln file:
- Navigate to
C:\Program Files (x86)\Common Files\Microsoft Shared\MSEnv\VSLauncher.exe.
- Right-click on
VSLauncher.exeand choose Troubleshoot compatibility.
- Choose Troubleshoot program.
- Check off The program requires additional permissions and hit Next.
- Click the Test the program... button to launch VS.
- Click Next, then hit Yes, save these settings for this program, and then the close buton.
To have Visual Studio always run as an admin when just opening visual studio directly, do the same thing to the DevEnv.exe file(s). These file are located at:
Visual Studio 2010
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
Visual Studio 2012
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe
Visual Studio 2013
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe
Visual Studio 2015
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe
Visual Studio 2017
C:\Program Files (x86)\Microsoft Visual Studio\2017\[VS SKU]\Common7\IDE\devenv.exe
Option 2 - Use VSCommands extension for Visual Studio
Install the free VSCommands extension for Visual Studio (it's in the Visual Studio Extensions Gallery) and then configure it to always have Visual Studio start with admin privileges by going to Tools -> VSCommands -> Options -> IDE Enhancements -> General and check off
Always start Visual Studio with elevated permissions and click the Save button.
Note: VSCommands is not currently available for VS 2015, but their site says they are working on updating it to support VS 2015.
I prefer Option 2 because:
- it also allows you to easily turn off this functionality.
- VSCommands comes with lots of other great features so I always have it installed anyways.
- it's just easier to do than option 1.
VSCommands didn't work for me and caused a problem when I installed Visual Studio 2010 aside of Visual Studio 2012.
After some experimentations I found the trick:
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers and add an entry with the name
"C:\Program Files (x86)\Common Files\Microsoft Shared\MSEnv\VSLauncher.exe" and the value
This should solve your issue. I've also blogged about that.