Windows OS Hub
  • Windows
    • Windows 11
    • Windows 10
    • Windows Server 2025
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
  • Microsoft
    • Active Directory (AD DS)
    • Group Policies (GPOs)
    • Exchange Server
    • Azure and Microsoft 365
    • Microsoft Office
  • Virtualization
    • VMware
    • Hyper-V
    • Proxmox
  • PowerShell
  • Linux
  • Home
  • About

Windows OS Hub

  • Windows
    • Windows 11
    • Windows 10
    • Windows Server 2025
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
  • Microsoft
    • Active Directory (AD DS)
    • Group Policies (GPOs)
    • Exchange Server
    • Azure and Microsoft 365
    • Microsoft Office
  • Virtualization
    • VMware
    • Hyper-V
    • Proxmox
  • PowerShell
  • Linux

 Windows OS Hub / Windows 10 / How to Run File Explorer Elevated (as Administrator) on Windows

March 7, 2024

How to Run File Explorer Elevated (as Administrator) on Windows

File Explorer process always runs with minimal (non-elevated) privileges in Windows. Even if you click the C:\Windows\explorer.exe executable file and try to start it in the ‘Run as administrator’ mode, it will not elevate privileges. In this article, we will look at a simple trick to run File Explorer on Windows with elevated privileges (as administrator).

Contents:
  • Running the File Explorer Process on Windows as an Administrator
  • Fix: You Don’t Have Permission to Access Folder

Running the File Explorer Process on Windows as an Administrator

To run the Windows Explorer process with elevated privileges, you will first need to kill the unprivileged explorer.exe process.

  1. Open the Windows Task Manager (taskmgr.exe), go to the Details tab, find a kill the explorer.exe process (End task);kill non elevated explorer.exe process with task manager
  2. Then in Task Manager select -> File -> Run New Task -> run the command: explorer.exe /nouaccheck (make sure that the Create this task with administrative privileges option is enabled);run explorer with administrative privileges nouaccheck
  3. This will start the File Explorer process with administrator privileges. How can you be sure of this?
  4. On the Details tab, right-click the title of the process list and choose Select Columns;
  5. Check the Elevated option;add the elevated column in task manager
  6. Now you can see that the explorer.exe process is running in privileged mode (Elevated=Yes).elevated explorer.exe process

You can also run the elevated explorer.exe process from the PowerShell console (be sure to run powershell.exe as an administrator):

  1. Kill the running low-privileged explorer.exe process:taskkill /f /FI "USERNAME eq $env:UserName"/im explorer.exe
  2. Run the privileged explorer.exe:
    c:\windows\explorer.exe /nouaccheck
  3. The new explorer process will inherit the elevated access token that is used to run the powershell.exe console.

explorer.exe /nouaccheck - run elevated

(NO|UAC|CHECK)

You can create the following BAT file on your desktop to quickly run File Explorer with administrator privileges:

taskkill /f /FI "USERNAME eq %USERNAME%" /im explorer.exe
start c:\windows\explorer.exe /nouaccheck

bat file to run file explorer as admin

Changes related to running explorer.exe with administrative privileges have been introduced in build Windows 11 23H2. In this build, Windows 11 detects when you start Explorer with an administrator token, kills the running process, and starts a new one with non-elevated permissions instead.

In order to disable this behavior, you must modify the AutoRestartShell parameter in the registry:

$path = 'HKLM:SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon'
New-ItemProperty -Path $path -Name AutoRestartShell -Type Dword -Value 0 -Force | Out-Null

Windows will still kill the elevated process when you run the following command for the first time:

taskkill /f /FI "USERNAME eq $env:UserName" /im explorer.exe ; c:\windows\explorer.exe /nouaccheck

But if you start it again, the privileged explorer.exe will survive. 👌

When you have finished your task, remember to allow the Explorer shell to restart:

New-ItemProperty -Path $path -Name AutoRestartShell -Type Dword -Value 1 -Force | Out-Null
taskkill /f /FI "USERNAME eq $env:UserName" /im explorer.exe

Fix: You Don’t Have Permission to Access Folder

Let’s have a look at a common scenario where an Explorer process with administrator privileges can be particularly useful

In some cases, you may need to open the system or other users’ profile folders or edit protected system files by using Explorer running as an account that has been added to the local Administrators group (or even under the built-in Windows administrator). If you try to open such a directory or file in the current Explorer context, a User Account Control (UAC) warning window will appear, asking you to grant access and elevate privileges.

For example, try using Explorer to open the system directory C:\Windows\System32\Config. The UAC prompt should appear, informing you that you are not allowed to access the directory:

You don’t currently have permission to access this folder.
Click Continue to permanently get access to this folder.

If your account has local administrator permissions, you can use UAC to elevate privileges by clicking Continue.

You don’t currently have permission to access this folder. Click Continue to permanently get access to this folder

When you click Continue, UAC temporarily elevates the privileges of your explorer.exe process and grants your account Full Control NTFS permissions on the folder.

Known issues with this approach:

After performing such an operation, your account will be explicitly added to the NTFS folder permissions. Even though you only wanted to view the contents of the directory, not change its ACL! If this Windows Server host is managed by more than one administrator, then the folder ACL will be constantly increasing. This is because, when accessing the folder, any administrator will change the directory ACL.

uac changed acl in ntfs folder permissions

This behavior of File Explorer causes major problems when managing shared folders on Windows Server file servers. As a workaround, many Windows administrators prefer to manage NTFS permissions on shared network folders via a UNC path (\\mun-fs01\docs\) rather than locally. In this case, there is no need to elevate permissions when accessing the shared folder. Accordingly, NTFS ACLs won’t be modified.

This pop-up UAC notification becomes annoying if you are actively managing system files or shared folders. To avoid completely disabling UAC in Windows, you can temporarily run File Explorer as an administrator.

Be sure to restart explorer.exe in Normal mode when you have finished working with protected or user folders.

This trick of running the Windows Explorer process with elevated privileges works in Windows Server 2016/2019/2022 as well as in all builds of Windows 10/11.

In early Windows 10 builds, the launch of the elevated explorer.exe process was blocked by the built-in CreateExplorerShellUnelevatedTask scheduler task.
12 comments
11
Facebook Twitter Google + Pinterest
Windows 10Windows 11Windows Server 2016Windows Server 2019Windows Server 2022
previous post
How to Clean Up System Volume Information Folder on Windows
next post
Reduce Virtual Machine Disk Size (VMDK) on VMWare ESXi

Related Reading

How to Repair Windows Boot Manager, BCD and...

March 11, 2024

Fix: The Computer Restarted Unexpectedly or Encountered an...

May 16, 2024

PowerShell: Get Folder Size on Windows

April 2, 2024

Fixing “Winload.efi is Missing or Contains Errors” in...

March 16, 2024

Network Computers are not Showing Up in Windows...

March 15, 2024

How to Download Offline Installer (APPX/MSIX) for Microsoft...

March 12, 2024

Windows Doesn’t Automatically Assign Drive Letters

March 15, 2024

How to Clean Up System Volume Information Folder...

March 17, 2024

12 comments

Jeff October 26, 2016 - 2:18 pm

I tried this from a Windows 10 LTSB 2015 machine and it didn’t work.  I was excited to see the article because you are correct this is a pain.  Do you have any suggestions?

Reply
admin November 10, 2016 - 6:24 am

This trick only works on Windovs Server 2012 R2

Reply
Jeff November 10, 2016 - 2:47 pm

Ok, that makes sense then.  Thanks.

Reply
lia June 21, 2018 - 11:21 am

Not working on Windows Server 2016. Always starts explorer.exe without Elevated privileges

Reply
k March 22, 2019 - 12:11 am

Try this – start an elevated command prompt, open task manager, right-click explorer.exe in details pane, and ‘End task’. Then, switch to the command prompt and run explorer. Seems to prevent the auto-restart of explorer.exe when you try it the above way.

Reply
Rambler April 17, 2019 - 2:42 pm

What you need to do on W10/WS2016 and newer is:
– open Task Manager
– kill Explorer.exe process
– click the File menu, select Start new task, type: explorer /nouaccheck, be sure to tick the ‘Create this task with administrative privileges’
– click OK, there’s your elevated Explorer again

Reply
Chris February 8, 2020 - 1:28 am

worked beautifully thanks brskie

Reply
BAKEMONO April 16, 2021 - 2:42 pm

Reading the title i thought it would be a way, as being a simple user, launching explorer as an administrator…

So i tried the trick New-ItemProperty -Path “HKCU:\Software\Policies\Microsoft\Windows\CurrentVersion\Explorer” -Name ShowRunasDifferentuserinStart -Value 1 -PropertyType DWORD -Force but Explorer key doesn’t exist (win10 20H2) and i don’t have right to create it, and, after the modification of GPEDIT.msc, as the explorer is not available in the start menu to run it as another user this is not possible either (knowing that it would have to be able to mix the two techniques when you have to close the explore … so no solution)

Reply
max April 16, 2021 - 2:50 pm

This trick assumes that you are logon Windows with an account that is a member of the local Administrators group.

Reply
e.ostenhof September 9, 2021 - 4:09 am

ExplorerShellUnelevated
\CreateExplorerShellUnelevatedTask

S-1-5-18

false
false
false
IgnoreNew
6
true

PT10M
PT1H
true
false

true

C:\Windows\explorer.exe
/NOUACCHECK (NO|UAC|CHECK)
These commands will terminate the explorer.exe process for
the current user and start a new one, which will inherit
the elevated access token that powershell.exe is run with.

Reply
dk July 18, 2023 - 7:11 am

CreateExplorerShellUnelevatedTask is a system task created by Windows to prevent users and apps from running Windows Explorer process elevated

Reply
Franco F February 2, 2024 - 10:41 am

Thank you, this is a great trick but unfortunately it seems it does not work anymore on Windows 11 PCs, any other way to run explorer.exe elevated working on Windows 11?

Reply

Leave a Comment Cancel Reply

join us telegram channel https://t.me/woshub
Join WindowsHub Telegram channel to get the latest updates!

Recent Posts

  • Failed to Open the Group Policy Object on a Computer

    June 2, 2025
  • Remote Desktop Printing with RD Easy Print Redirection

    June 2, 2025
  • Disable the Lock Screen Widgets in Windows 11

    May 26, 2025
  • Configuring Windows Protected Print Mode (WPP)

    May 19, 2025
  • Map a Network Drive over SSH (SSHFS) in Windows

    May 13, 2025
  • Configure NTP Time Source for Active Directory Domain

    May 6, 2025
  • Cannot Install Network Adapter Drivers on Windows Server

    April 29, 2025
  • Change BIOS from Legacy to UEFI without Reinstalling Windows

    April 21, 2025
  • How to Prefer IPv4 over IPv6 in Windows Networks

    April 9, 2025
  • Load Drivers from WinPE or Recovery CMD

    March 26, 2025

Follow us

  • Facebook
  • Twitter
  • Telegram
Popular Posts
  • How to Repair EFI/GPT Bootloader on Windows 10 or 11
  • How to Restore Deleted EFI System Partition in Windows
  • Network Computers are not Showing Up in Windows 10/11
  • Install and Manage Windows Updates with PowerShell (PSWindowsUpdate)
  • How to Download Offline Installer (APPX/MSIX) for Microsoft Store App
  • Updating List of Trusted Root Certificates in Windows
  • Fix: Windows Cannot Connect to a Shared Printer
Footer Logo

@2014 - 2024 - Windows OS Hub. All about operating systems for sysadmins


Back To Top