Run Command Prompt with admin rights by launching an elevated window from Start, Win+X, or Win+R with Ctrl+Shift+Enter, then accept the UAC prompt.
Some Windows commands work fine in a normal Command Prompt. Others fail with “Access is denied,” refuse to write to protected folders, or can’t change system settings. That’s when you need an elevated Command Prompt, often called “running CMD as administrator.”
This article shows the clean ways to open CMD with admin privileges, how to confirm you got the elevated window, and what to do when Windows blocks elevation. You’ll also see a few safe habits that keep admin sessions from turning into accidental damage.
What “Administrator” Means In Command Prompt
Windows separates day-to-day use from system-level changes. A standard Command Prompt runs with the permissions of your current user session. An elevated Command Prompt runs with a higher token that can write to protected areas, install drivers, manage services, and change system settings.
When you launch an elevated window, Windows usually shows a User Account Control prompt. That prompt is the gate that keeps random apps from silently taking admin rights. Microsoft’s overview of UAC elevation explains why the prompt exists and what changes when you approve it. How User Account Control works.
How To Run CMD As Administrator From Start Search
This is the most common path, and it works on Windows 10 and Windows 11.
- Press the Windows key.
- Type cmd or Command Prompt.
- Right-click Command Prompt.
- Select Run as administrator.
- Choose Yes on the UAC prompt.
If your account is not in the local Administrators group, Windows will ask for admin credentials. In that case, you can still open an elevated window, but only after entering the username and password of an admin account.
Quick Check That You’re Elevated
Look at the window title. It often starts with “Administrator: Command Prompt.” You can also run a command that shows your token groups.
- Type
whoami /groupsand press Enter. - Scan for “Mandatory Label\High Mandatory Level.”
That “High” label is a reliable sign the window is elevated.
Open Elevated CMD From The Win+X Menu
On modern Windows builds, the Win+X menu often shows Windows Terminal instead of Command Prompt. Either way, you can still reach an elevated shell.
- Press Win+X.
- Select Windows Terminal (Admin) if it appears.
- If a menu shows Command Prompt (Admin), pick that.
- Approve the UAC prompt.
If you land in PowerShell inside Windows Terminal, open a Command Prompt tab from the Terminal drop-down menu, or type cmd to start CMD inside the elevated Terminal session.
Launch Elevated CMD With Win+R And A Keyboard Shortcut
If you like staying on the keyboard, the Run dialog is a fast way to get an elevated prompt.
- Press Win+R.
- Type cmd.
- Press Ctrl+Shift+Enter.
- Approve the UAC prompt.
This shortcut helps when you’re already in another app and don’t want to reach for the mouse.
Pin CMD So “Run As Administrator” Is One Click Away
If you open an elevated prompt often, pinning a shortcut keeps things tidy.
- Search for Command Prompt in Start.
- Right-click it and choose Pin to Start or Pin to taskbar.
- Next time, right-click the pinned icon and choose Run as administrator.
This keeps the method consistent across Windows 10 and Windows 11.
Common Ways To Open Elevated CMD
| Method | Steps | Best For |
|---|---|---|
| Start search | Type cmd → right-click → Run as administrator | Most people, simplest path |
| Win+X menu | Win+X → Terminal (Admin) → open CMD tab | Power users, fast admin shell |
| Run dialog | Win+R → cmd → Ctrl+Shift+Enter | Keyboard-first workflow |
| Taskbar pin | Pin Command Prompt → right-click → Run as administrator | Frequent use |
| Start menu tile | Pin to Start → right-click tile → Run as administrator | Touch or tablet setups |
| File Explorer address bar | Type cmd in a folder → Enter (non-elevated) | Folder-scoped work without admin |
| Windows Terminal admin mode | Open Terminal (Admin) → run cmd | Multiple shells in one window |
| Shortcut set to admin | Shortcut Properties → Advanced → Run as administrator | Always-elevated shortcut |
Run Command Prompt As Admin Inside Windows Terminal
Windows Terminal can host Command Prompt, PowerShell, and other shells in tabs. You can open the whole Terminal app in admin mode, then launch CMD inside it.
- Right-click the Windows Terminal icon.
- Select Run as administrator.
- Open a Command Prompt tab, or run
cmd.
Microsoft’s Windows Terminal FAQ lists the built-in ways to start Terminal in administrator mode, including Win+X on many systems. Windows Terminal FAQ.
How To Confirm You’re Using The Right Window
It’s easy to open two prompts and lose track. A couple of checks prevent wasted time.
- Title bar: Many elevated windows show “Administrator:” at the start.
- Write test: Try
cd /d C:\Windows\System32. A normal window can enter the folder, but many admin-only actions inside it still fail. - Token label:
whoami /groupsshows the integrity level.
If a command fails, read the error text. “Access is denied” often points to permissions. “The requested operation requires elevation” is a straight signal you’re not elevated.
When You Should Avoid Admin CMD
Admin sessions are powerful, and that power cuts both ways. Use an elevated window when you need it, then close it.
- Use a normal window for file listing, simple network tests, and reading logs.
- Use elevation for service control, driver work, system file repair, and changing protected settings.
- Keep the elevated window scoped: run the command, check the result, exit.
This habit lowers the chance of running a destructive command in the wrong place.
Troubleshooting: When “Run As Administrator” Is Missing Or Fails
If the option is missing, the account or policy setup is usually the cause. Start with the simple checks, then move to deeper ones.
Check Account Type And UAC Prompt Behavior
If you’re on a standard user account, Windows can still elevate, but it needs admin credentials. If the prompt never appears, UAC settings or device policies may be blocking it.
- Try Start search → Command Prompt → Run as administrator again.
- Try Win+R → cmd → Ctrl+Shift+Enter to trigger elevation from a different entry point.
- Restart and try again, since explorer.exe glitches can block shell actions.
Fix “The Requested Operation Requires Elevation”
This message means the process you launched does not have admin rights, even if you expected it to. Reopen the window using one of the elevation methods above, then rerun the command.
If you’re running a batch file, call it from the elevated window, or set the shortcut that starts it to run as administrator so the whole chain starts elevated.
Use A Shortcut That Always Opens Elevated
For a consistent admin prompt, create a desktop shortcut to CMD and set it to run with admin rights.
- Right-click the desktop and choose New → Shortcut.
- Set the location to
C:\Windows\System32\cmd.exe. - Name it something clear, like “CMD (Admin)”.
- Right-click the shortcut → Properties → Shortcut tab.
- Select Advanced, tick Run as administrator, then save.
When you open this shortcut, UAC still prompts. That’s normal, and it’s the safety gate doing its job.
Open CMD In A Specific Folder With Admin Rights
People often want “open here as admin.” Windows makes it simple to start in the right directory, then elevate.
- Open a normal Command Prompt in the folder you want.
- Copy the full path shown after
cd. - Close it, open an elevated prompt, then run
cd /dand paste the path.
This takes an extra step, but it avoids registry hacks and stays easy to reverse.
Admin CMD Tasks That Commonly Need Elevation
Here are tasks that often require an elevated window. Run them only if you understand what they change.
| Task | Command Examples | What You’ll Notice |
|---|---|---|
| Service control | sc stop "ServiceName", sc start "ServiceName" |
Stops or starts Windows services |
| System file repair | sfc /scannow |
Scans and repairs protected system files |
| Image servicing | DISM /Online /Cleanup-Image /RestoreHealth |
Repairs component store issues |
| Network reset actions | netsh winsock reset |
Resets networking components |
| Drive checks | chkdsk C: /f |
May schedule a scan on reboot |
| User and group edits | net localgroup administrators |
Lists or edits local admin membership |
| Firewall changes | netsh advfirewall rules |
Edits firewall policy settings |
Safer Habits For Elevated Command Prompt Sessions
A few habits cut risk when you’re running with admin privileges.
- Check the path before delete or move commands. Confirm the folder with
cdanddir. - Prefer read-only commands first. Run
whoami,ipconfig, orsc queryto confirm context. - Copy commands from trusted sources, then read them. A single stray character can change the target.
- Close the window when you’re done. Leaving an elevated shell open invites mistakes.
CMD Elevated, Yet A Command Still Fails
Admin rights are not the only gate. Some operations are blocked by device management, antivirus rules, file ownership, or a missing component.
- If a command mentions “policy,” your device may be managed by work rules.
- If a file is “in use,” stop the related service or reboot, then retry.
- If you see “not recognized,” the tool may not be in PATH, or it may not be installed.
When you hit a wall, copy the exact error message and search it. Error text is more useful than the command name alone.
Wrap-Up: Pick The Method That Fits Your Workflow
If you want the simplest method, Start search and “Run as administrator” is hard to beat. If you want speed, Win+R with Ctrl+Shift+Enter keeps your hands on the keyboard. If you live in tabs, Windows Terminal in admin mode keeps CMD and PowerShell in one place.
Whichever method you pick, treat elevated windows as a short-lived tool. Open it, run the task, confirm the result, then close it.
References & Sources
- Microsoft Learn.“How User Account Control works.”Explains what changes during elevation and why UAC prompts appear.
- Microsoft Learn.“Windows Terminal FAQ.”Shows built-in ways to start Windows Terminal in administrator mode.
