How to Open File Explorer as Administrator in Windows

Most of the time, File Explorer works exactly as you'd expect — browse folders, move files, open documents. But occasionally you'll hit a wall: a folder you can't access, a file you can't delete, or a system directory that refuses to cooperate. That's usually a permissions problem, and opening File Explorer with administrator privileges is often the fix.

Here's what's actually happening, how to do it, and why the results depend more on your setup than most guides let on.

Why File Explorer Doesn't Run as Admin by Default

Windows runs File Explorer under your standard user token, even if your account is an administrator. This is part of User Account Control (UAC) — a security layer introduced in Windows Vista that separates everyday activity from elevated system access. The logic is sound: most of what you do in a file manager doesn't need deep system access, so Windows doesn't grant it by default.

When you need to view, move, or modify files in protected directories — like C:WindowsSystem32, certain ProgramData folders, or directories locked by other user profiles — a standard Explorer session will either block you outright or silently fail.

Running Explorer elevated gives it the same permissions as a full administrator session, bypassing those restrictions.

Method 1: Run File Explorer as Admin via the Run Dialog

This is the most straightforward approach:

1. Press Win + R to open the Run dialog
2. Type explorer.exe in the field
3. Hold Ctrl + Shift and click OK

Holding Ctrl + Shift while launching triggers a UAC elevation prompt. Accept it, and File Explorer opens with administrator privileges.

⚠️ One thing to know: Windows typically only runs one instance of Explorer at a time. If Explorer is already open, this method may simply bring that existing window to the foreground rather than launching a new elevated instance.

Method 2: Use Task Manager to Launch an Elevated Explorer

Task Manager lets you run processes under a different privilege level:

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

This method is more reliable for forcing a truly elevated instance, especially on systems where the standard shortcut workaround doesn't take effect.

Method 3: Open an Admin Command Prompt, Then Launch Explorer

If you're comfortable with the command line:

1. Search for cmd or PowerShell in the Start menu
2. Right-click and select Run as administrator
3. In the elevated terminal, type explorer.exe and press Enter

The Explorer window launched from an already-elevated shell will inherit those elevated permissions. This is a useful approach if you're already doing other admin tasks in the terminal.

Method 4: Create a Shortcut That Always Runs as Admin

If you regularly need elevated Explorer access, you can set up a persistent shortcut:

1. Right-click the desktop → New → Shortcut
2. Enter explorer.exe as the target location
3. Name the shortcut, then right-click it and select Properties
4. Go to the Shortcut tab → click Advanced
5. Check "Run as administrator"
6. Click OK and Apply

Every time you use this shortcut, Windows will prompt for UAC confirmation before launching Explorer with elevated rights.

The Single-Instance Problem: A Variable That Changes Everything 🔍

Here's where user setups diverge significantly. Windows is designed to run only one Explorer process across all windows. When you attempt to launch a second instance — especially an elevated one — Windows may route the request back to the existing non-elevated process.

Whether this happens depends on:

Some users on the same version of Windows will successfully get a separate elevated Explorer window; others will find the attempt redirected. There's no universal outcome.

What Administrator Access Actually Unlocks

Running File Explorer as admin typically lets you:

• Browse protected system folders without "Access Denied" errors
• Delete or rename files that are owned by the system or other users
• Move files into restricted directories like Program Files or Windows
• View hidden and protected operating system files more freely

It does not override file locks held by active processes, nor does it bypass encryption on files owned by other user accounts (like EFS-encrypted files belonging to a different profile).

The Variables That Determine Your Experience

What works cleanly on one machine may require extra steps on another. The key factors:

• Account type: You need an actual administrator account — not just a standard account. Elevation prompts will fail if you don't have admin rights to begin with.
• UAC level: If UAC is set to never notify, elevation happens silently. If it's at maximum, every prompt requires explicit confirmation.
• Windows edition: Home, Pro, and Enterprise editions handle group policies and user permissions differently, especially in managed or domain-joined environments.
• Whether existing Explorer is running: Closing all Explorer windows before attempting elevation often produces cleaner results.

Your specific combination of account type, Windows edition, UAC configuration, and whether you're on a personal or managed machine will shape which method works, how smoothly it works, and whether a truly isolated elevated instance is even achievable.