Windows 11 Context Menu Slow? 15 Fixes That Actually Work (2026)

Updated March 2026 for Windows 11 24H2

Right-click a file, wait three to ten seconds, then hit “Show more options” and wait again. That second pause is where most of the pain lives. It is almost never fixed by buying more RAM.

These 15 fixes go from quick checks to deeper cleanup. Stop when the menu feels normal again.

Why Windows 11 Right-Click Feels Slow

Windows 11 uses two menus:

1. Modern menu (first right-click): short list, mostly built-in actions.
2. Legacy menu (“Show more options” or Shift+F10): loads classic IContextMenu shell extensions.

That legacy path walks every registered handler before the menu appears:

• Cloud sync (OneDrive, Dropbox, Google Drive)
• Antivirus “Scan with…” entries
• GPU control panels (NVIDIA, Intel)
• Archive tools (WinRAR, 7-Zip)
• Dev tools (Git, Tortoise*, VS Code helpers)

Each slow handler can add tens to hundreds of milliseconds. Stack twenty of them and you get multi-second freezes. MenuShowDelay only changes submenu hover delay; it will not fix whole-menu lag.

Quick Fixes (Under 2 Minutes)

Fix 1: Restart Windows Explorer

1. Ctrl + Shift + Esc
2. Select Windows Explorer
3. Click Restart

This clears stuck loads. If lag returns after a few clicks, keep going.

Fix 2: Turn Off Cloud Context Menus (or Pause Sync)

Retest on a local folder. Pausing sync alone often proves the cause in under a minute.

Fix 3: Prefer “Stream Files” Over Full Mirrors

Mirrored cloud trees keep more overlay and status work in Explorer.

In Google Drive or OneDrive settings, pick stream / on-demand files if you do not need everything offline.

Intermediate Fixes (5-10 Minutes)

Fix 4: Binary-Search With ShellExView

1. Get ShellExView (64-bit).
2. Run as Administrator.
3. Options → Hide All Microsoft Extensions.
4. Disable everything left (select all, F7).
5. Restart Explorer and test.
6. Re-enable half, restart, test. Repeat until one extension brings the lag back.

Aim to keep only handlers you actually use. Thirty unused third-party entries is already too many for a snappy menu.

Fix 5: Restore the Classic Full Menu

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

You get one menu instead of the two-step path. Undo with:

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

Fix 6: Drop GPU Desktop Context Menu Entries

NVIDIA: Control Panel → Desktop → uncheck Add Desktop Context Menu.

Intel: Graphics Command Center → settings related to desktop context menu → disable.

These rarely justify the cold-start cost if you never use them.

Advanced Fixes (15+ Minutes)

Fix 7: Remove Orphaned Registry Handlers

Handlers whose DLL path is gone still make Explorer wait. Walk the cleanup steps and PowerShell checks in remove shellex issues, or delete obvious dead keys after exporting a backup.

Fix 8: SFC and DISM

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Use this when Explorer itself looks damaged, not as the first step for a single bad Dropbox DLL.

Fix 9: Rebuild Icon and Thumbnail Caches

Corrupt caches can make folders feel stuck even when the menu code is fine:

taskkill /f /im explorer.exe
Remove-Item "$env:LOCALAPPDATA\Microsoft\Windows\Explorer\thumbcache_*.db" -Force -ErrorAction SilentlyContinue
Remove-Item "$env:LOCALAPPDATA\IconCache.db" -Force -ErrorAction SilentlyContinue
start explorer.exe

Fix 10: Scan for Fake Shell Extension Files

Unsigned shellex.dll / shellex.exe under Downloads, Temp, or AppData is a red flag. Follow Is shellex.dll a virus? and use a second engine such as Malwarebytes if Defender alone is inconclusive.

Fix 11: Clean Boot Test

1. Win + R → msconfig
2. Services → hide Microsoft services → disable the rest (or use a selective set)
3. Startup apps: disable nonessential entries in Task Manager
4. Reboot and test right-click

Fast in clean boot means a third-party service or extension. Re-enable in groups to find which package.

Fix 12: Update or Uninstall the Named Offender

Once ShellExView names a DLL, update that product. If the vendor abandoned Win11 support, uninstall it and remove leftovers with Revo Uninstaller so registry handlers do not linger.

Fix 13: Limit Icon Overlays

Windows only shows a limited number of overlay slots. Dropbox + Google Drive + OneDrive + Tortoise* fight for them and add work on every folder paint. Disable overlays you do not need in each app’s preferences, or disable those handlers in ShellExView.

Fix 14: Check Event Viewer for Faulting Modules

Event Viewer → Windows Logs → Application. Look for explorer.exe errors around the time you right-click. The faulting module name is often the exact DLL to disable.

Fix 15: Compare Against Known Slow Extensions

Cross-check your ShellExView list with Top 10 slow shell extensions and the Explorer not responding guide for crash-style hangs. For 24H2-specific breakage, see 24H2 right-click bug fixes.

Rough Timing After Cleanup

These are order-of-magnitude expectations on a healthy SSD PC, not lab guarantees:

FAQ

Q: Do these steps apply to Windows 10? A: Yes for ShellExView, orphan cleanup, and cloud/AV menus. The classic-menu CLSID tweak is Windows 11 specific.

Q: Can I disable every shell extension? A: You can disable third-party ones. Leave Microsoft entries unless you know what they do.

Q: How often should I revisit this? A: After big app installs, or every few months if you install a lot of desktop software.

Q: Will more RAM fix it? A: No. This is blocking work inside Explorer, not a memory shortage.

Five-Minute Path Most People Need

1. Pause cloud sync and retest.
2. ShellExView → hide Microsoft → disable unused third-party → restart Explorer.
3. Re-enable only what you miss.
4. Optional: classic menu registry tweak.

That sequence fixes most “slow right-click on Windows 11” reports without touching SFC.