How to Fix Windows File Explorer When It Keeps Crashing

Published 2026-10-16 · Marion Remote Fix

You open File Explorer and it freezes. You navigate to a folder and it crashes, restarting automatically or closing entirely. You right-click a file and the window stops responding. File Explorer crashing repeatedly is one of the more disruptive Windows problems because File Explorer is the primary way you access files, folders, drives, and network locations. When it is unstable, routine file management becomes frustrating. The causes range from corrupted thumbnail caches and shell extensions to disk errors and system file corruption.

Quick fixes

Restart File Explorer

  • Open Task Manager (Ctrl+Shift+Esc). Find Windows Explorer in the process list. Right-click it and select Restart. This kills and restarts the Explorer process without rebooting the computer
  • If File Explorer is completely frozen and will not respond to Task Manager, you can end the Windows Explorer process and then restart it. In Task Manager, right-click Windows Explorer and select End Task. Then click File, Run New Task, type explorer.exe, and press Enter

Clear the File Explorer history

  • File Explorer stores a history of recently accessed files and folders. A corrupted history file can cause crashes when Explorer tries to load the Quick Access view
  • Open File Explorer Options (search for it in the Start menu or open it through Control Panel, Appearance and Personalization). Under the General tab, click the Clear button next to Clear File Explorer History
  • Also consider changing the Open File Explorer To setting from Quick Access to This PC. Quick Access loads recent files and frequent folders, which can trigger crashes if any of those paths are problematic (network drives that are offline, paths to deleted folders, corrupted shortcut targets)

Shell extensions

What shell extensions are

  • Shell extensions are add-ons that integrate into File Explorer to provide additional functionality — right-click context menu items, icon overlays, preview handlers, and property sheet tabs. They are installed by many applications including cloud storage clients (Dropbox, OneDrive, Google Drive), version control tools (Git, TortoiseSVN), archive tools (7-Zip, WinRAR), and antivirus software
  • A buggy or incompatible shell extension can crash File Explorer every time it loads. Since shell extensions run inside the Explorer process, a crash in the extension crashes Explorer itself

Diagnosing shell extension crashes

  • If File Explorer crashes when you right-click files or folders, a context menu shell extension is likely responsible
  • If Explorer crashes when opening specific folders, a preview handler or icon overlay extension may be failing on a specific file type in that folder
  • The free tool ShellExView from NirSoft shows all installed shell extensions and lets you disable them individually. Disable third-party extensions one at a time and test File Explorer after each to identify the culprit
  • Boot Windows in Safe Mode (which loads without third-party shell extensions) and test File Explorer. If Explorer works perfectly in Safe Mode, a shell extension is confirmed as the cause

Thumbnail and icon cache

  • File Explorer generates thumbnail previews and icon overlays for files and folders. The cache that stores these can become corrupted, causing crashes when Explorer tries to render thumbnails in certain folders
  • Clear the thumbnail cache: open Disk Cleanup (search for it in Start), select your system drive, check Thumbnails, and click OK. Alternatively, open a Command Prompt as Administrator and run the following: taskkill /f /im explorer.exe then del /f /s /q /a %LocalAppData%\Microsoft\Windows\Explorer\thumbcache_*.db then start explorer.exe
  • If crashes happen specifically in folders with many images or videos, the thumbnail generation for those file types may be the trigger. You can disable thumbnail previews temporarily to test: in File Explorer Options, View tab, check Always Show Icons, Never Thumbnails. If Explorer stops crashing, the thumbnail generation is the problem

Quick Access corruption

  • The Quick Access section in File Explorer maintains a list of pinned and frequently accessed folders. If any of these entries point to corrupted, moved, or inaccessible locations, Quick Access can cause Explorer to freeze or crash on startup
  • Clear Quick Access entries: open File Explorer Options, General tab, click Clear under Clear File Explorer History. Then unpin any manually pinned items in Quick Access that point to locations that no longer exist or are on disconnected drives
  • If Quick Access itself is corrupted beyond clearing, you can reset it by deleting the Quick Access database files. Navigate to the AppData, Local, Microsoft, Windows, Recent, AutomaticDestinations folder on your system drive and delete the files there. Restart Explorer. Quick Access rebuilds its database from scratch

System file repair

  • Corrupted Windows system files can cause File Explorer instability. Run the System File Checker to check for and repair corruption
  • Open Command Prompt as Administrator and run sfc /scannow. The scan takes several minutes and reports whether it found and fixed any corrupted files
  • If SFC reports corruption it could not fix, run DISM /Online /Cleanup-Image /RestoreHealth first, then run sfc /scannow again. DISM repairs the Windows image that SFC uses as its reference for correct files

Folder-specific crashes

Network folders

  • If Explorer crashes when accessing network drives or shared folders, the network path may be unreachable, causing Explorer to hang and eventually crash while waiting for a connection timeout
  • Disconnect mapped drives that are no longer accessible. In File Explorer, right-click a mapped drive and select Disconnect. If you cannot access File Explorer to disconnect, use the command net use Z: /delete (replacing Z with the drive letter) in Command Prompt
  • If mapped drives reconnect on login but the network is not ready yet, Explorer can crash during startup. Configure mapped drives to reconnect only when needed rather than at login

Folders with problematic files

  • Certain corrupted files can crash Explorer when it tries to generate a preview or read properties. If Explorer crashes only in one specific folder, a file in that folder is the cause
  • Try accessing the folder through Command Prompt instead of Explorer to list the contents without triggering preview generation. Use the dir command to list files and move suspect files (very large files, files with unusual extensions, recently downloaded files) out of the folder to isolate the problem

File Explorer add-ons and features

Preview pane

  • The Preview Pane in File Explorer (toggled with Alt+P or from the View menu) loads a preview of the selected file in a side panel. If a file format has a buggy preview handler, selecting that file crashes Explorer
  • If crashes correlate with selecting specific file types, disable the Preview Pane and test. If the crashes stop, the preview handler for that file type is faulty. Updating or reinstalling the application associated with that file type may fix its preview handler

Details pane

  • Similar to the Preview Pane, the Details Pane reads file metadata to display properties. Corrupted metadata in certain files can crash the metadata reader and take Explorer down with it
  • Toggle the Details Pane off (from the View menu) to test

Windows Update related issues

  • Windows Updates occasionally introduce File Explorer bugs. If Explorer started crashing immediately after an update, check if other users are reporting the same issue — Microsoft typically releases a fix within days for widespread Explorer problems
  • As a workaround, you can uninstall the most recent update through Settings, Windows Update, Update History, Uninstall Updates. This reverts the change while waiting for a fix

Need help with File Explorer crashes?

If File Explorer keeps crashing and the fixes above have not stabilized it, or if you suspect a deeper system corruption or a specific shell extension conflict you cannot identify, Marion Remote Fix can remotely diagnose Explorer crashes, identify problematic extensions, repair system files, and restore stable file management on your computer.

← Back to Blog