A practical guide for cleaning the right-click menu in Windows 10 and Windows 11: remove app entries safely, edit Send To shortcuts, disable registry verbs, hide advanced commands, and restart File Explorer after changes.
The Windows context menu is the menu that appears when you right-click a file, folder, drive, desktop area, or empty space inside File Explorer. It gives quick access to actions such as Open, Copy, Rename, Properties, archive tools, cloud storage commands, antivirus scans, image converters, code editors, and other app-specific shortcuts.
Over time, the menu can become crowded because many programs add their own entries during installation. Some entries are useful, but others slow down right-clicking, make the menu hard to scan, or remain after the related program is no longer used.
Removing unused entries makes the right-click menu easier to read and faster to use.
Broken shell extensions can delay File Explorer when you right-click files or folders.
Hiding rarely used commands reduces the risk of clicking the wrong app action.
Context menu entries can be simple shortcuts, app settings, registry verbs, or COM-based shell extensions. Some are safe to remove from a user interface. Others require Registry Editor, so it is important to back up the key before editing anything.
CLSID keys without identifying the app.SystemPropertiesProtection and press Enter.In Registry Editor, right-click the key you plan to change and select Export. Save the file with a meaningful name. If something goes wrong, you can double-click the exported .reg file to restore the old state.
reg export "HKCU\Software\Classes\*\shell" "%USERPROFILE%\Desktop\context-menu-backup.reg" /yBefore deleting anything, identify the source of the entry. The same right-click menu can be built from several locations, and each location requires a different cleanup method.
| Menu area | Common source | Best cleanup method |
|---|---|---|
| Main right-click menu | App setting, static registry verb, or shell extension | Disable it in the app first, then check registry keys if needed |
| Show more options | Legacy context menu handlers and classic shell verbs | Registry cleanup or shell extension manager |
| Send To | Shortcuts in the user SendTo folder | Delete or move shortcuts from shell:sendto |
| New | ShellNew registry entries for file types |
Disable the related ShellNew entry carefully |
| Open With | File association history and application registrations | Reset default apps or clean file association entries |
The safest rule is simple: start with the program that added the entry. Use registry methods only when the program does not provide a setting or when a broken item remains after uninstalling the app.
Many apps that add right-click entries also include a setting to turn them off. This is the cleanest method because the app removes its own integration without leaving broken registry references.
This approach is especially common for archive tools, cloud storage clients, developer tools, image editors, backup apps, antivirus utilities, and media converters.
If you no longer use the program, uninstalling it is often better than only hiding its context menu item. This removes the application, its background services, and most shell integration components.
If the context menu item remains after uninstalling the program, it may be an orphaned registry entry. In that case, use the registry sections below.
The Send To submenu is one of the easiest parts of the context menu to clean. Most items in it are shortcuts stored in a normal user folder.
shell:sendto and press Enter.shell:sendtoDeleting a shortcut from this folder does not delete the real destination. For example, removing a printer shortcut or folder shortcut from Send To only removes it from the submenu.
Some context menu entries are simple registry commands called verbs. These entries usually live under a shell key and have a command subkey that points to an executable file.
| Registry path | Where it appears |
|---|---|
HKEY_CLASSES_ROOT\*\shell |
Right-click menu for all files |
HKEY_CLASSES_ROOT\Directory\shell |
Right-click menu for folders |
HKEY_CLASSES_ROOT\Directory\Background\shell |
Right-click menu on empty folder background |
HKEY_CLASSES_ROOT\Drive\shell |
Right-click menu for drives |
HKEY_CLASSES_ROOT\Folder\shell |
Right-click menu for folders and shell folders |
HKEY_CURRENT_USER\Software\Classes\*\shell |
Per-user entries for all files |
HKEY_CLASSES_ROOT is a combined registry view that includes machine-wide and user-specific file association data. If you do not find an entry under HKEY_CLASSES_ROOT, also check HKEY_CURRENT_USER\Software\Classes and HKEY_LOCAL_MACHINE\Software\Classes.
For many static verbs, you can hide the entry without deleting the whole key by adding an empty string value named LegacyDisable under the verb key.
command subkey.LegacyDisable.reg add "HKCU\Software\Classes\*\shell\ExampleCommand" /v LegacyDisable /t REG_SZ /fIf you do not want to remove a command completely, you can make some static verbs appear only when you hold Shift while right-clicking. Add an empty string value named Extended to the verb key.
reg add "HKCU\Software\Classes\*\shell\ExampleCommand" /v Extended /t REG_SZ /fLegacyDisable and Extended work for many static verbs, but they do not disable every type of context menu item. COM-based shell extensions are handled separately.
Many third-party programs add right-click entries through ShellEx context menu handlers. These are COM shell extensions registered in the Windows registry. They are more powerful than simple verbs and can generate dynamic menu items depending on the selected file.
| Registry path | Typical menu target |
|---|---|
HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers |
All files |
HKEY_CLASSES_ROOT\AllFilesystemObjects\shellex\ContextMenuHandlers |
Files and folders |
HKEY_CLASSES_ROOT\Directory\shellex\ContextMenuHandlers |
Folders |
HKEY_CLASSES_ROOT\Directory\Background\shellex\ContextMenuHandlers |
Empty folder background |
HKEY_CLASSES_ROOT\Drive\shellex\ContextMenuHandlers |
Drives |
HKEY_CLASSES_ROOT\Folder\shellex\ContextMenuHandlers |
Folders and shell folders |
ContextMenuHandlers locations above..disabled to the end of its name.Renaming the handler key is safer than deleting it because you can restore it by renaming it back. If the menu item disappears and everything works correctly, you can keep it disabled.
HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers\ExampleHandler.disabled
The Open With menu can become cluttered when Windows remembers old apps or when several programs register themselves for the same file type. The safest fix is to reset or change the default app first.
.jpg, .txt, or .pdf.Advanced users can also inspect OpenWithList and OpenWithProgids registry entries for a specific extension, but this should be done only after exporting the related keys.
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.extension
Windows may not show registry and shell integration changes immediately. Restarting File Explorer is faster than rebooting the whole computer.
taskkill /f /im explorer.exe
start explorer.exeIf the item still appears, restart the computer. Some shell extensions are loaded by background components and may not unload until after a full sign-out or reboot.
The restore method depends on how you removed the item.
| How it was removed | How to restore it |
|---|---|
| Disabled in app settings | Open the app settings and enable Explorer or context menu integration again |
| Program was uninstalled | Install the program again |
| Send To shortcut was deleted | Recreate the shortcut in shell:sendto |
LegacyDisable value was added |
Delete the LegacyDisable value from the verb key |
| Handler key was renamed | Rename it back to the original key name |
| Registry key was deleted | Import the exported .reg backup or use System Restore |
To restore a registry export, double-click the saved .reg file and confirm the merge. Then restart File Explorer.
HKEY_CURRENT_USER and HKEY_LOCAL_MACHINE locations.shell and shellex\ContextMenuHandlers entries.A clean right-click menu is easier to maintain if you prevent clutter instead of removing everything later.
The best way to remove unwanted Windows context menu items is to start with the app that added them, then use simple folders such as shell:sendto, and only then move to Registry Editor. For static verbs, LegacyDisable or Extended can hide commands without deleting them. For ShellEx handlers, export the key and rename it instead of removing it permanently.
After every change, restart File Explorer and test one file type at a time. A careful, reversible approach keeps the menu clean without breaking File Explorer or installed applications.