File Explorer crashes in Windows 11 occur when the explorer.exe shell process encounters an unhandled exception thrown by an incompatible third-party context menu shell extension, corrupted SQLite jump-list databases inside AutomaticDestinations, a faulty media thumbnail handler, or memory pointer corruption in core system binaries like shell32.dll and ntdll.dll. When File Explorer crashes immediately upon opening, hangs when right-clicking, or repeatedly restarts the desktop taskbar, isolating the crashing dynamic link library (DLL) or purging corrupted cache indexes resolves the issue.

Quick Diagnostic Matrix

1. Purge Corrupted Quick Access and Jump List Databases

1. Press Windows Key + R, paste the following directory path, and press Enter:

   %AppData%MicrosoftWindowsRecentAutomaticDestinations
   

2. Select all files in this folder (Ctrl + A) and permanently delete them (Shift + Delete).

3. Press Windows Key + R again, navigate to the custom jump-list folder, and press Enter:

   %AppData%MicrosoftWindowsRecentCustomDestinations
   

4. Select all files in this folder and delete them as well.

5. Open Folder Options to clear the File Explorer history cache:
   • Press Windows Key + R, type control folders, and press Enter.

   • Under the General tab, locate the Privacy section at the bottom.

   • Click the Clear button next to Clear File Explorer history.

   • Set Open File Explorer to: from “Home” to This PC.

   • Click Apply, then OK.

[Folder Options (control folders)] 
 └── General Tab 
      ├── Open File Explorer to: [Change to "This PC"]
      └── Privacy > [Click] "Clear" File Explorer history

2. Isolate and Disable Faulty Shell Extensions

1. Download the free, official utility ShellExView (from NirSoft).

2. Launch ShellExView.exe with administrative privileges.

3. In the top menu bar, click Options > Filter by Extension Type, select Context Menu, and click OK.

4. Click Options again and enable Hide All Microsoft Extensions.

5. The remaining items represent non-Microsoft shell handlers running inside the Explorer memory space.

6. Select all non-Microsoft extensions (Ctrl + A), right-click, and select Disable Selected Items.

7. Restart your computer (or restart the explorer.exe process via Task Manager).

8. If the crashes cease, re-enable the third-party extensions in small batches to identify and uninstall the specific software responsible.

3. Disable Previews and Delete the Thumbnail Cache

Step A: Disable Thumbnails Temporarily

1. Press Windows Key + R, type control folders, and hit Enter.

2. Switch to the View tab.

3. Under Files and Folders, check the box for:
   Always show icons, never thumbnails.

4. Uncheck Show preview handlers in preview pane.

5. Click Apply and OK.

Step B: Wipe the Corrupted Thumbnail Database

1. Press Windows Key + S, type cmd, right-click Command Prompt, and select Run as administrator.

2. Terminate the active Explorer process to release open file locks on the database:
   DOS

   taskkill /f /im explorer.exe
   

3. Delete the entire cached thumbnail database:
   DOS

   del /f /s /q /a "%LocalAppData%MicrosoftWindowsExplorerthumbcache_*.db"
   

4. Restart File Explorer:
   DOS

   start explorer.exe
   

4. Launch Folder Windows in a Separate Process

1. Press Windows Key + R, type control folders, and press Enter.

2. Switch to the View tab.

3. Scroll down through the Advanced settings list.

4. Check the box labeled Launch folder windows in a separate process.

5. Click Apply, then click OK.

6. Restart your computer to establish independent thread boundaries.

5. Repair Damaged System Binaries (SFC and DISM)

1. Press Windows Key + S, type cmd, right-click Command Prompt, and choose Run as administrator.

2. Run the deployment image servicing tool to verify the local component store against clean Microsoft cloud images:
   DOS

   DISM /Online /Cleanup-Image /RestoreHealth
   

3. Once the DISM operation completes at 100%, execute the System File Checker:
   DOS

   sfc /scannow
   

4. Review the final console output:
   • “Windows Resource Protection found corrupt files and successfully repaired them” indicates the broken shell binaries were restored.

5. Reboot your system immediately.

6. Inspect the Windows Reliability Monitor for Faulting Modules

1. Press Windows Key + R, type perfmon /rel, and press Enter to open the Reliability Monitor.

2. Look for red Critical event “X” icons aligned with recent File Explorer crashes.

3. Click on the event labeled Windows Explorer – Stopped working, then click View technical details.

4. Examine the Fault Module Name:
   • If it flags ntdll.dll or kernelbase.dll: The crash is often triggered by deep system memory corruption or aggressive third-party antivirus hooks.

   • If it flags a display driver like nvlddmkm.dll (NVIDIA) or amdkmdag.dll (AMD): The graphics driver crashed during hardware-accelerated UI rendering. Perform a clean GPU driver reinstall using Display Driver Uninstaller (DDU).

   • If it flags a third-party DLL (e.g., from Dropbox, Adobe, or an audio driver utility): Directly uninstall or update the software hosting that file to permanently stabilize the Explorer process.