Dev stacks: order matters
SDKs, PATH clutter, and when Revo should not be the first tool you open.
Developer machines accumulate layers: compilers, container engines, local databases, Android emulators, and language runtimes that each register services, virtual adapters, or scheduled jobs. Revo is excellent at catching stray shortcuts and autostart entries after a vendor uninstaller quits—but it should rarely be the first tool you reach for when a product ships its own teardown workflow.
Shut down moving parts first
Stop WSL instances, shut down VMs, exit IDEs that host language servers, and quit Docker Desktop (or the engine service) before you delete large trees under Données d'application or Données du programme. File locks and hypervisor hooks are the usual reason “uninstall succeeded” yet folders remain.
- Prefer each product’s control panel or CLI uninstall for IDEs, SDKs, and database servers; they understand services and drivers.
- After the official path, use Revo to sweep autostart entries, firewall rules you recognize as app-specific, and orphaned profile folders.
Package managers are not mirrored in Add/Remove
npm, pip, cargo, and similar tools install thousands of small packages that never appear as discrete Windows programs. Run the documented removal command (npm uninstall -g …, pip uninstall …) before you manually delete cache directories, or you will desync metadata from disk.
Side-by-side language runtimes
When multiple JDKs or Python versions coexist, remove only the version you intend to retire. Check your IDE and CI scripts for hard-coded paths first—many teams still point to a minor version folder even when “latest” is installed. After removal, open a fresh terminal and verify java -version or python --version reports what you expect.
Containers, emulators, and virtual switches
Docker Desktop, Android emulators, and some VPNs install virtual network adapters. If networking acts odd after a cleanup, compare adapter names in ncpa.cpl against the vendor’s documented list before you delete “unknown” miniport drivers. Prefer removing the product that owns the adapter, not the adapter entry in isolation.
PATH length and duplicate entries
Old toolchain versions sometimes leave duplicate PATH segments that push you near Windows’ environment-variable limits. After uninstalling SDKs, open a new terminal and print PATH to confirm there are no stale directories prepended ahead of the runtime you meant to keep. CI agents on the same machine benefit from the same sanity check.
Réponses rapides
- Can I delete node_modules with Revo instead of the package manager?
- You can delete the folder, but you may leave global CLI shims or PATH entries pointing nowhere. Prefer the tool’s uninstall/remove commands first, then sweep stragglers.
- Docker left virtual switches. Is Revo the fix?
- Use Docker’s own reset/uninstall flows so vEthernet adapters and Hyper-V hooks are removed in a supported order. Revo is for leftovers after that engine exits cleanly.
- I removed Python but py still launches something.
- Check the Windows App Execution Alias page, pyenv, and stale PATH entries. Multiple launchers can coexist; verify which binary wins in a new shell.
Keep going: After toolchain removals, smoke-test builds, containers, and IDEs in a clean shell so PATH and services agree with reality. See the features overview and guides for Windows-side cleanup next to your CLI workflows.