Why Right-Click Show More Options Resets After a Feature Update

Quick fix: The classic context menu setting is stored in HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32. Feature updates wipe this user-specific override. Re-apply via PowerShell: reg add “HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32” /f /ve then restart Explorer.

You set Windows 11 to use the classic full context menu (skipping the “Show more options” submenu) because the new compact menu was missing entries you needed. Right-click started showing the old-style menu directly. Then a Windows feature update reverted the registry override, and you’re back to the new compact menu with “Show more options” at the bottom.

What controls the classic context menu

Windows 11 added a curated “new” context menu with the most-used actions at the top and a Show more options entry that opens the legacy menu. The override that shows the legacy menu directly is a CLSID registry trick: setting a specific InprocServer32 value to empty tells Explorer to skip the new menu shim entirely.

The CLSID is {86ca1aa0-34aa-4e8b-a509-50c905bae2a2}. The override key is per-user (HKCU). Feature updates sometimes wipe user-specific shell registrations to ensure compatibility with the new build. After the wipe, the new context menu returns.

Method 1: Re-apply the override via PowerShell

1. Press Win + S, type PowerShell, right-click and choose Run as administrator.
2. Run:
   
   reg add “HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32” /f /ve
3. Restart Explorer to apply:
   
   taskkill /f /im explorer.exe

start explorer.exe
4. Right-click the desktop. The classic full context menu appears immediately.

This sets an empty default value for the InprocServer32 key, which Windows interprets as “use the legacy menu.” You can put both commands in a .ps1 script and run after every feature update if needed.

Method 2: Apply it persistently via Group Policy or registry deployment

For Pro/Enterprise environments where you want this for all users:

1. Create a .reg file with this content (save as classic-context-menu.reg):
   
   Windows Registry Editor Version 5.00
   
   (blank line)
   
   [HKEY_CURRENT_USER\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32]

@=””
2. Deploy via Group Policy preferences → Registry → Update; target the HKCU path so it applies per user.
3. Or run as a logon script: reg import classic-context-menu.reg.
4. The override applies on first logon and persists until removed.

The logon-script approach also handles the post-feature-update wipe automatically — every sign-in re-applies the override.

Method 3: Use a context menu modifier instead

For users who want more than just “legacy menu” — like reorganizing entries, hiding ones, adding custom commands — consider a context menu modifier app.

1. Download ShellMenuView (free, NirSoft) to see what’s registered in your context menu.
2. Download Easy Context Menu or OpenShell for editing.
3. Configure custom entries (copy path, take ownership, etc.) and save.
4. The tool writes the registry directly; changes survive feature updates because they’re not in the user-specific path that gets wiped.

This is more capable than just enabling the classic menu — you can tailor exactly what appears.

How to verify the fix worked

• Right-click any file. The full context menu appears immediately, including entries like Take Ownership, custom file type associations, and third-party tool entries.
• No Show more options entry at the bottom (because the menu is already the full one).
• Reboot and recheck. The classic menu persists.
• Open regedit and navigate to HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32 — the default value is empty.

If none of these work

If the new menu returns even after re-applying the override, an EXE-based context menu manager may be conflicting — uninstall any “Context Menu” software from Settings → Apps. Some antivirus tools also inject their own menu modifications that interact with this; check if your AV has a “context menu integration” toggle. For chronic resets after each Windows Update (not just feature updates), set up the logon script in Method 2 — it runs at every sign-in and corrects any reset.

Bottom line: The classic context menu is a single empty registry value. Re-apply with one PowerShell command after each feature update, or deploy via logon script for permanent stickiness.