What to Do When File Explorer Keeps Crashing?

Is your File Explorer crashing every time you try to open a folder, browse files, or even right click on your desktop? You are not alone. Thousands of Windows users face this exact problem every day, and it can bring your entire workflow to a standstill.

File Explorer is more than just a file browser. It powers your taskbar, Start menu, and the entire Windows shell. So when it crashes, everything feels broken.

The good news is that most File Explorer crashes have clear, fixable causes. Corrupt cache files, buggy third party shell extensions, damaged system files, and outdated drivers are the usual suspects.

This guide walks you through 15 practical, step by step solutions that will get your File Explorer back to normal. Whether you use Windows 10 or Windows 11, these fixes apply to both. Let’s get your system stable again.

In a Nutshell

• Restart File Explorer from Task Manager as your first quick fix. This clears temporary glitches and reloads the entire Windows shell, including the taskbar and Start menu.
• Clear your File Explorer history and Quick Access cache. Corrupted recent file entries and broken thumbnail data are among the most common causes of repeated crashes.
• Disable third party shell extensions using a free tool called ShellExView. These extensions run inside the Explorer process and a single buggy one can crash the entire shell.
• Run SFC and DISM scans from an elevated command prompt to find and repair corrupted Windows system files that may be causing instability.
• Update or roll back your graphics drivers. Display drivers interact directly with how Explorer renders thumbnails, icons, and folder views. A faulty driver update can trigger constant crashes.
• Perform a clean boot to isolate whether background software or services are conflicting with File Explorer. This method helps you find the exact program causing the problem.

Why Does File Explorer Keep Crashing?

Understanding the root cause is the first step toward a permanent fix. File Explorer (explorer.exe) is deeply integrated into Windows. It does not just show your files. It also runs the taskbar, Start menu, desktop icons, and context menus. Because of this deep integration, problems in any connected component can crash Explorer.

The most common causes include corrupted cache and history files that Explorer tries to load every time it opens. Third party software often installs shell extensions that run inside the Explorer process. If one of these extensions has a bug, it will crash Explorer repeatedly.

Damaged system files are another frequent cause. Windows updates that fail to install properly can leave behind corrupt files. Driver conflicts, especially with GPU drivers, can also cause rendering problems that make Explorer freeze or crash.

Sometimes the issue is folder specific. A single malformed image, video, or document in a folder can crash Explorer when it tries to generate a thumbnail or preview. Network drives that are slow or disconnected can also hang the Explorer process until it stops responding.

Restart File Explorer Through Task Manager

The fastest way to recover from a crash is to restart the Explorer process. This does not mean closing and reopening a File Explorer window. You need to restart the entire shell process that powers Windows.

Press Ctrl + Shift + Esc to open Task Manager. Find Windows Explorer under the Processes tab. Right click it and select Restart. Your taskbar and desktop icons will briefly disappear and then come back. This clears all temporary glitches and reloads the shell.

If Task Manager is also unresponsive, open a Command Prompt window and type taskkill /f /im explorer.exe followed by start explorer.exe on the next line. This force kills the process and starts a fresh instance.

After the restart, pay attention to what you were doing before the crash. Did it happen when you opened a specific folder? Did it crash after a right click? These details help you pinpoint the cause for the fixes that follow.

Clear File Explorer History and Quick Access Data

File Explorer stores data about your recently accessed files and frequently used folders in the Quick Access section. Over time, this data can become corrupted and cause Explorer to freeze or crash during startup.

To clear this data, open File Explorer and click the three dot menu at the top. Select Options. Under the General tab, look for the Privacy section. Click the Clear button next to “Clear File Explorer history.” You can also uncheck the boxes for “Show recently used files” and “Show frequently used folders” while troubleshooting.

For a deeper clean, press Windows + R and type %APPDATA%\Microsoft\Windows\Recent\AutomaticDestinations then press Enter. Delete all files inside this folder. Do the same for %APPDATA%\Microsoft\Windows\Recent\CustomDestinations. These folders contain the jump list and Quick Access data that Explorer loads at startup.

Clearing this data is completely safe. Your actual files remain untouched. You only lose the recent files list, which rebuilds itself as you use your computer.

Delete the Thumbnail Cache

Windows generates and stores thumbnail images for your files to display them in Explorer. A corrupted thumbnail cache is a well known cause of Explorer crashes, especially in folders with many images or videos.

To clear it, open File Explorer Options from the three dot menu. Go to the View tab and check the box that says “Always show icons, never thumbnails.” Click Apply. This stops Explorer from trying to render thumbnails while you troubleshoot.

You can also manually delete the cache files. Open Disk Cleanup by searching for it in the Start menu. Select your system drive and click OK. Check the box for Thumbnails and click “OK” to delete them.

For a manual approach, go to %localappdata%\Microsoft\Windows\Explorer in the Run dialog. You will see files named thumbcache_*.db. Close all Explorer windows, delete these files, and restart your computer. Windows will rebuild the cache from scratch.

If your crashes stop after this step, the problem was a corrupt thumbnail file. You can re enable thumbnail previews once the cache has been rebuilt cleanly.

Disable the Preview Pane

The Preview Pane in File Explorer lets you see file contents without opening them. While this is convenient, it is also a common crash trigger. If a file is malformed or if a preview handler has a bug, Explorer will crash the moment it tries to display the preview.

To disable it, open File Explorer and go to the View menu. Look for Preview Pane and make sure it is toggled off. Also disable the Details Pane if it is active.

This is especially important if Explorer crashes only when you click on specific files or open certain folders. A corrupted PDF, a broken video file, or an unsupported image format can all cause the preview handler to fail.

If disabling the Preview Pane fixes your crashes, the next step is to identify the problematic file or preview handler. Move files out of the folder one at a time until you find the one causing the crash. You can also update or uninstall third party applications that install preview handlers, such as PDF readers or raw photo editors.

Find and Disable Buggy Shell Extensions

Shell extensions are add ons that other programs install into File Explorer. They add features like context menu entries, icon overlays, and preview handlers. These extensions run directly inside the Explorer process. A single faulty extension can crash Explorer every time you right click, open a folder, or hover over a file.

The best tool for this job is ShellExView from NirSoft. It is a free utility that lists every shell extension installed on your system. Download it from the official NirSoft website and run it.

Click Options in the menu bar and select “Hide All Microsoft Extensions.” This filters the list to show only third party items. Now disable all non Microsoft extensions by selecting them and pressing F7. Restart Explorer and test.

If the crashes stop, you know a third party extension is the cause. Re enable the extensions in small groups and test after each group. This process of elimination will reveal the exact extension causing the problem.

Common offenders include cloud storage sync clients, archive tools like 7 Zip or WinRAR, antivirus software, and older versions of multimedia applications. Once you identify the culprit, update or uninstall the associated software.

Run the System File Checker and DISM Commands

Corrupted Windows system files can cause all kinds of instability, including persistent File Explorer crashes. Windows includes two built in repair tools that can scan for and fix these problems.

Open the Start menu and search for Command Prompt. Right click it and select Run as administrator. First, run the DISM command to repair the Windows component store. Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This process can take 15 to 30 minutes.

After DISM finishes, run the System File Checker. Type sfc /scannow and press Enter. This scans all protected system files and replaces any corrupted ones with correct copies.

It is important to run DISM before SFC. The System File Checker relies on the Windows component store to get clean copies of files. If that store is itself corrupted, SFC cannot do its job properly. DISM fixes the store first.

After both commands finish, restart your computer and test File Explorer. If either tool reports that it found and repaired files, there is a good chance your crashes are now resolved.

Update or Roll Back Graphics Drivers

Your GPU driver plays a direct role in how File Explorer renders thumbnails, icons, and folder views. A buggy driver update can cause Explorer to crash or freeze, especially when browsing folders with media files.

Open Device Manager by pressing Windows + X and selecting it from the menu. Expand the Display adapters section. Right click your graphics card and select Update driver. Choose “Search automatically for drivers” and let Windows look for an update.

If the crashes started after a recent driver update, you should roll back the driver instead. Right click the graphics card in Device Manager, select Properties, go to the Driver tab, and click Roll Back Driver. This returns you to the previous working version.

For the best results, visit the official website of your GPU manufacturer. Download the latest stable driver from Intel, NVIDIA, or AMD directly. Avoid beta drivers when stability is a concern. A clean driver installation often resolves Explorer rendering issues that other fixes cannot.

Check for Windows Updates

Microsoft regularly releases updates that fix known bugs in File Explorer and other system components. Running an outdated version of Windows can leave you stuck with bugs that have already been patched.

Go to Settings > Windows Update and click Check for updates. Install all available updates, including optional ones. Some Explorer fixes are delivered through cumulative updates that bundle multiple patches together.

After installing updates, restart your computer. Pay special attention to updates labeled as “cumulative” or “reliability.” These often contain fixes for shell and Explorer problems.

If a recent Windows update caused the crashes, you can uninstall it. Go to Settings > Windows Update > Update history > Uninstall updates. Find the most recent update, click Uninstall, and restart. This can serve as a temporary fix while Microsoft releases a corrected version.

Perform a Clean Boot

A clean boot starts Windows with only essential Microsoft services and no third party startup programs. This helps you determine whether background software is causing the Explorer crashes.

Press Windows + R, type msconfig, and press Enter. Go to the Services tab. Check the box that says “Hide all Microsoft services.” Then click Disable all. Next, open Task Manager from the Startup tab and disable all startup items.

Restart your computer. If File Explorer runs without crashing in this clean boot state, the problem is caused by a third party service or startup program.

To find the exact culprit, re enable services in groups of five. Restart after each group. When the crashes return, you know the problem is in the last group you enabled. Narrow it down further until you identify the specific service or program.

Once you find the conflicting software, you can update it, reinstall it, or replace it with an alternative. Remember to re enable all other services and startup items after you finish troubleshooting.

Rebuild the Windows Search Index

File Explorer uses the Windows Search index to deliver fast search results and to populate certain views. A corrupted search index can cause Explorer to hang or crash, especially when you use the search bar or open indexed folders.

Open Settings and go to Privacy & Security > Searching Windows. Scroll down and click Advanced Indexing Options. In the dialog that opens, click the Advanced button. Under the Troubleshooting section, click Rebuild.

The rebuilding process can take anywhere from a few minutes to several hours depending on how many files are on your drives. During this time, search results may be incomplete or slow. Let the process finish without interrupting it.

If your crashes were related to search operations or happened when Explorer tried to index file metadata, rebuilding the index should resolve the issue. You can also try pausing or limiting indexing locations if you notice that indexing causes ongoing performance problems.

Test in a New User Profile

Sometimes the problem is specific to your user profile rather than a system wide issue. Corrupted user settings, broken registry entries, or damaged per user cache files can all cause Explorer to crash only for your account.

Open Settings > Accounts > Other users. Click Add account and create a new local account. Sign out of your current account and sign into the new one.

If File Explorer works perfectly in the new profile, the issue is isolated to your original account. You can migrate your files to the new profile or try repairing the old one by resetting Explorer settings and clearing user specific caches.

This is a valuable diagnostic step because it confirms whether the problem lies in your user data or in the Windows installation itself. Many users skip this step and spend hours on system level fixes when the answer was a simple profile reset.

Run a Disk Check for File System Errors

Hard drive errors and bad sectors can cause intermittent Explorer crashes. If your storage drive has file system corruption, Explorer may crash when it tries to read data from damaged areas.

Open an elevated Command Prompt and type chkdsk C: /f /r then press Enter. The system will ask you to schedule the check for the next restart. Type Y and restart your computer.

The check disk utility will scan your drive for file system errors and bad sectors. It will attempt to repair any issues it finds. This process can take a significant amount of time depending on the size of your drive.

If chkdsk finds and fixes errors, your Explorer crashes may stop immediately after the repair. If you see repeated disk errors on the same drive, it may be a sign that your storage hardware is failing and needs replacement.

Use System Restore as a Last Resort

If none of the above fixes resolve the problem, System Restore can take your computer back to a point in time when everything worked. This undoes recent system changes, driver installations, and software updates that may have caused the crashes.

Open the Start menu and search for “Create a restore point.” Click System Restore in the dialog. Select a restore point from before the crashes started and follow the prompts.

System Restore does not delete your personal files. It only reverts system files, drivers, and registry settings. However, any software you installed after the selected restore point will need to be reinstalled.

If System Restore is not available or if no restore points exist, you can perform an in place repair using the Windows installation media. This option keeps your files and apps while replacing all system files with fresh copies. It is the most thorough repair option short of a full reinstall.

Frequently Asked Questions

Why does File Explorer crash every time I open a specific folder?

This usually happens because of a corrupted file inside that folder that triggers the thumbnail generator or preview handler. Try disabling the Preview Pane and switching the folder view to “List” or “Details” instead of “Large Icons.” You can also try clearing the thumbnail cache. If the crash persists, move files out of the folder one at a time to identify the problematic file.

Can a Windows update cause File Explorer to crash?

Yes. Some Windows updates introduce bugs that affect Explorer. If your crashes started right after an update, go to Settings > Windows Update > Update history > Uninstall updates and remove the most recent one. Check Microsoft support forums to see if other users report similar issues with the same update.

Is it safe to disable shell extensions in ShellExView?

Disabling shell extensions is generally safe and reversible. You may lose some functionality, such as context menu options from specific programs. You can re enable any extension at any time. Avoid disabling Microsoft system extensions as those are needed for Windows to function properly.

Will clearing File Explorer history delete my files?

No. Clearing File Explorer history only removes the list of recently accessed files and frequently used folders displayed in Quick Access. Your actual files and folders remain completely untouched on your drive.

What should I do if File Explorer crashes even in Safe Mode?

If Explorer crashes in Safe Mode, the problem is likely caused by corrupted system files rather than third party software. Run the SFC and DISM commands from an elevated Command Prompt. If those tools cannot fix the issue, consider performing an in place repair installation of Windows using the official Media Creation Tool.

How do I know if a graphics driver is causing the crash?

Check Event Viewer for error entries around the time of each crash. Look under Windows Logs > Application and Windows Logs > System. If you see entries referencing your GPU driver (such as nvlddmkm for NVIDIA or atikmdag for AMD), a driver update or rollback should fix the problem. You can also test by temporarily switching to the Microsoft Basic Display Adapter in Device Manager.