Find Shell Extensions in Windows Regedit

Shell extensions are COM objects (Dynamic Link Libraries) that customize and expand the Windows interface, such as adding entries to the File Explorer right-click context menu, handling icon overlays, or managing property sheets. In the Windows Registry Editor (regedit), these extensions are not stored in a single unified list; instead, they are cataloged under several specific registry keys depending on their scope, approval status, and handler type.

1. Globally Approved Shell Extensions

Windows maintains a master list of approved shell extension CLSIDs (Class Identifiers). This is the most direct location to see extensions authorized to run in the Windows Explorer process:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved

To find blocked shell extensions, check the companion key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked

2. Context Menu and Object Handlers (shellex)

Specific shell extensions linked to files, folders, and system objects are stored within the shellex subkeys under HKEY_CLASSES_ROOT (or their user-specific counterparts in HKEY_CURRENT_USER\Software\Classes).

All Files and Global Objects

Folders and Directories

Other Handler Types

Within the same paths, replace ContextMenuHandlers with other handler subkeys to locate specific functionality: * PropertySheetHandlers (File Properties tabs) * DragDropHandlers (Right-click drag-and-drop actions) * CopyHookHandlers (Actions intercepting move/delete operations) * IconHandler / IconOverlayHandlers (File icon graphics and overlay badges)

3. Extension Details and DLL File Paths (CLSID)

The keys under shellex and Approved typically reference a CLSID GUID rather than a direct executable path. To locate the actual .dll file powering a specific shell extension:

  1. Copy the CLSID string (including the curly brackets {...}).

  2. Navigate to:

    HKEY_CLASSES_ROOT\CLSID\{YOUR-CLSID-GUID}\InprocServer32

    (Or HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{YOUR-CLSID-GUID}\InprocServer32)

  3. Check the (Default) value, which displays the exact filesystem path to the registered DLL file.