How to Open PowerShell as Administrator (3 Ways)
─□✕

How to Open PowerShell as Administrator (3 Ways)

PowerShell Tips Editor 4 min read
How to Open PowerShell as Administrator (3 Ways)

A surprisingly large number of PowerShell commands fail silently or return partial results when run as a standard user. If you’ve ever run Get-Service and gotten an “Access Denied” error, or tried to install a module and seen nothing happen, elevation is almost certainly the issue. Knowing how to open PowerShell as administrator on Windows 10 and 11 is a foundational skill — here are three reliable methods plus a way to auto-elevate your scripts programmatically.

Quick Answer / TL;DR

Right-click PowerShell in the Start menu and choose Run as administrator. The title bar will show “Administrator: Windows PowerShell” when elevated successfully.

Why Run PowerShell as Administrator

Windows User Account Control (UAC) restricts what standard users can do, even on their own machines. Many PowerShell operations require elevation:

  • Installing modules to the AllUsers scope with Install-Module
  • Starting, stopping, or changing Windows services
  • Modifying the registry under HKLM:\
  • Creating or deleting files in system directories
  • Setting the execution policy at the LocalMachine scope
  • Managing scheduled tasks for all users

Running elevated does not mean you’ll break things — it means PowerShell has the permissions to actually carry out the commands. You should still use -WhatIf before destructive operations regardless of elevation level.

Method 1: Right-Click Start Menu

This is the fastest method for Windows 10 and 11:

  1. Press the Windows key to open the Start menu.
  2. Type powershell.
  3. In the search results, right-click Windows PowerShell and select Run as administrator.
  4. Click Yes on the UAC prompt.

On Windows 11, you can also right-click the Start button (or press Win + X) to get a quick menu that includes “Windows PowerShell (Admin)” or “Terminal (Admin)” depending on your default terminal setting.

Method 2: Search Bar Shortcut

A keyboard-only approach that saves a few clicks:

  1. Press Win + S to open search (or just start typing from Start).
  2. Type powershell.
  3. Press Ctrl + Shift + Enter — this opens the highlighted result as Administrator directly.
  4. Confirm the UAC prompt.

This shortcut works for any application in Windows search, not just PowerShell. It’s worth memorizing.

Method 3: Run Dialog (Win+R)

The classic Run dialog still works and is especially useful on locked-down machines:

  1. Press Win + R to open the Run dialog.
  2. Type powershell.
  3. Press Ctrl + Shift + Enter instead of just Enter — this elevates it.
  4. Confirm the UAC prompt.

Alternatively, from an already-open standard PowerShell session, you can launch an elevated one with:

Start-Process powershell -Verb RunAs

How to Tell If PowerShell Is Elevated

Always verify before running sensitive commands. There are two quick checks:

# Method 1: Check the window title — it says "Administrator" when elevated

# Method 2: Check programmatically
$currentUser = [Security.Principal.WindowsIdentity]::GetCurrent()
$principal = [Security.Principal.WindowsPrincipal]$currentUser
$principal.IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)
True

Returns True when elevated, False when running as a standard user.

Auto-Elevate a Script Automatically

For scripts you run regularly, add this block at the top to self-elevate if needed:

# Self-elevation block — place at the top of your script
$isAdmin = ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole(
    [Security.Principal.WindowsBuiltInRole]::Administrator
)

if (-not $isAdmin) {
    Write-Warning 'Script is not running as Administrator. Relaunching elevated...'
    Start-Process powershell -Verb RunAs -ArgumentList "-NoProfile -ExecutionPolicy Bypass -File `"$PSCommandPath`""
    exit
}

This pattern relaunches the same script in an elevated window. Note that Start-Process -Verb RunAs requires a GUI session — it will fail in non-interactive contexts like Task Scheduler or CI/CD pipelines where there is no desktop to display the UAC prompt.

Common Errors and Fixes

  • UAC prompt not appearing — disabled by IT policy: In corporate environments, UAC may be configured to auto-deny or auto-approve elevation without a prompt. If you never see a UAC dialog, your IT policy may require you to use a different admin account. Run Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System' -Name EnableLUA to check if UAC is enabled (value should be 1).
  • Start-Process -Verb RunAs fails without GUI session: In headless or service contexts, there is no desktop session to display the UAC prompt. Instead, configure Task Scheduler to run the task as a user with administrative privileges, or use a service account. The -Verb RunAs approach is only reliable in interactive desktop sessions.

Related Cmdlets / See Also

Wrapping Up

Opening PowerShell as Administrator is a two-second operation once you know the shortcuts — right-click the Start menu result or use Ctrl + Shift + Enter from search. For scripts, embed the self-elevation pattern so they always run with the rights they need. Your next step: check your execution policy so scripts actually run once you’re elevated.

#admin#beginner#runas#uac
Send-Item -To