How to Open PowerShell as Administrator on Windows

Running PowerShell as Administrator is required for many system-level tasks such as configuring Windows, installing software, or running administrative scripts.

If a command fails unexpectedly, one of the first things to verify is whether the PowerShell session is actually elevated.

Below are the most reliable ways to open PowerShell with elevated privileges on Windows.

---

Quick method (fastest)

If you already have a PowerShell window open, run:

# Open PowerShell as Administrator
Start-Process powershell -Verb runas

You’ll be prompted by User Account Control (UAC). Click Yes to open an elevated PowerShell session.

This is often the fastest option when you realise mid-task that elevation is required.

---

1. Open PowerShell as Administrator from the Start Menu

Windows 10 / Windows 11

1. Press the Windows key
2. Type PowerShell
3. Select Run as administrator

This remains the most common and discoverable method on modern Windows versions.

To do this on Windows 7 or 8, the steps are slightly different. Those versions are out of support and should not be used for administrative work.

2. Open PowerShell as Administrator using Windows Terminal

Windows Terminal is the default terminal application on Windows 11 and supports PowerShell profiles.

To open PowerShell as Administrator:

• Right-click Windows Terminal
• Select Run as administrator

Or, if PowerShell is your default shell:

• Hold CTRL
• Click the + icon to open a new elevated tab

Be aware that Windows Terminal does not always launch elevated by default, even if PowerShell is your active profile. Always verify the session context.

---

3. Open PowerShell as Administrator from Task Manager

This method is useful when the Start Menu or Explorer is unavailable.

1. Press Ctrl + Shift + Esc to open Task Manager
2. Click Run new task
3. Type powershell
4. Check Create this task with administrative privileges
5. Click OK

An elevated PowerShell window will open.

This approach is especially useful during incident response or when troubleshooting broken shell environments.

---

Notes

• Many PowerShell cmdlets require administrator rights to modify system or security settings
• If a script fails with access or permission errors, always confirm the session is elevated before troubleshooting further
• Windows Terminal profiles can mask whether a tab is elevated, so visual confirmation matters