33

In Windows 7 opening Run dialog (Win+R) and confirming with Ctrl + Shift + Enter ran specified command elevated.

In Windows 8 this trick doesn't work anymore and I miss it a lot!

Is there a way to get this feature back?

rajat
  • 359

3 Answers3

30

Do not press Win + R.

Instead, just press Win and type the command directly into the Metro interface. As you type, the search interface will start bringing up possible matches, but just ignore them. When you're done typing, press Ctrl + Shift + Enter, and the command will run elevated, as expected.

This works perfectly for full commands with arguments. It also works for commands without arguments, but with some caveats (matching shortcut, multiple executables, etc.). I have not generally found these to be a major problem.

taoyue
  • 2,769
12

Okay, I figured it out. It seems to be caused by new a feature of UAC called "Admin Approval Mode" or "AAM". You can disable this feature and (at least with UAC turned off as well) Win+R will run applications as elevated by default. -- I have tried this on 3 machines now and it has worked for me every time.

Here's how to go about disabling it:

  1. Open Local Security Policy editor (on the Start screen type "secpol" and right click it, "Run as administrator").

  2. From the menu on the left, expand "Local Policy".

  3. Under the expanded "Local Policy" heading, select "Security Options".

  4. On the panel on the right find "User Account Control: Run all administrators in Admin Approval Mode", open this setting and change the value to Disabled.

SecPol - User Account Control: Run all administrators in Admin Approval Mode

  1. "OK" out of everything, and reboot (at least on my machine it said that a reboot was required, YMMV).

 

If it all worked right, when you hit Win+R at your windows desktop you should see the little shield below the text box that says "This task will be created with administrative privileges."

You can see that this works.

(Note: Depending on your luck, you may have to turn off UAC as well.)

3

^ ^ I just signed up to comment about this, but I don't have 50 reputation to reply to the above. So I will reply in a new answer.

"Okay, I figured it out. It seems to be caused by new a feature of UAC called "Admin Approval Mode" or "AAM". You can disable this feature and (at least with UAC turned off as well) Win+R will run applications as elevated by default. -- I have tried this on 3 machines now and it has worked for me every time."

This indeed seems to be the only way to make the Windows Start Menu 'Run Command' ALWAYS run with administrator privileges. If you have a machine like me that is a Windows 'Home' product, the registry key can be found at

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System clicking on that, on the right side there is 'EnableLUA'. Right click 'Modify' this to value '0' instead of '1' and that does the same thing of disabling UAC. Which apparently, is exactly the same thing as 'built in admin approval', or that the admin approval only works when there is the UAC enabled to 'control' the different user/admin account privileges/access rights.

I've ended up giving up and making an admin enabled shortcut to cmd prompt and placing it above the 'programs' folder on my start menu, as this is pretty close to near my 'run' button (just above shutdown on my modified 'classic Start Menu' modded Windows 10 Home edition). Otherwise with UAC off, I am able to get admin rights on my run command in the start menu BUT CANNOT get rid of the error (doesnt seem to do much, stuff works after clicking 'ok' on it but don't like seeing it) - http://www.bleepingtech.com/windows-8-fix-this-app-cant-open-for-built-in-administrator-account/ This app can’t open for Built-in Administrator account please sign in with a different account and try again .. trying that fix but I don't think there is any way to get admin rights on the run command, without disabling UAC, which in turn gives that error..