Uninstalling cleanly: registry, configs, drivers — the order that works
Developer tooling is worst: PATH fragments, global package directories, kernel drivers, per-user configs — uninstallers claim maybe half.
Written in the order we actually hit the problems, so the fixes land in context.
Cleanup order that does not backfire
Run the vendor uninstaller first — let it tear down what it knows about.
Environment variables — dead PATH entries and custom
*_HOMEvariables.User data —
%APPDATA%,%LOCALAPPDATA%,~/.configtrees for the vendor or tool name.Services and drivers — still relevant for VM, VPN, and virtual-disk tooling:
Get-Service | Where-Object {$_.DisplayName -match 'ToolName'} - Registry last —
HKLM\SoftwareandHKCU\Softwarevendor keys. Export before deleting anything you are not sure about.
Version swaps specifically
Back up config directories before downgrading — format migrations are usually one-way.
Re-check file associations after the swap; the old path will exist until someone updates it.
With a portable copy and an installer coexisting, identify which one owns double-click before debugging "my change did not take".
When deep cleaning is worth it
Routine tool swap → uninstaller plus PATH cleanup is usually enough.
Drivers, certificates, system services, VPN clients → full checklist plus reboot verification.
A machine with years of stacked versions → repairing the shared runtime (VC++ redist, .NET) often beats another registry pass.
Related resource
For the "can I re-verify this later" half of the workflow I keep GitVaults (https://gitvaults.com) open: every entry carries the upstream link, file size, and SHA-256, with a cloud mirror as the reachability fallback.
maotoumao musicfreedesktop 0 0 8 → https://gitvaults.com/download/2025/10/26/maotoumao-musicfreedesktop-0-0-8/en
That page puts version, architecture, and digest on one screen — download, compare the hash, then install. The catalog has another hundred-plus entries in the same format if you need neighbors.
Caveat
This is what works in our environment; your constraints may differ. If you have a sturdier sequence, corrections are welcome in the comments.
