By Andrew Armstrong 
File Explorer crashing is almost never File Explorer’s fault. It’s the shell, and the shell loads code from every application that has ever added a right-click menu item, a preview handler or a cloud-sync overlay. One badly-behaved extension takes the whole thing down.
The fix is isolation: work out which extension, then disable it. That’s much faster than the usual advice of reinstalling Windows.
Quick Facts
- Third-party shell extensions cause most crashes. Cloud sync, archivers and video codec packs are the usual suspects.
- Slow folders are usually a different problem. Folder type optimisation, not a crash.
- Restart Explorer from Task Manager rather than rebooting: it takes two seconds.
- Reliability Monitor names the faulting module, which usually identifies the culprit outright.
- Clearing Quick Access history fixes a surprising share of freezes on network shares.
First, restart it properly
Task Manager, find Windows Explorer, right-click, Restart. The taskbar disappears for a moment and comes back. If Explorer has vanished entirely and there’s no taskbar, use File, Run new task and enter explorer.exe.
Find out what’s actually crashing
Open Reliability Monitor with perfmon /rel, find the crash, and click View technical details. You want the faulting module, not the application name. The application will always say explorer.exe.
If the faulting module is a DLL belonging to a cloud sync client, an archiving tool or a codec pack, you’ve found it. If it’s a Windows DLL like shell32.dll, that usually means something else corrupted the shell rather than that Windows itself is broken.
Isolating a bad shell extension
The reliable method is disabling non-Microsoft extensions in bulk, confirming the crash stops, then re-enabling in halves until it returns. NirSoft’s ShellExView is the standard tool. It lets you sort by company and disable everything non-Microsoft in one action.
Quick Steps
- Download ShellExView and run it as administrator.
- Sort by Company. Select everything not from Microsoft.
- Disable them all, then restart Explorer.
- Use it normally. If the crashes stop, an extension was the cause.
- Re-enable half. Restart Explorer. Test again.
- Keep halving until you’ve found it, six or seven rounds identifies one extension out of a hundred.
Common culprits worth suspecting first: cloud storage clients (particularly two installed at once), archive tools that add context menus, codec packs providing thumbnail handlers, and older backup software.
If it’s slow rather than crashing
Folders that take forever to open, usually ones with lots of media. Are a different problem entirely. Windows optimises each folder for a content type, and a folder wrongly set to Pictures or Videos tries to generate thumbnails for everything in it.
Quick Steps
- Right-click the slow folder, Properties, Customize.
- Set “Optimize this folder for” to General items.
- Tick “Also apply this template to all subfolders”.
- Apply, and reopen the folder.
Also worth trying: File Explorer Options, uncheck “Show recently used files” and “Show frequently used folders”, then Clear the history. Quick Access rebuilding itself against unreachable network paths causes freezes that look like crashes, and this fixes it immediately.
If nothing above helps
# Repair the component store, then system files
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
# Rebuild the icon and thumbnail caches
taskkill /f /im explorer.exe
del /f /s /q /a %LocalAppData%\IconCache.db
del /f /s /q /a %LocalAppData%\Microsoft\Windows\Explorer\thumbcache_*.db
start explorer.exeA corrupted thumbnail cache produces crashes that only happen in certain folders, which is a confusing symptom until you know to look for it. The cache rebuilds automatically.
Glossary
| Term | What it means |
| Shell extension | Code from an application that adds context menus, previews or icon overlays to Explorer. |
| Faulting module | The specific DLL where a crash occurred. The useful field in crash details. |
| Folder type optimisation | A per-folder setting telling Explorer what kind of content to expect. |
| Quick Access | The recent files and frequent folders list. A common cause of freezes on network paths. |
| Thumbnail cache | A local database of generated previews. Corruption causes folder-specific crashes. |
| ShellExView | A free NirSoft utility for listing and disabling shell extensions. |
Frequently asked questions
Why does File Explorer crash only in certain folders?
Usually a corrupted thumbnail cache, or a preview handler failing on a specific file type in that folder. Clear the thumbnail cache first, then look at shell extensions relating to whatever media is in there.
Is it safe to disable all non-Microsoft shell extensions?
Yes, and it’s reversible. You’ll lose some right-click menu entries and icon overlays until you re-enable them. Nothing is uninstalled.
Why is File Explorer slow to open on network drives?
Frequently Quick Access trying to reach a path that no longer responds. Turn off recent files and frequent folders, clear the history, and see if it improves.
Will resetting Windows fix it?
It would, but it’s disproportionate. Isolating a shell extension takes twenty minutes and doesn’t cost you every installed application.
Gear We Recommend
Chasing an intermittent fault? These are the diagnostic bits we keep to hand.
Browse our General Tech Accessories picks on AmazonAs an Amazon Associate, TechyGeeksHome earns from qualifying purchases
Disclosure: this post may contain affiliate links. If you buy through one of them, we may earn a small commission at no extra cost to you. We only recommend products we’ve tested or genuinely rate.
Discover more from TechyGeeksHome
Subscribe to get the latest posts sent to your email.
