Fix Explorer Class Not Registered Error in Windows 10

This guide walks you through the most effective ways to resolve the “Explorer class not registered” error in Windows 10. This error typically appears when opening folders, using the Start menu, or accessing certain system settings, and it is usually caused by corrupted file associations or a broken Windows Registry entry. The steps below are safe, non-destructive, and designed for users of all skill levels.

What You’ll Need

A Windows 10 PC with administrator access (you’ll need to confirm a User Account Control prompt)
An internet connection (for the DISM and SFC steps, though they can run offline)
About 15–30 minutes of time

Step-by-Step

Restart Windows Explorer. Press Ctrl+Shift+Esc to open Task Manager. Find “Windows Explorer” in the list, right-click it, and choose “Restart.” This often clears temporary glitches without affecting open files.
Run the System File Checker. Click Start, type cmd, right-click “Command Prompt” and select “Run as administrator.” In the window, type sfc /scannow and press Enter. Wait for the scan to finish (it can take 10–15 minutes). If it finds corrupted system files, it will repair them automatically.
Run DISM to repair the system image. In the same administrator Command Prompt, type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This fixes deeper Windows corruption that SFC cannot. Let it complete—it may take up to 20 minutes. After it finishes, restart your PC.
Check the default file associations. Go to Settings (Windows key + I) > Apps > Default apps. Scroll down and click “Reset” under “Reset to the Microsoft recommended defaults.” This restores the default file associations that may have been changed by third-party software.
Re-register the Windows Store apps. Open PowerShell as administrator (right-click Start > Windows PowerShell (Admin)). Type the following command and press Enter:
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
This command re-registers all built-in apps, which often resolves the “class not registered” error. It may take a minute; you can ignore the red text that appears.
Create a new user account. If the error persists, the issue may be tied to your current user profile. Go to Settings > Accounts > Family & other users > Add someone else to this PC. Create a new local account, sign out of your current one, and sign into the new account. If the error is gone, you can migrate your files.
Perform a clean boot. Press Windows key + R, type msconfig, and press Enter. On the Services tab, check “Hide all Microsoft services,” then click “Disable all.” On the Startup tab, click “Open Task Manager,” disable all startup items, and restart. If the error disappears, a third-party service or startup program is the culprit—re-enable services one by one to find it.

Common Mistakes

Skipping the DISM step: Many users run SFC but skip DISM. If SFC finds issues it cannot fix, DISM is required to repair the underlying image. Always run both.
Not running as administrator: The SFC, DISM, and PowerShell commands will fail or do nothing if you don’t open the command prompt or PowerShell with admin rights.
Using the wrong PowerShell command: The re-register command is case-sensitive in some parts—copy it exactly as shown. Also, ensure you’re in PowerShell, not Command Prompt.
Disabling all services permanently: If you use a clean boot to diagnose, remember to re-enable the services afterward. Leaving them disabled can cause other problems.

Tips

Create a restore point first: Before making registry or system changes, go to Control Panel > Recovery > Configure System Restore and create a restore point. This gives you a safe rollback option.
Keep Windows updated: The error is often fixed by cumulative updates. Go to Settings > Update & Security > Windows Update and check for updates.
Use the built-in troubleshooter: Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters, then run the “Windows Store Apps” troubleshooter—it can automatically fix app registration issues.
Check for third-party context menu tools: Tools like WinRAR, 7-Zip, or shell extensions can break file associations. Uninstall or update them if the error started after installing one.

Troubleshooting

If the error persists after following all steps, try the following:

Check the Event Viewer: Press Windows key + X, select “Event Viewer,” and look under “Windows Logs > Application” for errors related to Explorer or Shell. The details may point to a specific DLL or app causing the issue.
Run a full antivirus scan: Malware can corrupt file associations. Use Windows Defender or a reputable third-party scanner to rule this out.
Use System Restore: If you created a restore point earlier, go to Control Panel > Recovery > Open System Restore and choose a point before the error started.
Perform an in-place upgrade repair: Download the Windows 10 Media Creation Tool, run it, and choose “Upgrade this PC now.” This reinstalls Windows while keeping your files and apps—it often fixes persistent system corruption.
Check the registry manually (advanced): Press Windows key + R, type regedit, and navigate to HKEY_CLASSES_ROOT\Directory\shell. Look for any unusual subkeys that might be causing the error. Only delete entries you’re sure are not standard—this is risky, so back up the registry first.

Frequently Asked Questions

What exactly does “Explorer class not registered” mean?

It means Windows Explorer (the file manager and desktop shell) cannot load a specific component—usually a COM object or a file association handler. This often happens after a Windows update, a software install, or a registry change.

Will I lose my files if I run SFC or DISM?

No. SFC and DISM only repair system files; they do not touch your personal documents, photos, or other data. However, it’s always wise to back up important files before running system repairs.

How long does the DISM command take?

It can take anywhere from 5 to 20 minutes depending on your computer’s speed and the level of corruption. Let it run to completion—do not close the window or restart your PC during the process.

Can I fix this error without admin rights?

No. All the main fixes (SFC, DISM, PowerShell re-registration) require administrator privileges. You’ll need to log in with an account that has admin rights or ask the system administrator for help.

Why does the error happen only when I open a specific folder?

That usually points to a broken file association for that folder type (e.g., a custom icon or a third-party preview handler). Resetting default apps or re-registering the Windows Store apps often resolves it.

Is it safe to use the PowerShell re-register command?

Yes, the command is safe and is a standard Microsoft-recommended fix. It only re-registers built-in apps; it does not remove or alter your personal data. Some apps may briefly disappear from the Start menu, but they will return after a restart.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →