Hunter Mode in practice
Tray applets, portable folders, and duplicate entries after upgrades.
Hunter Mode is best thought of as a targeting scope: it helps you jump from “something on screen” to “the underlying executable, shortcut, or service entry” without guessing paths in Explorer. It shines when Add/Remove Programs is empty, misleading, or duplicated—but it does not replace judgment about shared components.
Tray tools and notification icons
Drag the crosshair onto a tray icon when you want to identify which process owns it. Before you uninstall or delete anything, confirm the publisher path: shell extensions and cloud sync clients sometimes register under names that look unrelated. If the target lives under System32 or a broad “Windows” vendor path, stop and research—those are rarely exclusive to one consumer app.
- Close the app normally first; Hunter Mode is for discovery, not a substitute for a clean exit.
- If multiple icons share one host process, removing “the wrong” piece can affect several tools at once.
Portable folders and side-loaded tools
Portable apps often have no Add/Remove entry. Hunter Mode can still reveal the folder, Start-menu shortcuts, and sometimes firewall or autorun hooks the tool created manually. Capture what you find in a short note before you delete, so you can restore if a script or game launcher still expected that path.
Prefer deleting the portable tree as a unit after you confirm nothing else references it. Avoid cherry-picking DLLs inside the folder unless you know they are not redistributables bundled for that app only.
Duplicate listings after upgrades
Major in-place upgrades or vendor reinstallers occasionally register the same product twice—one stale, one current. Remove the stale entry first (the one with the older install date or broken shortcut), reboot if the vendor asks, then run a leftover scan on the remaining entry. Trying to delete both at once often produces overlapping registry keys and a noisier scan.
When Hunter Mode is the wrong first step
If the program still appears in Settings → Apps with a working uninstall entry, use that path first. Hunter Mode does not magically uninstall better than the vendor’s script; it maps UI to files so you do not fly blind. The same applies to Store-delivered apps: use the appropriate removal flow for that channel before you hunt stray shortcuts.
After you identify the target
Write down the full path and parent process you saw. If you later run a leftover scan, you can reconcile Hunter’s findings with registry rows instead of deleting twice from muscle memory. If the item was a context-menu shell extension, reboot once and re-test Explorer before you declare victory—some extensions cache until session restart.
Quick answers
- Does Hunter Mode uninstall programs by itself?
- No—it helps you aim at the executable, shortcut, or window you are curious about. You still decide whether to use the normal uninstaller, delete a portable folder, or leave shared components alone.
- The crosshair points at something in System32. Now what?
- Treat that as a research task, not a green light to delete. Note the exact path and DLL name, then search who loads it. Many tray tools host UI in user space while legitimately touching system libraries.
- I found two shortcuts to the “same” app. Which is safe?
- Compare targets: one may point at an old version folder after an upgrade. Remove the broken or older target first, reboot if needed, then rescan so the leftover list is not duplicated noise.
Keep going: After you map a target with Hunter Mode, run the normal uninstall path when it exists, then circle back with a leftover scan for stragglers. See the features overview and guides for how Revo fits into a full cleanup workflow.