Windows Explorer Not Responding When Right Clicking – 2026 Complete Fix Guide

Updated March 2026 — Covers Windows 11 24H2, Windows 10 22H2

You right-click a file expecting the context menu, but instead you get:

• A spinning blue circle
• “Explorer.exe is not responding” error
• Complete desktop freeze for 10-30 seconds
• Sometimes a full Explorer restart

This is one of the most common Windows frustrations, and shell extensions are the culprit in 90% of cases. This guide walks you through every possible cause and solution, from quick fixes to deep system repair.

Quick Diagnosis: What’s Actually Happening?

When you right-click, Windows must:

1. Load all registered Context Menu Handlers (shell extensions)
2. Execute each one’s QueryContextMenu() function
3. Merge results into a single menu
4. Render the menu on screen

The problem: If ANY handler freezes, crashes, or times out, the entire process blocks.

Common Error Messages

Immediate Relief: 3 Ways to Unfreeze Explorer

Method 1: Wait It Out (15-30 seconds)

Most freezes are network timeouts. Cloud storage extensions (OneDrive, Dropbox, Google Drive) wait for server responses that never come. Default Windows timeout is 30 seconds.

When to use: If you’re on a slow/unstable connection.

Method 2: Restart Explorer via Task Manager

1. Press Ctrl + Shift + Esc
2. Find Windows Explorer under Processes
3. Click Restart (bottom-right button)

When to use: Immediate relief, but problem will return on next right-click.

Method 3: Command Line Kill

If Task Manager is also frozen:

1. Press Ctrl + Alt + Delete → Task Manager
2. File → Run new task → type cmd → check “Create with admin privileges”
3. Paste these commands:

taskkill /f /im explorer.exe
timeout /t 2 /nobreak >nul
start explorer.exe

When to use: When entire UI is unresponsive.

The Real Fix: Identifying the Problematic Extension

Step 1: Check Event Viewer Logs

Windows logs Explorer crashes. Let’s find them:

1. Press Win + X → Event Viewer
2. Navigate to: Windows Logs → Application
3. Look for Error entries with Source = Application Error
4. Check for Faulting module name — this tells you which DLL crashed Explorer

Example log entry:

Faulting application name: explorer.exe
Faulting module name: nvcontext.dll
Exception code: 0xc0000005

This means NVIDIA’s context menu handler crashed Explorer.

Step 2: Use ShellExView (Recommended Method)

NirSoft ShellExView is the gold standard tool.

The Binary Search Method:

1. Download ShellExView (64-bit version)
2. Run as Administrator
3. Hide Microsoft extensions: Options → Hide All Microsoft Extensions
4. Select all remaining extensions (Ctrl+A)
5. Disable half (F7)
6. Restart Explorer: File → Restart Explorer
7. Test right-click

If it works: The culprit is in the disabled half. Re-enable the good half, disable half of the remaining. If it fails: The culprit is in the enabled half. Disable half of those.

Repeat until you find the single extension causing the freeze.

Step 3: Process Monitor Deep Dive

For intermittent freezes, use Process Monitor from Sysinternals:

1. Download from Microsoft
2. Run as Admin
3. Add filters:
   • Process Name is explorer.exe
   • Operation is Load Image
   • Result is not SUCCESS
4. Right-click a file until freeze occurs
5. Stop capture (Ctrl+E)
6. Look for NAME NOT FOUND or ACCESS DENIED on DLL files

These indicate orphaned extensions pointing to deleted files.

The 7 Most Common Causes (And Fixes)

Cause 1: Orphaned Shell Extensions

What it is: Uninstalled software left registry entries pointing to non-existent DLL files.

How to identify:

# List broken shell extensions
Get-ChildItem "Registry::HKCR\*\shellex\ContextMenuHandlers" -EA SilentlyContinue | ForEach-Object {
    $clsid = $_.GetValue("")
    $dllPath = "Registry::HKCR\CLSID\$clsid\InprocServer32"
    if (Test-Path $dllPath) {
        $dll = (Get-ItemProperty $dllPath -EA SilentlyContinue)."(default)"
        if ($dll -and !(Test-Path $dll)) {
            Write-Host "ORPHANED: $($_.PSChildName) → $dll" -ForegroundColor Red
        }
    }
}

The Fix:

1. In ShellExView, sort by File Version column
2. Look for blanks (no version = file missing)
3. Right-click → Delete Selected Items
4. Restart Explorer

Cause 2: Network Drive Disconnections

What it is: Mapped network drives (Z:, Y:, etc.) that are offline cause timeouts when Explorer checks file properties.

How to identify:

• Open File Explorer
• Look for red X on drive icons
• Or run: net use

The Fix:

# Remove all disconnected network drives
net use * /delete /y

# Or remove specific ones
net use Z: /delete

Also check printer connections — offline network printers cause the same issue:

Get-Printer | Where-Object { $_.Type -eq "Connection" -and $_.Status -ne "Normal" } | Remove-Printer

Cause 3: Cloud Storage Network Timeouts

What it is: OneDrive, Dropbox, or Google Drive waiting for server responses.

Affected DLLs:

• OneDriveShellExt.dll
• dropboxext.dll
• googledrivesync64.dll

The Fix:

Option A: Disable context menu (keeps sync)

1. OneDrive → Settings → Sync and backup → Disable “File collaboration”
2. Dropbox → Settings → Sync → Disable “Show Dropbox badges”
3. Google Drive → Settings → Disable right-click menu

Option B: Disable network adapters temporarily

# Disable Wi-Fi
disable-netadapter -name "Wi-Fi" -confirm:$false

# Test right-click (should be instant)

# Re-enable
enable-netadapter -name "Wi-Fi"

Option C: Set firewall rules to block cloud apps temporarily

Cause 4: Antivirus Real-Time Scanning

What it is: Antivirus hooks into right-click to offer “Scan this file” but performs deep scans.

Affected DLLs:

• nsePh.dll (Norton)
• kxhkcreg.dll (Kaspersky)
• mcctxmngr.dll (McAfee)
• ashShell.dll (Avast)
• bdShellExt.dll (Bitdefender)

The Fix:

Each AV has a setting to disable context menu integration. If you can’t find it:

1. Open ShellExView
2. Disable your AV’s context menu handler
3. Keep real-time protection enabled (different component)

Note: Disabling context menu does NOT disable antivirus protection!

Cause 5: Corrupted Icon Cache / Thumbnails

What it is: Windows tries to generate thumbnails but the handler crashes.

How to identify:

• Freeze only happens in folders with images/videos
• Explorer.exe CPU usage spikes

The Fix:

# Stop Explorer
taskkill /f /im explorer.exe

# Delete thumbnail cache
Remove-Item -Path "$env:LOCALAPPDATA\Microsoft\Windows\Explorer\thumbcache_*.db" -Force

# Clear icon cache
Remove-Item -Path "$env:LOCALAPPDATA\IconCache.db" -Force

# Restart Explorer
start explorer.exe

Cause 6: Windows Search Indexer Corruption

What it is: Search integration in context menu hangs when index is corrupted.

How to identify:

• Freeze on right-click in large folders
• SearchIndexer.exe high CPU

The Fix:

# Stop search service
Stop-Service WSearch -Force

# Delete and rebuild index
Remove-Item "$env:ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" -Force

# Restart service
Start-Service WSearch

# Wait for rebuild (can take hours on large drives)

Disable search in context menu:

1. Registry: HKEY_CLASSES_ROOT\Directory\shell\find
2. Rename LegacyDisable to disable

Cause 7: GPU Driver Conflicts

What it is: NVIDIA and Intel graphics extensions conflict when both installed.

Affected DLLs:

• nvcontext.dll (NVIDIA)
• igfxDTCM.dll (Intel)
• igfxpph.dll (Intel legacy)

The Fix:

Disable one or both:

NVIDIA:

1. NVIDIA Control Panel → Desktop → uncheck “Add Desktop Context Menu”

Intel:

1. Intel Graphics Command Center → Settings → Disable context menu

Both in ShellExView:

• Find nvcontext.dll → F7 to disable
• Find igfxDTCM.dll → F7 to disable

Advanced: The Nuclear Registry Cleanup

If you’ve tried everything, perform a complete shell extension audit:

Step 1: Backup Registry

reg export "HKCR\*\shellex" C:\shellex-backup.reg
reg export "HKCR\Directory\shellex" C:\shellex-directory-backup.reg

Step 2: Export Current Extensions

Get-ChildItem "Registry::HKCR\*\shellex\ContextMenuHandlers" -EA SilentlyContinue | 
    Select-Object PSChildName, @{N="CLSID";E={$_.GetValue("")}} |
    Export-Csv C:\current-extensions.csv -NoTypeInformation

Step 3: Safe Mode Test

1. Press Win + R → type msconfig → Enter
2. Boot tab → check “Safe boot” → Minimal
3. Restart
4. Test right-click in Safe Mode

If it works in Safe Mode: Guaranteed third-party extension problem. If it still fails: Windows system file corruption.

Step 4: Clean Boot (Selective Startup)

1. msconfig → Services tab
2. Check “Hide all Microsoft services”
3. Click “Disable all”
4. Startup tab → Open Task Manager → Disable all startup items
5. Restart
6. Test right-click
7. Re-enable services in groups of 5 until problem returns

Windows 11 Specific Issues

The “Show More Options” Delay

Windows 11’s new context menu doesn’t load legacy extensions, but clicking “Show more options” triggers the old menu with all extensions.

Fix: Disable new menu entirely (get old menu back):

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

# Restart Explorer
taskkill /f /im explorer.exe && start explorer.exe

To restore Windows 11 menu:

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

Windows 11 24H2 Specific Bug

Some users report right-click freezes after 24H2 update due to XAML Islands integration.

Temporary workaround:

# Disable XAML context menu animations
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced" /v "UseXamlContextMenu" /t REG_DWORD /d 0 /f

Malware Disguised as Shell Extensions

Some malware installs itself as a shell extension to:

• Monitor all file operations
• Inject ads into context menus
• Steal data from right-clicked files

Warning Signs

• Extension with generic name: shellex.dll, context.dll, shellmenu.dll
• Located in AppData\Local\Temp or Downloads
• No digital signature
• Unknown publisher
• Recently installed (check timestamp)

How to Check

1. Properties → Digital Signatures tab
2. VirusTotal scan: Upload the DLL to virustotal.com
3. Google the filename + “malware”

Common Malicious Names

Prevention: Keep Explorer Fast

Monthly Maintenance Script

Save this as Maintain-Explorer.ps1 and run monthly:

# Check for broken shell extensions
$broken = Get-ChildItem "Registry::HKCR\*\shellex\ContextMenuHandlers" -EA SilentlyContinue | Where-Object {
    $clsid = $_.GetValue("")
    $dllPath = "Registry::HKCR\CLSID\$clsid\InprocServer32"
    if (Test-Path $dllPath) {
        $dll = (Get-ItemProperty $dllPath -EA SilentlyContinue)."(default)"
        $dll -and !(Test-Path $dll)
    }
}

if ($broken) {
    Write-Host "Found $($broken.Count) broken extensions. Run ShellExView to clean." -ForegroundColor Yellow
    $broken | Select-Object PSChildName
} else {
    Write-Host "No broken extensions found." -ForegroundColor Green
}

# Check extension count
$count = (Get-ChildItem "Registry::HKCR\*\shellex\ContextMenuHandlers" -EA SilentlyContinue).Count
Write-Host "Total context menu handlers: $count" -ForegroundColor Cyan
if ($count -gt 40) {
    Write-Host "Consider reducing to under 40 for optimal performance." -ForegroundColor Yellow
}

Installation Best Practices

1. Always choose “Custom” install
2. Uncheck “Add to context menu” when offered
3. Use portable versions when available (no shell integration)
4. Check after updates — they often re-enable extensions

FAQ: Explorer Not Responding

Q: Will disabling shell extensions break my programs? A: No. Shell extensions are optional UI features. The programs work normally, you just lose right-click shortcuts.

Q: Why does right-click work on desktop but not in folders? A: Desktop and folders use different extension registry keys. Desktop uses Directory\Background, folders use Directory and *.

Q: Can I right-click in Task Manager to restart Explorer? A: Yes! Task Manager’s right-click menu is separate and won’t freeze even if Explorer is broken.

Q: Does this affect Windows 10 too? A: Yes, all fixes apply to Windows 10. The registry paths are identical.

Q: How do I know if it’s fixed without rebooting? A: Restarting Explorer (taskkill /f /im explorer.exe && start explorer.exe) is sufficient to test changes.

Q: What if I disable the wrong extension? A: Just re-enable it in ShellExView and restart Explorer. Changes are instantly reversible.

Q: Can a shell extension cause BSOD? A: Rarely. Most run in user mode (explorer.exe), so they crash Explorer, not the whole system. Kernel-mode filters (some antivirus) can cause BSODs.

When All Else Fails: System Repair

DISM and SFC

# Run as Admin
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

In-Place Upgrade (Keep files)

1. Download Windows 11 ISO from Microsoft
2. Mount ISO, run setup.exe
3. Choose “Keep personal files and apps”
4. This repairs system files without data loss

Reset Windows (Last Resort)

Settings → System → Recovery → Reset this PC

• “Keep my files” — removes apps, keeps data
• “Remove everything” — clean slate