BrowsePopularContact UsAbout Us

How to Open CMD as Administrator in Windows

Running the Command Prompt with elevated privileges unlocks a different tier of system access. Standard CMD sessions operate within user-level permissions — enough for basic tasks, but blocked from anything that touches system files, services, registry entries, or network configurations. When you need that deeper access, you need to open CMD as an administrator.

Here's how it works, why it matters, and what affects whether a given method will work on your machine.

Why Administrator Access Changes What CMD Can Do

Windows uses a permission model called User Account Control (UAC). Even if your Windows account is an administrator account, most programs — including CMD — launch in standard user mode by default. This is a deliberate security layer.

When you open CMD with elevated (admin) privileges, you're effectively telling Windows: run this session with full system rights. That unlocks commands like:

  • net user and net localgroup (user/group management)
  • sc and net start/stop (service control)
  • diskpart (disk partitioning)
  • netsh (advanced network configuration)
  • sfc /scannow (System File Checker)
  • Editing protected registry paths via reg

Without elevation, these commands either fail silently or return "Access is denied."

Methods to Open CMD as Admin 🖥️

Method 1: Right-Click the Start Menu

This is the fastest route for most users.

  1. Right-click the Start button (or press Win + X)
  2. Select "Windows Terminal (Admin)" or "Command Prompt (Admin)" — depending on your Windows version
  3. Click Yes on the UAC prompt

On Windows 11, the default elevated terminal is Windows Terminal. On Windows 10, you may see Command Prompt listed directly.

Method 2: Search and Run as Administrator

  1. Press the Windows key and type cmd
  2. In the search results, right-click Command Prompt
  3. Select "Run as administrator"
  4. Confirm the UAC prompt

This works reliably across Windows 10 and Windows 11 on any hardware configuration.

Method 3: Use the Run Dialog

  1. Press Win + R to open the Run dialog
  2. Type cmd
  3. Instead of pressing Enter, press Ctrl + Shift + Enter

This keyboard shortcut forces the program to launch with elevation. It's one of the most efficient methods once it's muscle memory.

Method 4: Task Manager

  1. Press Ctrl + Shift + Esc to open Task Manager
  2. Go to File → Run new task
  3. Type cmd
  4. Check the box labeled "Create this task with administrative privileges"
  5. Click OK

This method is especially useful when the taskbar or Start menu isn't responding correctly.

Method 5: From File Explorer

  1. Navigate to C:WindowsSystem32
  2. Find cmd.exe
  3. Right-click it and select "Run as administrator"

Not the most convenient for daily use, but works when other launchers are unavailable.

What Affects Whether These Methods Work

Not every method produces the same result on every machine. Several variables determine your actual experience:

VariableHow It Affects Access
Account typeOnly accounts with admin privileges can elevate. Standard accounts require admin credentials at the UAC prompt.
UAC settingsIf UAC is set to "Never notify," elevation may happen silently — or be blocked by Group Policy.
Windows editionHome, Pro, Enterprise, and Education editions handle UAC and Group Policy differently.
Managed/corporate devicesIT-managed machines may restrict elevation entirely, regardless of local account type.
Windows versionWindows 11 defaults to Windows Terminal instead of standalone CMD, which changes where the option appears.

Standard User vs. Administrator Account

If your Windows account is a standard user (not an admin), you'll see a credential prompt when attempting elevation — asking for an administrator username and password. Without those credentials, CMD won't open with admin rights regardless of method.

To check your account type: Settings → Accounts → Your info — it will display "Administrator" or "Standard User" beneath your name.

Group Policy Restrictions

On domain-joined or enterprise machines, Group Policy can override local UAC settings. Some organizations disable elevation entirely for certain users, or require specific approval workflows. If you're on a managed device and none of these methods work, the restriction likely lives at the IT policy level — not in Windows itself.

The Pin-to-Taskbar Trick for Repeated Use ⚡

If you regularly need elevated CMD access:

  1. Open CMD as admin using any method above
  2. Right-click the CMD icon in the taskbar while it's running
  3. Right-click "Command Prompt" in the jump list
  4. Select "Pin to taskbar"

From then on, right-clicking the pinned icon gives you a "Run as administrator" option directly.

Alternatively, you can create a shortcut that always launches elevated: right-click the shortcut → Properties → Advanced → check "Run as administrator".

A Note on Windows Terminal vs. Classic CMD

In Windows 11 (and optionally in Windows 10 with the Terminal app installed), Windows Terminal is the modern host for CMD, PowerShell, and other shells. When you open an elevated terminal, you're running CMD (or PowerShell) inside the Terminal interface — not the legacy cmd.exe window.

Functionally, the elevated CMD session inside Windows Terminal behaves identically to the classic elevated CMD window. The commands, permissions, and behavior are the same. The difference is purely the shell host — which matters more for customization and multi-tab workflows than for the commands themselves.

Which method makes sense for your workflow depends on how often you need elevated access, what type of account you're using, and whether your machine is personally owned or managed by an organization. Those specifics shape which approach is actually available to you — and which is worth building into your routine.