Classic Shell Reborn

Windows has no built-in interface for viewing or managing shell extensions. The problem with shell extensions is that they accumulate over time. It scans your Windows installation and displays a complete list of every shell extension registered on the system. Fix slow right-click menus, stop Explorer crashes, and take control of every context menu handler on your system. You can plug the drive into any Windows PC — even one without internet — and immediately diagnose shell extension problems.

• If you are running a modern 64-bit copy of Windows 10 or Windows 11, choose the 64-bit ZIP (~140 KB).
• The problem with shell extensions is that they accumulate over time.
• Removing unwanted items from the Windows right-click menu is ShellExView’s primary use case.
• Version 2.01 supports Windows from XP through Windows 11, works on both 32-bit and 64-bit systems, and the entire program fits in a ZIP file under 140 KB.

Suspicious Extension Highlighting

Disable all thumbnail and preview handlers, restart Explorer, and then re-enable them one by one. ShellExView makes these invisible extensions visible so you can manage them. A single badly coded extension can slow down your entire file browsing experience or cause Explorer to crash. The issue is that Windows loads these extensions every time you interact with Explorer. A shell extension is a small piece of software (usually a DLL file) that plugs into Windows Explorer to extend its functionality.

The ZIP contains just the executable (shexview.exe), a help file (shexview.chm), and optionally a readme. Head to our download section and grab the version that matches your system architecture. No installation wizard, no registry changes, no admin setup required beyond running as administrator on Vista and later. Full CLI interface for scripting disable/enable operations, running exports, and performing remote scans. Connect to other Windows machines on your network and view their shell extensions remotely.

Some context menu entries are static (simple registry-based entries). Note that ShellExView manages dynamic context menu extensions (DLLs). Use the 32-bit version only if you are running a 32-bit copy of Windows (increasingly rare) or if you specifically need to troubleshoot 32-bit shell extensions in isolation on a 64-bit system.

Windows Firewall may need an exception for remote registry access. This is useful for IT administrators who need to troubleshoot Explorer issues on employee workstations without physically going to each machine. On Windows XP and earlier, administrator privileges are not enforced by the OS in the same way, so ShellExView runs with full access for any admin-level user account. ShellExView needs to read and write to registry keys under HKEY_LOCAL_MACHINE and HKEY_CLASSES_ROOT, which are protected areas that require elevated permissions.

One-Click Disable/Enable

ShellExView manages dynamic shell extensions — DLL files registered as COM objects that inject code into Explorer at runtime. Both tools are made by NirSoft and both deal with the right-click context menu, but they target different types of menu entries. This re-enables every extension in the list, including ones that were already enabled (pressing F8 on an enabled extension does nothing, so it is safe). If you change your mind, open ShellExView again, find the disabled entry (it will show “Yes” in the Disabled column), select it, and press F8 to re-enable it. The 64-bit version of ShellExView shows both types in a single list, so it gives you the most complete picture. However, some older applications install 32-bit extensions that run under the WoW64 compatibility layer.

Useful for IT teams tracking which extensions are installed across workstations or building baseline configurations. Save the full extension list in multiple formats for documentation, comparison, or analysis. Unsigned or tampered extensions are flagged, which helps identify software that might have been modified or installed from an unverified source. Everything you need to inspect, manage, and fix Windows shell extensions in one portable tool. Version 2.01 supports Windows from XP through Windows 11, works on both 32-bit and 64-bit systems, and the entire program fits in a ZIP file under 140 KB.

If Explorer crashes immediately when you open certain folders, the problem is likely a thumbnail or preview handler extension. Explorer crashes and the “Windows Explorer has stopped working” error are frequently caused by a online casinos faulty shell extension. Sort by Type and check how many “Icon Overlay Handler” entries are active.

If the menu appears instantly but just has too many items, use ShellMenuView to trim the static entries. These are lightweight entries like “Open with Notepad++” or “Edit with VS Code.” They rarely cause problems but can clutter the menu. These are the more complex (and more problematic) type of context menu handler. Removing that registry value (which is what F8 does) fully restores the extension to its original state. Disabled extensions are not deleted or modified in any way. Search for that DLL filename in ShellExView to find the exact extension responsible.