FIX: File Explorer crashes when searching in Windows 10

Andrew Wafer
by Andrew Wafer
Download PDF
Affiliate Disclosure

  • On a Windows 10 based computer, all sorts of errors need to be addressed by users.
  • If File Explorer crashes when searching in Windows 10, then this post will help you resolve the problem.
  • Deleting Registry Keys or disabling cloud storage extensions are two efficient ways to solve the issue.
File Explorer crashes when searching in Windows 10

Windows 10 is mostly a stable system that can be installed on both portable and desktop devices. Even though Microsoft tried to address all the Windows issues by releasing different OS updates, one problem is still present in the platform: File Explorer crashes during searches.

Why does File Explorer keep crashing? Improper system settings, permission issues, or graphics card driver errors are all potential causes to take into consideration.

In case you are experiencing multiple File Explorer (explorer.exe) issues, then you should follow this tutorial in order to learn how to easily fix these bugs and how to enjoy a stable and smooth OS.

The troubleshooting solutions detailed here will address the most common Explorer bugs and issues from Windows 10, thus don’t hesitate and give them a try as soon as possible.

How can I fix the Windows 10 File Explorer crash issue?

1. Delete Registry Keys

  1. To access the Registry Editor in Windows 10, press Windows + R keyboard shortcut to open the Run Dialog box.
  2. Enter regedit in this box and press OK.
  3. In the prompt asking for permission, don’t hesitate to click Yes.
  4. Go to:
    HKEY_CURRENT_USERSoftwareClassesLocal SettingsSoftwareMicrosoftWindowsShell
  5. Expand Shell and delete BagMRU and Bags by right-clicking the folders and choosing Delete.delete BagMRU
  6. Finally, you need to restart your computer and confirm that File Explorer doesn’t crash any longer.

Windows Registry remains one of the main components of the Windows operating system. The Bag keys store information about each folder including its display settings, so don’t hesitate to delete these keys.

This will reset the settings for all folders on your computer. You may safely do so as long as Windows will automatically rebuild them after a restart and helpfully fix the issue you’re currently facing.

Can’t access Registry Editor in Windows 10? Check this guide to solve the issue quickly!

2. Disable cloud storage extensions

  1. On your computer, use the keyboard shortcut Windows Key + R to launch the Run window.
  2. On the Run box, type regedit and click OK.type regedit
  3. From left panel of Registry Editor go to HKEY_CLASSES_ROOT > CLSID{8E74D236-7F35-4720-B138-1FED0B85EA75} ShellFolder key.go to HKEY_CLASSES_ROOT
  4. Right-click on the ShellFolder key, head towards Permissions and select advanced.
  5. Tap on the Owner and select change. You should be the owner, so type in your username and confirm.
  6. Under your username, check to Replace owner on sub containers and objects.
  7. Furthermore, from the bottom of the same window check Replace all child object permissions with inheritable permissions from this subject, then click OK.
  8. You will be set back on the Permissions section for the SellFolder window.
  9. From there, check the full control box and click OK – now you will be back on Registry Editor.
  10. From the right pane of Registry Editor, click on Attributes key and set the value to 0.
  11. Save your changes and reboot your Windows 10 device.

3. Scan system directory and repair issues automatically

  1. Press the Windows key + R key, which opens the Run dialog box.
  2. On the Run box, type cmd and click OK.type cmd in the run box
  3. On the cmd window, type sfc /scannow and press Enter.
  4. Wait while System File Checker is repairing your computer.
  5. When it completes the procedure, restart your PC. Check if the issue is resolved at the next system startup.

If File Explorer still crashes on startup, let the System File Checker built-in administrative tool step in. You may actually run this SFC command every time when troubleshooting a buggy Windows system.

scannow command has stopped before the process finished? Don’t worry, we’ve got an easy fix for you.

When all previous methods failed, our last recommendations are to take into consideration clearing the File Explorer History or updating the graphics card driver.

The truth is that the majority of Windows 10 users have outdated drivers. Be a step ahead using this guide to update drivers like a pro.

Congratulations, you have successfully fixed the File Explorer crashing issue from your Windows 10 OS. Don’t forget to share your experience with us by using the comments field from below.

Editor’s Note: This post was originally published in May 2014 and has been since revamped and updated in March 2020 for freshness, accuracy, and comprehensiveness.

Was this page helpful?
Thanks for letting us know! You can also help us by leaving a review on MyWOT or Trustpillot.
Get the most from your tech with our daily tips
Tell us why!
  • When attempting setting the value to “0” in the first fix I get the error message “Cannot exit Attributes: Error writing the values new contents”. Is there a way around this issue?

  • I have to admit, though I had been to several websites including Microsoft for my issue which is explorer freezing (all folders, windows task manager etc), your solution # 2 (Registry fix for that DLNA) fixed the issue like a breeze. Though I could not find the key for the Solution # 1. Anyways, I am extremely happy… and a big THANK YOU !

  • I am not able to get pass number 11 when setting the Attributes to 0. It tells me “Cannot edit Attributes: Error writing the value’s new contents.”

  • Started well, nice clear instructions but when I was on step 11 – changing the Attributes key to 0, I wasn’t able to save the changes. Have had to reverse out what I was doing and reset user name to SYSTEM, but then not able to select the ‘Replace all child object permission entries….’ tick box. Then tried the SCANNOW option (I am an administrator) but says that I need to open a console session in order to run it. No idea how to do this. Will Windows be bringing out a fix in an update pack soon as I am clearly not competent to fix it myself?