How to Fix Windows File Explorer Crashing and Restarting
Published 2026-10-16 · Marion Remote Fix
File Explorer crashes when you open it, freezes when navigating to certain folders, or the entire taskbar disappears and reappears as explorer.exe restarts itself. Windows File Explorer is not just the file browser — it is also responsible for the taskbar, Start menu, desktop icons, and system tray. When explorer.exe crashes, all of these elements disappear momentarily before Windows restarts the process. Frequent crashes make the computer feel unstable and interrupt your work. The causes range from corrupted shell extensions and bad thumbnails to system file damage.
Restart File Explorer cleanly
Before diagnosing deeper issues, try a clean restart of the explorer.exe process:
- Press Ctrl+Shift+Esc to open Task Manager. Find Windows Explorer in the Processes tab. Right-click it and select Restart. This kills and restarts explorer.exe cleanly, which clears any temporary state that may be causing the crash
- If File Explorer crashes so quickly that you cannot use it at all, open Task Manager, click File, Run New Task, and type cmd. From the command prompt you can navigate the file system and apply fixes without relying on File Explorer
Clear File Explorer history and cache
Corrupted history data and thumbnail caches are among the most common causes of File Explorer crashes:
- Clear history: Open File Explorer Options (search for it in the Start menu or access it through Control Panel, Appearance and Personalization). On the General tab, under Privacy, click Clear next to Clear File Explorer history. Also uncheck Show recently used files in Quick Access and Show frequently used folders in Quick Access. Click Apply
- Clear thumbnail cache: Open Disk Cleanup (search for it in the Start menu), select your C: drive, check Thumbnails, and click OK. Or from Command Prompt as administrator, run: del /f /s /q %LocalAppData%\Microsoft\Windows\Explorer\thumbcache_*.db followed by a restart. Corrupted thumbnail database files cause File Explorer to crash when it tries to generate previews for certain files
- Disable Quick Access: If crashes happen specifically when File Explorer opens (before you navigate anywhere), Quick Access may be pointing to a corrupted or inaccessible location. In File Explorer Options, General tab, change Open File Explorer to from Quick Access to This PC. This skips the Quick Access scan entirely on launch
Check for problematic shell extensions
Shell extensions are add-ons that other programs install into File Explorer — right-click menu items, preview handlers, thumbnail providers, and column handlers. A buggy shell extension can crash explorer.exe every time it loads:
- Download ShellExView from NirSoft (a free utility). Run it and sort by Type. Look for third-party shell extensions (ones not published by Microsoft). Common problematic extensions come from cloud storage apps (Dropbox, Google Drive, OneDrive), archive tools (7-Zip, WinRAR), antivirus software, and GPU driver packages
- Disable non-Microsoft extensions one group at a time, then restart File Explorer to test. When the crashes stop, the last group you disabled contains the problematic extension. Re-enable them individually to isolate the exact one
- Once identified, update or uninstall the software that installed the problematic extension. If you need the software, check for a newer version that fixes the compatibility issue
Run system file repair
Corrupted Windows system files that File Explorer depends on cause crashes that no settings change can fix:
- Open Command Prompt as administrator. Run sfc /scannow and wait for it to complete. This scans all protected system files and replaces corrupted ones with correct copies from the component store. If it reports finding and repairing files, restart the computer and test File Explorer
- If SFC reports it found corruption but could not fix some files, run: DISM /Online /Cleanup-Image /RestoreHealth. This repairs the component store itself (the source SFC uses for replacement files). After DISM completes, run sfc /scannow again
- Restart the computer after any repairs. System file corruption can be caused by sudden power loss, forced shutdowns during updates, disk errors, or malware
Check for display driver issues
File Explorer uses GPU acceleration for rendering thumbnails, preview pane content, and animations. A buggy or outdated display driver can crash explorer.exe during these operations:
- If crashes happen when viewing image or video files (File Explorer tries to render previews), the display driver is a likely cause. Update to the latest GPU driver from NVIDIA or AMD. Use the Clean Installation option during install
- Disable preview pane and details pane: Open File Explorer, click View (or the three-dot menu in Windows 11), and turn off Preview Pane and Details Pane. These features invoke the display driver to render file previews. If crashes stop with these disabled, the driver or a specific preview handler is the cause
- Disable thumbnail previews entirely: File Explorer Options, View tab, check Always show icons, never thumbnails. This prevents File Explorer from generating any visual previews, eliminating that entire class of crash triggers
Fix folder-specific crashes
If File Explorer crashes only when you open a specific folder, the problem is likely a corrupted file or thumbnail in that folder:
- Navigate to the parent folder of the problematic one. If File Explorer crashes before you can get there, use Command Prompt to investigate: dir /b "C:\path\to\folder" to list contents, and try moving or renaming files to isolate which one triggers the crash
- Large folders with thousands of files can cause File Explorer to crash when it tries to generate thumbnails for all of them simultaneously. Switching the folder view to List or Details (instead of Large Icons or Tiles) prevents thumbnail generation and may allow you to access the folder
- Video files with corrupted metadata or unusual codecs can crash the shell extension that generates video previews. If a folder with video files crashes File Explorer, the video preview handler is likely the cause — disable preview pane and thumbnail previews as described above
Windows Update and recent changes
- If File Explorer started crashing after a Windows Update, the update may have introduced a bug or a compatibility issue with installed software. Check Windows Update history: Settings, Windows Update, Update History. If you can identify the update that coincides with the crashes starting, uninstall it: Settings, Windows Update, Update History, Uninstall Updates
- If the crashes started after installing new software, that software likely installed a shell extension or system component that conflicts with File Explorer. Uninstall the most recently added software and test
Check Event Viewer for crash details
- Open Event Viewer (search for it in the Start menu). Navigate to Windows Logs, Application. Look for Error events with Source as Windows Error Reporting or Application Error around the time of the crashes. The faulting module name tells you which DLL or component caused the crash — this points directly to the problematic software or driver
- Common faulting modules: ntdll.dll (system-level, often indicates corrupted system files or bad RAM), shell32.dll (shell extension conflict), comctl32.dll (common controls issue), and third-party DLL names (points to the specific software)
Create a new user profile
If all other fixes fail, the issue may be in your user profile specifically — corrupted registry entries, broken Quick Access data, or damaged profile-specific settings:
- Create a new local user account: Settings, Accounts, Other Users, Add Account. Sign in with the new account and test File Explorer. If it works perfectly in the new profile, the problem is your original profile configuration, not the system itself
- You can gradually move your data (Documents, Desktop, Downloads) from the old profile to the new one. The old profile folder is at C:\Users\OldUsername
Remote repair for File Explorer crashes
File Explorer crashes can be tricky to diagnose because the causes involve shell extensions, drivers, system files, and user profile data all interacting together. Our remote technicians can connect to your computer, analyze the crash logs, identify the specific faulting component, and apply the targeted fix to stop the crashes.