How to Open PowerShell Using Windows + R (Run Dialog)

Opening PowerShell through the Run dialog is one of the fastest and most reliable methods available on Windows — no desktop shortcut required, no hunting through menus. If you're comfortable with the keyboard, this approach becomes second nature quickly.

Here's exactly how it works, what variations exist across Windows versions, and what to consider depending on your specific setup.

What Is the Windows + R Method?

Pressing Windows key + R opens the Run dialog — a lightweight input box that accepts commands, file paths, and program names directly. It's been part of Windows since Windows 95, and it remains one of the most efficient ways to launch system tools.

When you type a command into Run and press Enter, Windows looks for a matching executable in known system paths. Because PowerShell is registered as a system tool, it responds to a simple typed command without needing a full file path.

Step-by-Step: Opening PowerShell via Run

1. Press Windows key + R simultaneously. The Run dialog appears in the lower-left area of your screen.
2. Type powershell into the input field.
3. Press Enter (or click OK).

PowerShell opens as a standard window running under your current user account. That's the entire process for a basic launch.

Opening PowerShell as Administrator 🔑

Many tasks — including modifying system settings, running certain scripts, or changing execution policies — require elevated (administrator) privileges. The Run dialog supports this with one small change:

1. Press Windows key + R.
2. Type powershell.
3. Instead of pressing Enter, press Ctrl + Shift + Enter.

This combination tells Windows to launch the program with administrator rights. You'll typically see a UAC (User Account Control) prompt asking for confirmation. After approving, PowerShell opens with an "Administrator" label in the title bar.

If UAC prompts don't appear on your machine, your account may already have unrestricted admin access — common on personal single-user machines — or UAC has been manually disabled, which carries its own security considerations.

PowerShell vs. Windows PowerShell vs. PowerShell 7

The command powershell in the Run dialog launches Windows PowerShell (version 5.1), the version built into Windows 10 and Windows 11. This is the default system PowerShell and handles the vast majority of everyday tasks.

PowerShell 7 (also called PowerShell Core) is a separate, cross-platform version that must be installed independently. It does not replace Windows PowerShell — both can coexist. If you've installed PowerShell 7, you can launch it via Run using:

pwsh 

If pwsh returns an error in the Run dialog, PowerShell 7 is either not installed or its installation directory isn't in your system's PATH variable.

Why the Run Dialog Is a Preferred Launch Method

Some users default to right-clicking the Start menu or searching in the taskbar, but the Run dialog has specific advantages:

• Speed — keyboard-only, no mouse required
• Consistency — works the same across Windows 10 and Windows 11
• Reliability — unaffected by taskbar customization or Start menu layout changes
• Elevation shortcut — Ctrl + Shift + Enter for admin mode works here but isn't as intuitive in other launch methods

For IT professionals and power users who frequently need a terminal, this method tends to stick once learned.

What Affects Your Experience

Several factors shape how this process behaves on a given machine:

Windows version and edition — Windows 10 Home, Pro, and Windows 11 all include Windows PowerShell 5.1, so the powershell command works universally. However, Group Policy restrictions on certain organizational or enterprise machines may block Run dialog usage or require additional authentication steps.

User account type — Standard user accounts can open PowerShell normally but will be denied certain commands that require elevation. Admin accounts trigger UAC by default; fully unrestricted accounts skip UAC entirely.

Execution policy — PowerShell may open fine but refuse to run scripts depending on your system's execution policy setting. This is separate from how you launch it. Common policies include Restricted (no scripts), RemoteSigned (local scripts allowed), and Unrestricted. Changing execution policy itself requires an elevated session.

PowerShell version installed — If your workflow requires PowerShell 7 features (better error handling, cross-platform compatibility, updated cmdlets), simply using powershell won't get you there. You'd need pwsh, and that depends on whether version 7 was installed and properly configured.

Organizational IT policies — In managed environments (corporate machines, school computers), Run dialog access or PowerShell itself may be locked down via Group Policy. What works on a personal machine may behave differently on a work-issued device. 🖥️

Common Mistakes and Quick Fixes

Run dialog doesn't appear — Some Windows configurations or third-party shells suppress the Run shortcut. Try searching "Run" in the Start menu as an alternative.

"Windows PowerShell" opens instead of expected version — Confirm whether you need PowerShell 7 (pwsh) versus the built-in version (powershell). They're functionally different in some areas.

Script won't execute after opening — This is an execution policy issue, not a launch issue. Running Get-ExecutionPolicy in the PowerShell window confirms your current setting.

UAC prompt appears unexpectedly — This is expected behavior when using Ctrl + Shift + Enter. It's a security confirmation, not an error. ✅

The Run dialog method itself is straightforward — but what you do once PowerShell is open, and which version or privilege level you actually need, depends entirely on the task you're working on and how your system is configured.