File Explorer Not Responding on Windows 11? Fix Guide

Press Ctrl+Shift+Esc to open Task Manager, find Windows Explorer in the Processes list, right-click it, Restart. The taskbar disappears for a second then comes back — Explorer gets killed and respawned. This fixes most freezes immediately without rebooting. If Explorer is so frozen it’s not even in the Processes list, click File, Run new task, type explorer.exe, Enter. That launches a fresh process.

If it hangs again within a few minutes, the restart only treated the symptom. Something specific is dragging Explorer down — usually a corrupted thumbnail cache, a bad shell extension, or the Quick Access list trying to reach a folder that’s slow or offline. Occasionally what looks like a freeze is actually drag and drop not working — you try to move a file and nothing happens, so you assume Explorer hung when really the drag handler is broken. About 65% of these tickets fix in 5-10 minutes once you know which one to hit.

A real estate agent called us because her laptop’s File Explorer had been freezing for two weeks — gray “(Not Responding)” title bar for 20-30 seconds every time she opened it, right-click froze it for another minute. She had 4,000 listing photos to organize. We restarted Explorer, cleared the thumbnail cache — same pattern came back. Ran ShellExView and found three Dropbox-related context menu entries from an uninstall she’d done a year earlier. The uninstaller left orphaned shell extensions in the registry. Every right-click was making Explorer query a Dropbox service that no longer existed, hanging while it waited for a response that would never come. Disabled the three extensions, freezing stopped completely. Three minutes once we identified it.

Shell Extensions

If Explorer freezes specifically when you right-click, a shell extension is the cause. Almost guaranteed. (If your right-click isn’t working at all — not just in Explorer but everywhere — that’s a different problem with a different fix.) When you right-click a file, Explorer loads context menu items from every installed shell extension — Dropbox, OneDrive, 7-Zip, WinRAR, Adobe, antivirus programs, cloud storage apps. If any one of them hangs or crashes, the entire right-click freezes.

Download ShellExView from Nirsoft — free, portable, no installation. Run as Administrator. Go to Options menu, Hide All Microsoft Extensions. This narrows the list from hundreds of entries to maybe 20-50 third-party extensions. The Microsoft ones are safe, the third-party ones are where problems come from.

Right-click any suspect extension, Disable, restart Explorer, test. Common culprits in order of frequency: Dropbox shell extensions (especially orphaned ones left after uninstall), OneDrive extensions that hang waiting for sync state, Google Drive extensions, old versions of 7-Zip or WinRAR, Adobe extensions left after Creative Cloud uninstall, and antivirus “scan file” context menu items. Most users find the bad one within 3-5 tries. Once you find it, either leave it disabled permanently or properly uninstall the parent application.

The orphaned-extension pattern repeats constantly. Software uninstallers leave registry debris behind, and those debris entries become the silent cause of Explorer freezes months later. Any time Explorer is slow and you remember installing-then-removing cloud storage or archive utilities, shell extensions are the first thing to check.

Thumbnail Cache and Quick Access

Thumbnails are preview images Windows generates for every photo, video, and document. The cache grows over time and when it gets large or corrupted, Explorer hangs trying to read it. Clear it: Settings, System, Storage, Temporary files, check Thumbnails, Remove files. Or the old way — Win+R, type cleanmgr, choose C: drive, check Thumbnails, OK. For the most thorough cleanup, close every Explorer window, Win+R, type %USERPROFILE%\AppData\Local\Microsoft\Windows\Explorer\, delete all files starting with thumbcache_ and iconcache_. Some files might refuse to delete because Explorer is using them — restart Explorer first, then delete. The cache rebuilds automatically as you browse folders.

Quick Access is the section at the top of Explorer’s left sidebar showing recent files and pinned folders. If you’re trying to find a file like a screenshot that saved somewhere unexpected, Quick Access showing recent files is actually useful — when it works. If any pinned folder is slow to enumerate — a network share, an OneDrive folder, a USB drive that isn’t connected — the whole list hangs trying to display it. To fix: open Explorer, click the three-dot menu, Options, General tab, change “Open File Explorer to” from Quick access to This PC. In the Privacy section below, uncheck “Show recently used files” and “Show frequently used folders,” then click Clear next to “Clear File Explorer history.” Explorer launches faster and skips the whole Quick Access enumeration.

SFC/DISM and Event Viewer

If the easy fixes didn’t stick, corrupted system files might be the cause. Run these in Terminal as Administrator:

sfc /scannow — takes 10-15 minutes, scans protected system files and replaces corrupted ones. Then DISM /Online /Cleanup-Image /RestoreHealth — takes 15-30 minutes, downloads fresh components Windows can’t repair locally. Then sfc /scannow again — the second run has clean source files from DISM so it catches things the first couldn’t. Our SFC guide covers the full CBS.log analysis if SFC reports corruption it can’t fix.

Event Viewer tells you exactly which DLL crashed Explorer — no guessing. Win+R, eventvwr.msc, Windows Logs, Application, filter for Source “Application Error” and look for entries mentioning explorer.exe. Click the entry and the General tab shows the faulting module. If it’s ntdll.dll or shell32.dll, that’s core Windows corruption and SFC/DISM fixes it. If it’s a DLL you don’t recognize that’s not in System32, a third-party program is injecting into Explorer — Google the DLL name to find which app installed it.

Also check the Shell registry key if Explorer crashes with weird behavior. Navigate to HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon, find the Shell value. It should say explorer.exe and nothing else. If anything extra is appended after it, malware has hijacked your shell — clean it and run a full scan with Windows Defender plus Malwarebytes.

If your Start menu also acts up alongside Explorer, they share components and often fail together. Same goes for copy-paste not working — the clipboard runs through Explorer’s process, so when Explorer hangs, clipboard dies with it. If Explorer’s slowness correlates with random whole-system freezes, a dying hard drive is often the real culprit — Explorer is fine but it’s waiting on disk access that never comes. If the freezing started after a Windows Update, uninstalling the suspect KB is often the fastest path, and we can pull Event Viewer crash logs and identify the exact faulting module remotely in about fifteen minutes.