Key Points
- Use a specific registry workaround that forces Explorer to fall back to the classic context menu, bypassing the ‘Show more options’ layer.
- Apply the registry change via PowerShell or Group Policy Preferences.
- Use Shift + right-click to access the classic context menu before editing the registry.
- Delete the Class Identifier (CLSID) key or run the cleanup command to restore the default menu.
- Recheck after cumulative updates, as Windows changes may affect this workaround.
Windows 11 offers a modern UI design that helps streamline navigation. One aspect is the “Show more options” context menu item, which creates tighter right-click shortcuts. But this simplified look can also hinder advanced users and make automated workflows less efficient.
Tailor context menu design to optimize productivity. This article explains how to configure Windows 11 to always display the classic context menu by default using a registry-based workaround.
How to disable the “Show more options” context menu item
Bringing back the Windows 11 old context menu on one or multiple workstations will require the proper equipment and the right permissions. Before disabling the context menu item, consider your technical constraints.
Prerequisites:
- Administrative privileges to modify the local registry and Active Directory Group Policy Objects (GPOs)
- Test device running the same Windows 11 build as target systems
- Ability to restart File Explorer or log off after applying changes
Method 1: Preview the classic menu without changes
First, check to see if the old context menu suits your needs. This test doesn’t require admin rights and helps your team confirm whether a workflow truly needs an expanded option list.
To do this:
- Hold Shift and right-click on your desktop or
- Select an item and press Shift + F10
Method 2: Restore the classic context menu via the Registry Editor
If you want the classic context menu to appear by default, you can create a specific registry entry that changes the context menu behavior in supported Windows 11 builds.
Use Cases: Enforcing the Windows 11 classic context menu.
Prerequisites: None. This is a per-user change written to HKEY_CURRENT_USER.
- Press Win + R, type regedit, and press Ctrl + Shift + Enter.
- Navigate to: HKEY_CURRENT_USER\Software\Classes\CLSID
- Right-click CLSID and select New > Key.
- Name the new key {86ca1aa0-34aa-4e8b-a509-50c905bae2a2}.
- Right-click {86ca1aa0-34aa-4e8b-a509-50c905bae2a2} and select New > Key.
- Name it InprocServer32.
- Double-click (Default), ensure the Value data field is empty, and click OK.
- Close Registry Editor.
- Restart File Explorer. To do this, press Ctrl + Shift + Esc, find Windows Explorer, and click Restart. Alternatively, sign out and back in.
Method 3: Use a .reg file for one-click setup
To simplify registry changes, store your changes in a script, save it as a REG file, and deploy it to one or multiple workstations. This straightforward method helps prevent human errors and helps restore the classic context menu behavior on supported Windows 11 builds.
Use Cases: Reverting the Windows 11 context menu on one/multiple devices.
Prerequisites: Administrative privileges.
- Press Win + S, type notepad, and press Enter.
- Paste the following script:
Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32] @=””
- Name the file appropriately (e.g., RevertContextMenu) and save it with the .reg extension.
- Execute the file to merge the changes to the workstation’s registry.
- Restart File Explorer or reboot the machine.
- Streamline this task with dedicated automation policies that offer full visibility.
Method 4: Apply via PowerShell script
PowerShell’s versatile command-line shell can automate registry edits with a few lines of code, making it ideal for IT teams that want to deploy quick changes at scale with native tools.
Use Cases: Apply the registry-based workaround to restore the classic context menu on one or multiple devices.
Prerequisites: Administrative privileges, PowerShell 5.1.
- Press Win + R, type powershell, and press Ctrl + Shift + Enter.
- Paste this script:
$base = "HKCU:\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32"
New-Item -Path $base -Force | Out-Null
Set-Item -Path $base -Value ""
Stop-Process -Name explorer -Force
Start-Process explorer.exe
- Press Enter.
- Test your context menu to verify changes.
Method 5: Deploy with Group Policy Preferences (for MSPs or enterprises)
Using Group Policy Preferences allows centralized deployment of registry changes across enterprise environments.
Use Cases: Centrally deploying the registry-based workaround to restore the classic context menu for users.
Prerequisites: An Active Directory Domain Services (AD DS) environment, access to Group Policy Management, and appropriate permissions to create, edit, and link GPOs.
- Press Win + R, type msc, and press Enter.
- In Group Policy Management, create a new GPO for the registry configuration and link it to the appropriate domain, OU, or site containing the target users.
- Right-click the new GPO and select Edit to open the Group Policy Management Editor.
- Navigate to User Configuration > Preferences > Windows Settings > Registry.
- Right-click Registry, select New > Registry Item, and configure the following settings:
- Action: Update
- Hive: HKEY_CURRENT_USER
- Key Path: Software\Classes\CLSID{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32
- Value Name: Leave blank to target the default value
- Value Type: REG_SZ
- Value Data: Leave blank
- Click Apply, then OK.
- Allow Group Policy to refresh normally, or run gpupdate /force on a client device to initiate a Group Policy refresh.
- After the policy has applied, restart Windows Explorer, sign out and back in, or restart the device so Explorer reloads the context menu configuration.
Verify that right-clicking an item displays the classic context menu by default.
Method 6: Roll back and restore the modern context menu item
You can run a Command Prompt command to delete the registry key created by the previous methods.
Use Cases: Removing the registry workaround to restore the default Windows 11 context menu.
Prerequisites: Administrative privileges.
- Open Command Prompt (Admin).
- Paste and run the following command: reg delete “HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}” /f
- Restart File Explorer or reboot the machine.
Method 7: Post-deployment validation after Windows updates
Lastly, set up a regular cadence for checking context menu behavior. Windows updates may change Explorer behavior, causing this registry-based workaround to stop working even if the registry key remains present. This means that your schedule needs to align with the manufacturer’s patch releases.
Regularly check if your changes still persist, and if not, reapply the method that worked for you.
Best practices for managing the “Show more options” context menu
Caution is necessary when modifying low-level settings, such as registry settings. Keep the following in mind when you restore the classic context menu in Windows 11:
| Method | Benefit | Outcome |
| Registry edit per user | Easy and reversible tweak | Reverts the right-click pop-up menu instantly |
| PowerShell or GPO deployment | Can be rolled out at scale safely | Consistent changes seen across endpoints |
| One-click .reg rollback | Straightforward recovery | Safe and simple reversals |
| Update validation | Maintains your configurations | Prevents disruptions to workplace productivity |
NinjaOne integration
Having a centralized dashboard lets you manage policies and automate registry changes from one place. Here’s how NinjaOne streamlines the process:
| Step | With NinjaOne |
| Preview the classic menu without changes. | Remote access and scripting capabilities allow administrators to manually verify context menu behavior on endpoints without applying permanent changes. |
| Restore the classic context menu via the Registry Editor. | Centralized scripting allows registry values related to the context menu to be modified across endpoints without manual local intervention. |
| Use a .reg file for one-click setup. | Script Library enables IT teams to deploy REG files to multiple devices instantly. |
| Apply via PowerShell script. | PowerShell automation feature helps roll out scripts and bulk changes. |
| Deploy with Group Policy Preferences (for MSPs or enterprises). | RMM-based automation can replicate registry-based configurations across managed endpoints without relying on native Windows Group Policy. |
| Roll back to the modern menu. | Custom rollback scripts can be executed centrally to remove registry-based changes and restore default Windows behavior. |
| Validate after Windows updates. | Scheduled scripts and monitoring alerts can be used to detect changes to registry-based configurations after Windows updates. |
Enforce the Windows 11 classic context menu with centralized control
IT teams can evaluate whether the classic context menu better supports their workflows and, when appropriate, apply the registry-based workaround using manual or centralized deployment methods. Testing and post-update validation can help identify compatibility issues and reduce deployment risk.
Related topics:
- How to Add or Remove Default New Context Menu Items in Windows 10
- How to Add “Take Ownership” to the Context Menu in Windows
- How to Add or Remove “Open in Windows Terminal” Expandable Context Menu in Windows 10
- How to Add or Remove “Pin to Start” from the Context Menu in Windows 11
- How to Add or Remove ‘Install CAB’ Context Menu in Windows 10
