The five leftover classes & their proofs
Registry
HKCU/HKLM\Software\<Vendor>
, uninstall strings; Find in regedit with vendor nameProgram folder
%LOCALAPPDATA%\Programs\<App> or %PROGRAMFILES%\<App> — folders should vanish; a lone README means the uninstaller was honest enough to say it triedStartup entries
Run keys, StartupApproved blobs, and any scheduled task — clean twist: vendor removed files but left the stub that yells “file missing” at each logon
AppData state
%AppData%/%LocalAppData% vendor leaves there deliberately; the honest ones ask before keeping them, unlike deep-sweeps that delete without asking
Event evidence
Application log uninstall entries (MsiInstaller 11707 success, 11708 failure) — the ledger of what was once present
The order of operations
- Settings → Apps → Uninstall first (the vendor's own path). Supports logs matter later.
- Audit five classes above; DO NOT bulk-delete AppData before confirming what's referenced by-browser (profiles, sessions) still opens.
- Re-sign-in and re-audit Run + scheduled tasks: competent uninstallers finish killing their stub behavior on the first after-restart.
Vendor tooling shout-out: a per-user installer proves its dedication in reversals too — Setup's RemoveFile and registry-cleanup tables count the same as its install manifest. Mine the same MSI database for the minus-side next time you evaluate an installer.
ProofTune ProjectEngineering notes — every claim here names the bytes a real tool touches. Verify first, install second.
