Update: Stop getting error messages and slow down your system with our optimization tool. Get it now at this link
File Explorer, originally known as Windows Explorer, is a file management application built into Windows. It is undoubtedly one of the most used applications on the PC. However, even though Microsoft is constantly improving File Explorer, some problems remain, for example, Windows 10 File Explorer constantly crashes. This issue worries many users and causes various problems. If you are facing the problem of “File Explorer” crashing in Windows 10, you may find yourself in one of the following scenarios.
There are several common situations where users report that “File Explorer crashes” in Windows 10.
- File Explorer constantly closes
- File Explorer crashes frequently
- Windows 10 file explorer doesn’t respond
- File Explorer no longer opens in Windows 10
- Windows 10 file explorer doesn’t work anymore
- File Explorer closes when you right-click on a file
What causes File Explorer to crash?
After a thorough investigation, it was found that File Explorer crashes can be caused by various reasons such as faulty registry, corrupted system files, non-functioning software, etc.
According to user reports, WinRAR files are often the cause of these errors. Unfortunately, this problem is not among the most common ones, which may be the reason why Microsoft has not yet released a fix.
However, below are some very effective guides that can help you troubleshoot File Explorer crashes.
How to repair File Explorer crashes?
Install the latest updates
- Open the Settings app and go to Update and Security.
- Click the Check for Updates button.
Reinstall your graphics card driver
- Press the Windows + X key to open the Win + X menu.
- Select Device Manager from the list of results.
- Find your video card driver, right-click on it, and select Uninstall Device from the menu.
- Select the Uninstall driver software for this device checkbox and click the Uninstall button.
Perform netsh and reset winsock
- Type cmd in the search bar -> right-click Command Prompt -> Run as administrator.
- Type netsh at the command prompt -> press Enter.
- Type winsock at the command prompt -> press Enter.
You can also use the entire netsh winsock reset command in one recovery attempt.
Grant yourself full access rights to the contents of the folder
- Launch File Explorer -> right-click the folder where the files are stored -> select Properties.
- Go to Security -> click Advanced.
- Click Edit next to the owner name -> click Advanced in the new window.
- When you click Advanced, a new window opens.
- Click Search Now to display all groups and users on your computer.
- Select a name or group from the list -> click OK. Save your changes.
- Set full access to the file folder for your account.
- Set the permissions in the Allow column for your account to Full Access and click Apply and OK to save your changes.
Changing file explorer settings
- Press the Windows + S key combination and go to Folder Options.
- Select File Explorer Preferences from the menu.
- Click the View tab.
- Enable the option Start folder window in a separate process and click Apply and OK to save your changes.
Frequently Asked Questions
- Delete the registry key.
- Delete the File Explorer history.
- Disable access to DeepL.
- Change display settings.
- Update the video card driver.
- Enable the Windows startup folder.
- Check account authorization.
- Perform a Netsh Winsock reset.
If the "File Explorer" error is caused by corrupted files, you can fix it by running an SFC scan. To run an SFC scan, locate the "Command Line" application on the Start menu, right-click it, and select "Run as administrator".
If File Explorer keeps crashing, one of the most common reasons is missing or corrupted files. To check (and repair) missing or corrupt system files, you can run the System File Checker (SFC) tool using Windows PowerShell. The SFC tool takes some time to check your computer for file errors.
- Keep Windows up to date.
- Remove third-party add-ons.
- Disable thumbnails.
- Run folder windows in a separate process.
- Remove Windows Explorer history.
- Check the Windows event viewer.
- Run SFC and Chkdsk scans.