When File Explorer crashes, restarts, or hangs for seconds every time you right-click, the usual cause is a third-party shell extension: a DLL that an app installed into the right-click menu, which runs inside Explorer itself. Fix it by finding which extension is involved and disabling it, not by reinstalling Windows. ContextCleaner lists every app add-on with the app and DLL behind it, lets you block one at a time with a snapshot first, and undoes any step if you picked the wrong one.
This page walks through why it happens, how to narrow it down, and how to test fixes without making things worse.
See which app and DLL added each right-click add-on, and block one safely.
Get it from Microsoft
Why can a right-click crash File Explorer?
Because many right-click entries are code, not just text. Microsoft’s Creating Shell Extension Handlers page says “many Shell extension handlers are in-process Component Object Model (COM) objects,” and its shortcut menu handlers page warns: “Take care when creating in-process handlers as they can cause harm to the process that loads them.”
In-process means the handler’s DLL loads inside explorer.exe. If that DLL crashes, Explorer crashes with it. If it waits on a network drive, a license check, or a slow disk, your right-click waits too.
Microsoft acknowledged this when it redesigned the Windows 11 menu. Its developer blog post Extending the Context Menu and Share Dialog in Windows 11 lists among the old menu’s problems that “many commands run in-process in Explorer, which can cause performance and reliability issues.”
Which symptoms point to a shell extension?
| Symptom | Likely meaning |
|---|---|
| Explorer closes and the taskbar flickers when you right-click a file | A context menu handler crashed inside Explorer |
| Right-click is fine on some file types and crashes on others | A handler registered for those file types |
| Show more options is slow or crashes, the compact menu is fine | A classic handler, which loads in the Windows 10 style menu |
| Right-click is slow only on network or cloud folders | A handler that checks remote state |
| Problem started after installing or updating an app | That app’s extension |
The last row is the most useful clue. Think about what you installed or updated around the time it started: archivers, cloud sync clients, antivirus, version control tools, and media tools commonly add extensions.
What should I do before I start testing?
A few minutes of preparation make the whole process calmer:
- Save open work. A crash during a test restarts Explorer, which closes open Explorer windows.
- Pick one reproducible test. For example, right-click the same .zip file in the same folder every time. A consistent test makes it obvious when a change worked.
- Take a snapshot. ContextCleaner writes one before each apply anyway, but taking one yourself at the start (Ctrl+K, take a snapshot) gives you a clean point to return to after several experiments.
- Change one thing at a time. Blocking five add-ons at once fixes the crash but hides which one caused it, and you may lose a feature you wanted to keep.
How do I find the extension that is causing it?
Work from the cheapest test to the most thorough:
- Note the pattern. Which file types, which folders, compact menu or Show more options? Write it down.
- Check Event Viewer. Open Event Viewer, go to Windows Logs, Application, and look for an error from explorer.exe at the time of the crash. If it names a faulting module, that DLL name is your best lead.
- Match the DLL to an app. In ContextCleaner, find the app add-on whose DLL matches that name. Each add-on row shows the app and DLL that registered it and which file types it covers.
- Block one suspect. Stage that single add-on to be blocked and apply. ContextCleaner writes a snapshot first.
- Test the same right-click. If the crash is gone, you found it. If not, undo and try the next suspect.
- Repeat by halves if there is no lead. Block half of the third-party add-ons for the affected file type, test, then narrow down. Undo makes this safe.
Test fixes one at a time with snapshots and 25-step undo stored on disk.
Get it from Microsoft
Why block an extension instead of deleting its registry keys?
Deleting keys by hand is the advice you will find most often, and it is the riskiest:
- You may delete the wrong thing. A CLSID that looks unused may belong to an app you still need.
- There is no undo unless you exported the key first.
- Apps re-register on update, so the entry can come back.
ContextCleaner’s approach is reversible by design. From its product page: “entries are marked hidden rather than deleted, add-ons go on a block list rather than being unregistered, and New items are renamed rather than removed.” Undo and redo are stored on disk, up to 25 steps each, and survive restarts. Entries File Explorer needs to open folders, drives, and network locations are protected and cannot be removed, even by a bulk action.
What if the crash is in the Windows 11 compact menu?
Windows 11’s compact menu uses a newer model. Microsoft’s Learn guide on adding a File Explorer context menu command to a packaged app says these commands are implemented by “a native DLL” exposing IExplorerCommand and registered through the app’s package manifest. They are still code, so a buggy one can still misbehave.
ContextCleaner lists these modern items too, including entries from packaged and MSIX apps, so you can hide a suspect entry the same way. Our explainer on right-click items that are not in the registry covers how they are registered.
What should I do once I find the culprit?
You have three options, best first:
- Update the app. The vendor may already have fixed the extension.
- Turn off the app’s Explorer integration in its own settings, if it offers that.
- Keep it blocked in ContextCleaner. The app still works; only its right-click add-on stops loading.
If you need help from the vendor or IT, ContextCleaner can produce a diagnostics report that scrubs folder names, so you can share it without exposing your file structure.
How is this different from a slow right-click menu?
Slowness and crashes have the same root cause, code running inside Explorer, but different urgency. If your menu is slow rather than crashing, start with our guides on a right-click menu that is slow to open and on shell extensions that slow File Explorer.
Frequently asked questions
Will blocking a shell extension break the app?
The app keeps working. Only the right-click integration is disabled. You can unblock it later with undo or a snapshot restore.
Do I need administrator rights to fix this?
For extensions registered for all users, yes. ContextCleaner asks once per apply, not once per entry. Per-user entries need no admin rights.
Can Windows built-in entries cause the crash?
It is much less likely. Third-party extensions are the usual suspects. ContextCleaner marks which entries are built in and protects the ones Explorer needs.
Does ContextCleaner send my data anywhere?
No. It makes no network connections.
Try ContextCleaner
Get ContextCleaner from the Microsoft Store for Windows 11 or Windows 10 22H2, and read the ContextCleaner product page. For a manual approach, see the shell extension manager guide.
Find the add-on behind the crash, block it, and keep undo one click away.
Get it from Microsoft
Microsoft, Windows, and File Explorer are trademarks of the Microsoft group of companies. Other product names are trademarks of their owners. ContextCleaner is not affiliated with or endorsed by any of them.
Last updated 17 October 2026. Published by Automata Labs, a software company in Canada.