Leftover context menu after uninstall: registry and ShellExView orphans

Published October 2026, Windows 11 24H2 / 25H2 and Windows 10

You uninstall Notepad++ / WinRAR / an old cloud client / a PDF tool. The program is gone. The right-click entry remains, sometimes delaying the menu while Explorer tries to load a DLL that no longer exists.

Those leftovers are registrations, not ghosts in the Start menu. Clear them with ShellExView first, then targeted registry cleanup when the orphan key still sticks.

What an orphan looks like

Signs:

• Menu label for software you already removed.
• Brief delay or error when right-clicking after uninstall.
• ShellExView row with empty or invalid File Extensions / missing file path.
• regedit ContextMenuHandlers key whose CLSID InprocServer32 points at a path under Program Files that is gone.

Working uninstallers remove files and COM registration. Partial uninstallers leave COM behind.

Step 1: Find orphans in ShellExView

1. Install or open ShellExView as Administrator.
2. Options → hide Microsoft extensions for a clearer third-party list.
3. Sort by Filename or Company. Look for the uninstalled product name.
4. Check the file path column. If the DLL is missing, you have an orphan.
5. Select it → F7 Disable (immediate relief) or use ShellExView’s remove option if you use that workflow carefully.
6. Restart Explorer. Confirm the menu label is gone or no longer stalls.

Cross-check weird names in the DLL checker.

If many unknowns exist, binary-search enabled non-Microsoft context menus until the stall disappears, then delete only the orphan you identified (Disable shell extensions on Windows 11).

Step 2: Registry map (export before edit)

These are the common context menu attachment points. Browse first; delete only keys you can tie to the orphan CLSID.

HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers
HKEY_CLASSES_ROOT\AllFilesystemObjects\shellex\ContextMenuHandlers
HKEY_CLASSES_ROOT\Directory\shellex\ContextMenuHandlers
HKEY_CLASSES_ROOT\Directory\Background\shellex\ContextMenuHandlers
HKEY_CLASSES_ROOT\Folder\shellex\ContextMenuHandlers
HKEY_CLASSES_ROOT\Drive\shellex\ContextMenuHandlers
HKEY_CLASSES_ROOT\CompressedFolder\shellex\ContextMenuHandlers
HKEY_CLASSES_ROOT\SystemFileAssociations\<ext>\shellex\ContextMenuHandlers

Also check legacy verb keys (not shellex) when the leftover is a static command:

HKEY_CLASSES_ROOT\*\shell
HKEY_CLASSES_ROOT\Directory\shell
HKEY_CLASSES_ROOT\Directory\Background\shell
HKEY_CLASSES_ROOT\Drive\shell

64-bit Windows may mirror older 32-bit registrations under WOW6432Node paths. If ShellExView shows a 32-bit location, look there.

CLSID confirmation

Handler keys usually store a CLSID like {GUID} as the default value. Resolve it:

HKEY_CLASSES_ROOT\CLSID\{GUID}\InprocServer32

If the default value is a missing DLL path, the registration is safe to remove after backup. Delete:

1. The ContextMenuHandlers\Name subkey that references the GUID.
2. Optionally the CLSID{GUID} tree if nothing else references it (only when you are sure).

Prefer renaming MyOldApp to backup_MyOldApp before permanent delete. Restart Explorer and test.

Step 3: Icon overlays and static leftovers

Uninstalled cloud tools leave overlay identifiers:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ShellIconOverlayIdentifiers

and the WOW6432Node counterpart. Rename leftover vendor overlay keys with a z prefix or remove the orphan key after export. Overlays rarely create menu labels but can keep Explorer busy.

SendTo shortcuts under %APPDATA%\Microsoft\Windows\SendTo are not COM orphans; delete unused shortcuts directly.

Step 4: App Paths and installer leftovers

If the uninstaller left a repair entry:

1. Settings → Apps: remove any remaining “helper” or “shell integration” packages for that vendor.
2. Re-run the vendor’s official remover if they publish one (Adobe Creative Cloud Cleaner, old archive uninstall tools, etc.).
3. Re-check ShellExView afterward; official cleaners often miss ContextMenuHandlers.

Safe cleanup order (do not skip)

1. Backup: create a System Restore point or export the specific registry branch.
2. Disable orphan in ShellExView and verify menu behavior.
3. Rename handler key under ContextMenuHandlers.
4. Restart Explorer; confirm.
5. Delete the renamed key and unused CLSID only after a day of normal use.
6. Avoid random “context menu cleaner” freeware that deletes Microsoft entries wholesale.

Common vendor leftover patterns

Work through the table only for software you actually removed. Do not strip every Background handler because one PDF verb lingered.

PowerShell inventory (read-only)

For a quick list of ContextMenuHandlers names without clicking through regedit:

Get-ChildItem "Registry::HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers" |
  Select-Object PSChildName
Get-ChildItem "Registry::HKEY_CLASSES_ROOT\Directory\Background\shellex\ContextMenuHandlers" |
  Select-Object PSChildName

Compare the names to ShellExView. If a name belongs to an uninstalled app and the CLSID path is dead, that is your cleanup target. Still export before deleting.

When the leftover still appears

• You are looking at a different handler with a similar label (for example two PDF tools).
• The entry comes from a Group Policy / enterprise-deployed AppX package.
• Windows Terminal / inbox verbs (not third-party) need settings cleanup instead of CLSID deletion.
• Explorer cached the menu; restart Explorer again or reboot once.
• A second user profile still has per-user HKCU shell additions. Check HKEY_CURRENT_USER\Software\Classes for mirroring ContextMenuHandlers if HKCR cleanup was not enough.

If Explorer crashes while opening the menu after uninstall, capture the faulting module (Find which shell extension is crashing Explorer) and remove that registration path.

24H2 / 25H2 notes

Feature updates do not reliably purge third-party orphans. Driver or Store repairs can resurrect GPU or Terminal verbs, which are not the same as dead WinRAR keys. After major upgrades, skim ShellExView for pink/missing paths once.

For general lag after cleanup, return to Windows 11 context menu slow fix.

Related guides

• Disable shell extensions on Windows 11
• Windows 11 context menu slow fix
• Find which shell extension is crashing Explorer
• ShellExView download
• DLL checker