ContextCleaner: see every entry in the Windows 11 right-click menu, and which app added it — on the Microsoft Store.

Last updated:

Guided workflow variation

Every entry came from somewhere.Find out where.

ContextCleaner labels each row with the app, DLL, or package that registered it, the location it was discovered in, and the file types it applies to — so removing it is a decision rather than a guess.

ContextCleaner shows the origin of every right-click entry: the responsible app or DLL, its identifier, where it was found, and which file types it covers. Search or filter by any of those.

Pay once. Own it forever.

One-time purchase on the Microsoft Store · No subscription · Instant install

Buy through the Microsoft Store—instant install, automatic updates, and a Microsoft receipt for easy expensing. No account needed on our site, and no subscription on Store purchases.

Full ContextCleaner overview
One-time purchase No telemetry Local-first

windows 11 & 10 · no regedit · snapshot before every apply · no network requests

If this sounds like your week

A menu label tells you almost nothing useful.

Menu text is chosen by whoever wrote the entry, and it is often generic. "Scan", "Open with", "Share", "Convert" — none of those identify a program. Some entries show no recognisable name at all. When you cannot attribute an entry, you cannot judge whether removing it is safe, and you certainly cannot search for instructions.

Where tooling usually breaks

Attribution is exactly what Windows hides.

The shell resolves an entry to code, runs it, and shows you the result. It never surfaces the chain. Working it out by hand means searching the registry for the label, following an identifier to a class registration, then to a file path on disk — several steps, each easy to get wrong, and none of it available for packaged apps that register through their manifest instead.

Where ContextCleaner lands

Provenance on every row, and searchable.

ContextCleaner resolves that chain during discovery and keeps the result attached to the entry. Each row carries the friendly name, the registered identifier, the backing file or package, the publisher where one is recorded, the discovery location, and the click contexts it applies to — files, folders, empty space, drives, and other targets. All of it is searchable, so you can start from a label, an app name, a DLL path, or an identifier and arrive at the same place.

Pay once. Own it forever.

One-time purchase on the Microsoft Store · No subscription · Instant install

Buy through the Microsoft Store—instant install, automatic updates, and a Microsoft receipt for easy expensing. No account needed on our site, and no subscription on Store purchases.

Learn more about ContextCleaner

windows 11 & 10 · no regedit · snapshot before every apply · no network requests

What you get

Feature highlights

Sees all four menu surfaces

Classic commands, the COM add-ons installed apps register, Windows 11 modern and packaged items, and the New submenu—together in one searchable list.

Shows where every entry came from

Each row names the app, DLL, or package behind it, where it was discovered, and which file types it applies to.

Remove one or clear the whole view

Flip a single toggle, multi-select a batch, or remove every third-party entry in the current view with one button.

A dedicated New menu cleanup

Turn off the document types you never create. The file type keeps working—only the New-menu shortcut goes away, and it is a reversible rename.

Review before anything is written

Changes stage as pending until you press Apply, and machine-wide edits are batched into a single administrator prompt per apply.

Undo that survives restarts

Undo and redo are stored on disk rather than in memory—up to 25 steps each—alongside one-click snapshot restore.

A verifiable record of every change

A hash-chained (SHA-256) local audit log with a one-tap integrity check that reports the exact entry where the chain broke.

Private by default

No network requests at all, no account, no ads, no third-party analytics. Diagnostics exports replace personal folder names first.

Especially when

  • Remove entries from the Windows 11 right-click menu without opening Registry Editor yourself
  • Find out which app added a right-click entry, and why deleting a registry key did not remove it
  • Clean up the right-click New submenu without breaking the underlying file types

Who benefits

Real-world scenarios

The unrecognised entry

There is an entry in your menu with a vague one-word label and no icon you recognise, and you are not comfortable removing something you cannot identify.

The detail pane names the backing file and publisher, so you can decide knowingly — and if you still want it gone, the removal is reversible.

The audit before a rebuild

You are documenting what a machine has accumulated before reimaging it, and need to know which software touched the shell.

Filter to third-party, review the origins, and export a diagnostics report. Personal folder names are replaced before export.

The shared identifier

Four separate menu entries look related and you suspect they come from the same program, but the labels do not match.

They share one add-on identifier in the list, so disabling that add-on clears all four at once instead of four separate attempts.

Deep dive

How an entry is traced back to the app that registered it

Attribution works differently for each of the four menu surfaces, which is why a single lookup method never covers everything.

For classic commands, the entry lives as a shell verb under a file class. The registration itself usually holds the display label and a command line, so the executable is directly readable. The complication is that the same logical entry can be registered per-user, machine-wide, or under a file-type association rather than the obvious class — so the same label can appear from more than one place, and the one that governs what you see is not necessarily the one you found first. ContextCleaner records which location each instance came from, and when it changes an entry it writes to the location that is actually in effect rather than to a parallel one that would have no effect.

For COM app add-ons, the registration is an identifier, not a name. Resolving it to something human-readable means looking up the class registration, reading the backing library path, and reading a publisher value where the app recorded one. Some handlers do not register a friendly name at all, in which case the most reliable label comes from asking the handler itself what it would draw. ContextCleaner does this out-of-process so a misbehaving handler cannot take the app down with it, and falls back to the registry-derived name when a handler does not answer.

For modern menu items from packaged apps, there is no classic registry verb to find. The declaration lives in the package manifest, and the link between the manifest, the identifier, and the package that owns it has to be assembled from the installed-package catalogue. That is why these entries are invisible to registry-only tools and why they are so often the ones that survive every cleanup attempt.

For the New submenu, entries attach to a file extension or a program identifier, so the natural attribution is the file type itself plus whatever program owns that type.

The practical payoff of doing all four is that the list is complete and the attribution is consistent. You can search one field — app name, path, identifier, label — and find every entry connected to a program regardless of how it chose to register. That is the difference between removing an entry and removing a program's presence in your menu.

Trusted by pragmatic desktop users

Built for people who prefer tools that stay local.

Real workflows: focus timers that stay visible, batches that never leave the disk, and renames you can rewind.

Customer review 01

PinPoint: Always On Top saves me so much time as I can organize all my report materials without having to flip between windows or tabs. I love the fact that it is straightforward and simple.

Senior Accountant · Manufacturing Company · United States · PinPoint Reviewed About PinPoint
Customer review 02

I used to get so frustrated when my Taskbar would freeze and disappear. Taskbar Sentinel has eliminated that pain without subjecting me to another subscription.

Darren · Calgary, Alberta, Canada · Taskbar Sentinel Reviewed About Taskbar Sentinel
Customer review 03

OpticBatch and MetaForge are a lifesaver for me as a person with a passion for photography. They give me the ability to stay organized and keep personal information confidential when I post pictures online.

Sherri · United States · OpticBatch & MetaForge Reviewed Browse the full catalog

Quotes are shown with customer permission; names and locations appear as reviewers provided them.

Our Core Moat

Engineered to respect your system boundaries.

System Resource Monitor (Idle State Comparison)
Automata Labs low idle memory footprint compared to generic Electron applications

Lightweight Native Stack

Compiled Rust core wrapped inside an optimized Tauri shell. No heavy background node loops or duplicate Chromium engines cooking your memory footprint (<25MB idle RAM).

100% Local-First Privacy

Executes entirely on-device with full offline isolation. Absolute zero background telemetry policies, no metrics aggregation, and zero mandatory cloud-sync accounts.

Perpetual Fallback Licenses

Pay a single, clear one-time purchase price. Own your specific native software utility execution tier permanently without artificial subscription paywalls or ongoing usage tax.

FAQ

Straight answers—no glossary dump

How do I tell which program added a right-click menu entry?

ContextCleaner shows it directly on each row: the app or DLL behind the entry, its registered identifier, the publisher where one exists, and the location it was discovered in. You can also search by any of those fields.

Some entries have no recognisable name. Can they still be identified?

Usually, yes. When a handler does not register a friendly name, ContextCleaner asks the handler what label it would draw, in a separate process so a faulty handler cannot crash the app. If it does not answer, the registry-derived name and the backing file path are still shown.

Can I remove everything one app added, in one step?

For COM add-ons, yes — entries that share an identifier are removed together when you disable that add-on. For an app that registers across several surfaces, search by its name to see all its entries and select them as a batch.

Does removing an entry uninstall or break the app?

No. Removals are non-destructive: classic entries are marked hidden, add-ons are added to a block list rather than unregistered, and New-menu items are renamed. The app stays installed and works normally; it just stops drawing into the shell menu.

What does it need to run?

Windows 11 or Windows 10, and the Microsoft Edge WebView2 runtime, which is already present on virtually all Windows 11 PCs. ContextCleaner does not install WebView2 for you. It runs as a standard user; only machine-wide entries need administrator approval, requested once per apply.

Is it private, and how do I get it?

ContextCleaner makes no network requests at all — it requests no networking permission from Windows, so there is no telemetry, no analytics, no ads, and no account. Snapshots and change history stay on your PC. It is a one-time purchase on the Microsoft Store; use the Microsoft Store button on this page for the current listing and price.

Every right-click entry,
and the app that put it there.

ContextCleaner scans all four surfaces Windows builds the right-click menu from—classic commands, app add-ons, Windows 11 modern and packaged items, and the New submenu—names the app behind each entry, and lets you remove what you never use without opening Registry Editor. A snapshot is written before each apply, and undo survives restarts.

Pay once. Own it forever.

One-time purchase on the Microsoft Store · No subscription · Instant install

Buy through the Microsoft Store—instant install, automatic updates, and a Microsoft receipt for easy expensing. No account needed on our site, and no subscription on Store purchases.

Open full product page

Technical specifications

Technical specifications for procurement

Spec Implementation
Data Sovereignty Menu edits, snapshots, and the full change history stay on your PC; diagnostics exports replace personal folder names first
Telemetry Status None; no account, no ads, no third-party analytics
Core Runtime Tauri 2 + Rust native Windows app; requires the Microsoft Edge WebView2 runtime, which it does not install for you
Network Requirements Makes no network requests at all and requests no networking permission from Windows
Deployment Compatibility Windows 11 and Windows 10; no version gating, so Windows 10 simply shows fewer modern and packaged entries. Microsoft Store
Scope All four menu surfaces: classic commands, COM app add-ons, Windows 11 modern and packaged items, and the New submenu
Provenance Each entry names the app, DLL, or package behind it, where it was discovered, and the file types it applies to
Reversibility Snapshot written before each apply (the apply stops if it cannot be saved), one-click restore, and disk-persisted undo and redo up to 25 steps each
Guardrails Entries File Explorer depends on are protected from removal even by bulk actions; machine-wide edits use one administrator prompt per apply
Accountability Tamper-evident, hash-chained (SHA-256) audit log with one-tap integrity verification, stored only on your PC
Access System tray presence with a customizable hotkey and Ctrl+K quick actions across 14 rebindable shortcuts
Approximate size 30 MB installed or less