File Explorer crashing in Windows 11 — where the file manager window disappears, the taskbar briefly vanishes, and then everything restores — is usually more annoying than serious. Windows restarts Explorer automatically after each crash, so the impact is a brief interruption rather than data loss. The problem is when it happens repeatedly, every few minutes, making File Explorer essentially unusable. For a broader walkthrough, our Complete Guide to Fixing Windows, Browser, and Software Errors is a good next read.
The two most common causes by far: a shell extension installed by a third-party application is crashing Explorer, or the Quick Access navigation panel has accumulated corrupted entries. Both are fixed without touching any drivers or doing anything drastic.
Quick Access fix first — try this before anything else: Open File Explorer → View → Options → Clear File Explorer history. This removes the Quick Access cached data. If crashes were happening specifically when File Explorer opened or when clicking Quick Access, this resolves it immediately and takes 20 seconds.
Understanding Shell Extensions
Shell extensions are DLLs that other applications install into Windows Explorer to add functionality: right-click menu options, file preview handlers, thumbnail generators, and custom file icons. Cloud storage clients (Dropbox, Google Drive overlay icons), antivirus software (right-click scan), PDF readers (PDF preview in the preview pane), and many other applications add shell extensions.
When a shell extension has a bug, conflicts with the current Windows version, or becomes corrupted, it crashes Explorer every time Explorer tries to use it — which can happen when you right-click a file, open a folder containing a file type that extension handles, or open the Preview Pane with a specific file selected. The crash and restart cycle is Explorer failing, the shell extension being temporarily unloaded, and Explorer restarting without it — until Explorer loads the extension again and crashes again.
Fix 1: Find the Offending Shell Extension
The free tool ShellExView from NirSoft (nirsoft.net) lists every shell extension installed on the system with clear colour coding: Microsoft extensions in pink, third-party in white. Disable non-Microsoft shell extensions systematically:
- Download and open ShellExView (no installation needed — runs directly)
- Sort by “Company” to separate Microsoft from third-party entries
- Select all non-Microsoft (white) extensions → right-click → Disable Selected Items → restart Explorer (or the machine)
- If Explorer is now stable: re-enable extensions in groups → restart → test after each group
- When crashes return after enabling a specific extension, that extension’s parent application is the cause
Update the application that installed the crashing extension, or leave that specific extension disabled. The application still works normally — only its Explorer integration is disabled. For cloud storage clients (Dropbox, OneDrive, Google Drive file overlay icons), the overlay extensions are cosmetic features that can be disabled without affecting sync functionality.
Fix 2: Clear the Navigation Panel Corruption
Quick Access stores shortcuts to frequently accessed folders and recent files in a local database. When this database references folders that no longer exist — network shares that were disconnected, external drives removed without ejecting, deleted folders — Explorer sometimes crashes when loading Quick Access because it can’t handle the broken references.
More thorough Quick Access clear: close all File Explorer windows → Win + R → navigate to %appdata%MicrosoftWindowsRecentAutomaticDestinations → select all files → delete. Do the same for %appdata%MicrosoftWindowsRecentCustomDestinations. These folders store the Quick Access and Jump List data. Explorer rebuilds them from scratch on next launch. This is more comprehensive than the history clear in View → Options and resolves cases where that simpler clear didn’t work.
Fix 3: The Preview Pane as a Crash Source
The Preview Pane shows file content when a file is selected. Each file type’s preview is handled by a different preview handler — the PDF preview handler loads when a PDF is selected, the Office document preview handler loads for Word/Excel files, and so on. When a specific preview handler has a bug or isn’t correctly installed, selecting a file of that type in Explorer triggers a crash.
Test: View → Show → Preview Pane → disable it → browse through the folders where crashes were occurring. If Explorer becomes stable, a preview handler is the cause. Re-enable the Preview Pane and click through different file types one at a time: click a PDF, wait; click a Word document, wait; click an image, wait. When Explorer crashes after selecting a specific file type, that file type’s preview handler needs updating (update the associated application) or the preview can be disabled for that file type specifically through the Default Programs settings.
Fix 4: SFC and DISM
Corrupted Windows system files that Explorer depends on cause crashes that don’t trace to any specific shell extension or file type. SFC repairs these files:
DISM /Online /Cleanup-Image /RestoreHealthThen:
sfc /scannowFrom an administrator Command Prompt. If SFC reports “found corrupt files and repaired them” — system file corruption was involved. Restart after both commands complete and test Explorer stability.
Fix 5: Identify the Crash With Event Viewer and Reliability Monitor
When shell extension testing and Quick Access clearing haven’t resolved the crashes, Event Viewer provides the specific crash details that guide the next step.
Event Viewer → Windows Logs → Application → look for “Application Error” entries timestamped at each crash. The “Faulting module name” field names the DLL that caused the crash. If it’s a third-party DLL: match it to the installed application that owns it and update or remove that application. If it’s a Windows DLL: run SFC. If it’s shell32.dll or ntdll.dll: these system libraries crash when something calls them incorrectly — the true cause is elsewhere in the stack.
Reliability Monitor (search “View reliability history” in Start) plots crashes on a calendar view, making it easy to see when Explorer crashes started and what changed around that time — software installations, Windows updates, or configuration changes appear on the same timeline.
Fix 6: OneDrive and Cloud Storage Shell Extensions
OneDrive, Dropbox, and Google Drive all install shell extensions to display sync status icons on files (checkmarks, blue cloud icons, etc.). These overlay extensions are a particularly common source of Explorer crashes because they actively modify the display of every file in the Explorer window — meaning they run on every folder navigation, not just on specific user actions.
If a cloud storage client was recently updated or if crashes started after installing a cloud service: disable those specific overlay extensions in ShellExView (look for extensions with names containing “overlay,” “icon,” or the cloud service name). Alternatively: uninstall the cloud storage client → restart → reinstall the latest version. Fresh installation of the latest version resolves crashes caused by version mismatches between the cloud client and the current Windows 11 version.
Explorer on Network Locations
File Explorer crashing specifically when browsing network shares or mapped drives is a different failure mode from general Explorer crashes. Network file access failures — timeouts, unexpected disconnections from a file server, protocol errors — can propagate up to Explorer and crash it when it’s trying to display network content.
If crashes happen only when navigating to network locations: check whether the network location is actually accessible (ping the server from Command Prompt). Mapped drives that point to servers no longer available cause Explorer to hang and eventually crash while trying to display the drive contents. Disconnect unavailable mapped drives: File Explorer → This PC → right-click each mapped drive → Disconnect. Reconnect them only when the server is available. Also check: Quick Access pinned shortcuts to network folders cause crashes at Explorer startup if those network locations are unreachable — clear Quick Access (Fix 2) to remove the problematic pinned network locations.
Our guide on Windows 11 taskbar not working covers the Explorer crashes that affect the taskbar alongside File Explorer — both use the same explorer.exe process and the same shell extension infrastructure, so a fix for one often resolves the other. For persistent system file corruption that SFC can’t fix in normal mode, our Windows 11 not booting guide covers running SFC offline from the recovery environment. Microsoft’s File Explorer documentation covers the Shell Extension Manager built into Windows 11 22H2 and later which provides a Microsoft-supported alternative to ShellExView for disabling shell extensions.
Crashes After Specific Actions vs Random Crashes
The pattern of crashes determines the diagnosis approach:
Explorer crashes when right-clicking files: A right-click context menu shell extension is the cause. The context menu loads all registered context menu handlers when you right-click. Disabling shell extensions via ShellExView specifically in the “Context Menu” extension type narrows the suspect list. Right-click handlers are the most common shell extension crash source because they load on demand and many applications add them without the user being aware.
Explorer crashes when opening specific folder types: The folder type’s shell extension (namespace extension or custom folder view handler) is the issue. This is less common but appears with some version control system integrations (Git, SVN overlays) and certain security software that scans directories on open.
Explorer crashes on startup before the desktop appears: A startup shell extension is crashing before Explorer can display the desktop. This is the most disruptive pattern — it prevents normal Windows use. Boot into Safe Mode to access ShellExView and disable all third-party shell extensions. Then restart normally and test which specific extension caused the startup crash.
Random crashes with no consistent trigger: Hardware issues (failing RAM, storage errors) cause random crashes that look like software problems. Run Windows Memory Diagnostic and CrystalDiskInfo before spending more time on software shell extension analysis — if hardware is failing, software fixes won’t provide lasting improvement.
Windows 11 22H2+ Shell Extension Management
Windows 11 version 22H2 introduced a built-in Shell Extension Manager accessible directly from File Explorer. Open File Explorer → click the three-dot menu (…) at the top → Settings → Open in separate window → not there. The built-in management is actually in a different location: Settings → Personalisation → Taskbar → then it’s not there either. The built-in tool is specifically in Windows 11 22H2 and later under a Windows Settings deep link. For most users, NirSoft’s ShellExView remains the practical tool for shell extension management regardless of Windows 11 version, because it provides a cleaner interface and more detailed information about each extension than the built-in alternative.
GPU Driver and File Explorer Rendering
File Explorer uses Windows’ compositing engine (DWM — Desktop Window Manager) for its interface rendering. When the GPU driver has a bug in a specific rendering path that DWM uses, Explorer can crash during certain visual operations — particularly when thumbnail rendering for large image folders, when animating folder transitions, or when hardware-accelerated effects are applied to Explorer windows.
The diagnostic: if Explorer crashes specifically when entering folders with many images or when scrolling quickly through image thumbnails, GPU rendering is the likely cause. Update the GPU driver from the manufacturer’s website. If the crashes are caused by a specific GPU driver version, the driver release notes often mention Explorer or shell stability improvements in the changelog. NVIDIA’s release notes at nvidia.com/drivers and AMD’s at amd.com/support document specific bug fixes per driver version.
Large Folder Sizes and Thumbnail Generation
File Explorer generates thumbnails for image and video files in any folder view. When a folder contains thousands of files with thumbnails to generate — particularly large video files where the first frame needs to be decoded for the thumbnail — Explorer spends significant time and memory generating them. On machines with limited RAM or slow storage, this thumbnail generation can consume enough resources to cause Explorer to crash.
Mitigation: change the folder view to “List” or “Details” rather than “Large icons” or “Extra large icons” for folders with many image or video files. Details view doesn’t generate thumbnails and dramatically reduces memory and CPU usage for large folders. Also: File Explorer → Options → View tab → check “Always show icons, never thumbnails” — this disables thumbnail generation system-wide, which prevents the crash-causing thumbnail rendering overhead at the cost of icons replacing all thumbnails throughout the system.
Search Integration Causing Explorer Crashes
File Explorer’s search functionality integrates with Windows Search. When the Windows Search index is rebuilding, corrupted, or has service issues, Explorer may crash when you click the search box within a File Explorer window — because the search initialisation fails and the failure propagates to Explorer rather than showing a graceful error.
Check Windows Search status: search “Indexing Options” in Start → look at the status message. If it shows an error or “Indexing speed is reduced due to user activity,” the index has issues. Rebuild the index: Advanced → Rebuild. During the rebuild, avoid using File Explorer’s search feature — wait for the rebuild to complete and the item count to stabilise before searching in Explorer. If Explorer crashes specifically when clicking the search box, this is the cause. If this sounds familiar, Microsoft Word Keeps Crashing is worth a look.
