Windows 11 New Context Menu vs Legacy Shell Extensions

Updated February 2026 — Windows 11 24H2

Windows 11 introduced a completely redesigned right-click context menu, and it fundamentally changed how shell extensions work. If you are confused about why some of your right-click options disappeared, why you need to click “Show more options,” or how to manage extensions in this new system — this guide explains everything.

The Two Context Menu Systems

The New Menu (Windows 11 Default)

When you right-click a file in Windows 11, you see a compact, modern menu with:

• Cut, Copy, Paste, Rename, Delete (as icons at the top)
• Share, Compress to ZIP, Properties
• App-specific options from Windows Store apps
• “Show more options” at the bottom

This menu uses the new IExplorerCommand interface. Only extensions that implement this modern interface appear here.

The Classic Menu (“Show more options” / Shift+F10)

Clicking “Show more options” (or pressing Shift+F10) opens the full classic context menu with:

• All traditional IContextMenu handlers (7-Zip, WinRAR, Git, etc.)
• All the familiar items from Windows 10

Side-by-Side Comparison

Why Microsoft Changed the Context Menu

The classic context menu had several problems that Microsoft wanted to solve:

1. Performance: With 50+ extensions, the classic menu took 2-10 seconds to appear. Each IContextMenu handler ran QueryContextMenu() synchronously.

2. Inconsistency: Every app added items in different formats, positions, and styles. Some added icons, others did not. Some created submenus, others cluttered the root level.

3. Security: Legacy handlers run arbitrary code inside explorer.exe. A malicious shell extension had full access to the Explorer process.

4. Touch support: The classic menu was designed for mouse cursors, not touch screens. Items were too small and too close together for finger tapping.

The new menu loads faster because it does not run legacy extension code until you explicitly request it.

How to Bring Back the Full Classic Menu

If you prefer the old-style menu that shows all extensions immediately:

Method 1: Registry (Permanent)

reg add "HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32" /f /ve

Restart Explorer or sign out. To revert:

reg delete "HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}" /f

Method 2: Keyboard Shortcut (Per-Use)

• Hold Shift while right-clicking to go directly to the classic menu
• Or press Shift+F10 after selecting a file

Method 3: Via Settings App (24H2)

In Windows 11 24H2, Microsoft added an option in one of the Settings pages under Personalization to determine the default context menu style.

Managing Extensions Across Both Menus

Extensions That Appear in the New Menu

These use IExplorerCommand and appear immediately on right-click:

• Windows shell verbs (Open, Edit, Print)
• OneDrive (Share, Free up space, Always keep on this device)
• Windows Defender (Scan with Microsoft Defender)
• Some Microsoft 365 apps
• Apps explicitly updated for Windows 11

Extensions That Only Appear in the Classic Menu

All legacy IContextMenu handlers:

• 7-Zip, WinRAR, PeaZip
• TortoiseGit, TortoiseSVN
• NVIDIA Control Panel
• Most antivirus “Scan with…” options
• Most developer tools

Making Legacy Extensions Appear in the New Menu

Software developers can register their extensions for the new menu using IExplorerCommand + a Sparse Package. Some tools have updated for Windows 11:

Performance Comparison

We benchmarked both menu systems on a system with 45 non-Microsoft shell extensions:

The performance difference is dramatic because the new menu does not execute any legacy extension code until you click “Show more options.”

Windows 11 24H2 Changes

The 24H2 update brought several improvements to the context menu system:

1. Faster “Show more options”: The transition to the classic menu is now nearly instant.
2. Stricter DLL validation: Unsigned extensions may show a security warning.
3. New API capabilities: IExplorerCommand now supports submenus and dynamic icons.
4. Better touchscreen support: Menu items are larger with more spacing.

Frequently Asked Questions

Q: Can I have some extensions in the new menu and others only in the classic menu? A: This is determined by the extension developer, not the user. Extensions must implement IExplorerCommand to appear in the new menu.

Q: If I restore the classic menu, do I lose the new menu’s features? A: Yes — restoring the classic menu replaces the new menu entirely. You get the old Windows 10-style full menu with all its extensions (and its slowness if you have many).

Q: Why did Microsoft not just make an option to choose? A: In Windows 11 24H2, they added a partial option. However, the core issue is that legacy extensions have an inherent performance cost that cannot be eliminated without skipping their code.

Q: Do disabled shell extensions still slow down the new menu? A: No. Disabled extensions are not loaded by either menu system. They have zero performance impact.