Context Menu Manager Plus: a Windows right-click menu manager that quarantines new entries before they appear

The problem: software that writes itself into your right-click menu

Installing a Windows application often adds entries to the shell context menu, and the user is rarely asked. Context Menu Manager Plus exists to invert that: in the README's words, it turns the menu from software deciding what it may insert into the user deciding what stays. The project is aimed at Windows 10 and Windows 11 users who want to audit and control those entries, not just hide a few of them. It is explicitly not a simple on/off switch. The scope covers classic shell and shellex entries, Windows 11 Packaged COM and AppX entries, and special entry points such as New, Send To and Win + X, which the README notes do not behave like ordinary shell entries.

Intercept first, review later: the review queue design

The distinguishing design choice is stated as the project's most important goal: when a new context menu entry is detected, the tool tries to disable or intercept it before it becomes visible, then places it in a pending review page. The user chooses one of three actions: allow (enable the entry), keep disabled (retain the entry but leave it off), or remove (delete it from the registry or the review queue). Detection runs against external changes: the README lists newly added third-party entries, known entries being restored or deleted, and mismatches between registry state and local state. The same logical entry is aggregated rather than listed repeatedly, and TrayHost can raise a notification and pull up the frontend for handling. This is the part that separates it from a plain menu toggle tool, and it is also the part that depends on the background service being installed and running.

Architecture: a service, a WPF frontend, a tray host and a probe process

The repository is split into ContextMenuMgr.Backend, ContextMenuMgr.Frontend, ContextMenuMgr.TrayHost, ContextMenuMgr.ProbeHost, ContextMenuMgr.Contracts and ContextMenuMgr.Tests, with an Installer directory and build scripts at the root. The stack is .NET 10, WPF, WPF-UI, Named Pipe IPC, a Windows Service, a native Win32 tray host and a separate ProbeHost process for Shell Extension analysis. Responsibilities are divided: the frontend handles interaction, the backend service performs scanning and registry operations, and TrayHost owns notifications and the tray entry point. Shell Extension probing runs in ProbeHost as an isolation boundary, so a failed probe normally does not affect ordinary menu management. That separation is a reasonable answer to a real problem, because third-party shell extensions are arbitrary native code and loading them in-process is how a menu manager crashes.

Installing Context Menu Manager Plus and handling your first pending entry

Three install paths are documented. The GitHub Releases page is the manual route: expand Assets and pick the file matching your architecture and install scope; the README suggests x64-self-contained for most machines. WinGet and Scoop are the package manager routes. The WinGet commands install the stable or beta channel:

winget install PLFJY.ContextMenuMgrPlus
winget install PLFJY.ContextMenuMgrPlus.Beta

For Scoop you add the project bucket first, then install:

scoop bucket add PLFJY https://github.com/PLFJY/scoop-bucket.git
scoop install PLFJY/ContextMenuMgrPlus
scoop install PLFJY/ContextMenuMgrPlus-Beta

After installation, the settings page is where the service is installed, repaired or uninstalled, and where you can restart Explorer, set the log level, enable start with Windows, and toggle registry protection. The first real use is the pending review page: when the backend detects a new entry it appears there, and you choose allow, keep disabled, or remove. If nothing shows up, check the backend and trayhost logs before assuming detection is broken; the README states that logs are usually more useful than the interface when edge cases appear.

Where it breaks: registry ACLs, security software and best-effort parsing

The README's own caution list is unusually direct. Registry modification is involved, so the tool deserves care. Delete, disable and ACL protection operations can be affected by system permissions, security software or Windows protection mechanisms, and some system-protected registry root keys cannot have their ACLs changed by ordinary means at all, which the README attributes to a Windows limitation rather than a bug. Security software may block deletion, restoration, registry writes or Shell Extension probing. Icon, display name, command text and CLSID metadata parsing are best-effort and do not guarantee coverage of every third-party entry. Shell Extension deep analysis is likewise best-effort, and the README says failure is usually normal. User-level entries, system-level entries, PackagedCom and ShellEx/CLSID entries do not behave identically, so a fix that works for one class may not transfer. There is also a self-imposed constraint: with registry protection on, some software or driver installers may be unable to write context menu related keys, so the README advises turning it off temporarily before installing such software.

How it differs from ContextMenuManager and Easy Context Menu

The README credits BluePointLilac/ContextMenuManager and branhill/windows-11-context-menu-manager as major references, so the lineage is openly acknowledged. The difference in approach is the review queue and the interception step. A conventional manager presents the current menu contents and lets you enable, disable or delete entries; the decision happens after the entry is already live, and if you do not open the tool, nothing changes. Context Menu Manager Plus tries to catch new entries first, disable them, and surface them for a decision, with TrayHost notifying you. That is a heavier design: it requires a Windows service, named pipe IPC and a tray process to be running, and it is why the settings page carries service install, repair and uninstall controls. If you want a single portable executable you open occasionally, the older single-process model is simpler and has fewer moving parts to break.

Licence, maintenance and the cost of upgrading

The project is licensed GPL-3.0, and the repository ships a LICENSE file. For anyone embedding it in a commercial product or shipping a modified fork, that copyleft obligation is the thing to read, and a lawyer is the right person to read it, not this article. On maintenance, the last push to main was on 2026-09-23, and v1.7.6 was released on 2026-09-22, one day earlier, with v1.7.5 on 2026-09-12. The repository is not archived. The upgrade cost is not zero: the tool installs a Windows service and a tray host, so an upgrade means the service is replaced and Explorer may need restarting, which the settings page provides a control for. The README also warns that a substantial part of the code was AI-assisted and then worked over by hand, and that omissions, insufficient edge-case handling and behaviour that differs from expectations are still possible. Treat version pinning as reasonable if you depend on a specific registry protection behaviour, and check the beta channel separately if you want fixes early; the beta is published as its own WinGet and Scoop package.

Editorial conclusion

Adopt Context Menu Manager Plus if you want a review gate in front of third-party context menu entries on Windows 10 or 11, and you are comfortable with a tool that edits the registry and installs a Windows service. Do not adopt it if you only need to toggle a handful of built-in entries once, or if you cannot tolerate best-effort metadata parsing and Shell Extension probing that the README says fails often enough to be normal. Verify first that the release asset matches your architecture and install scope (x64-self-contained is the README's default suggestion), that your security software does not block registry writes or Shell Extension probing, and that the registry protection switch is off before you install drivers or software that writes menu entries.

Frequently asked questions

Official sources

1. License: GPL-3.0
2. PLFJY/ContextMenuMgr on GitHub
3. Project website
4. README
5. Releases