Home / Guides
Common problems & fixes
These are distilled patterns from help forums and IT benches. They are not a substitute for vendor documentation, but they tell you what to try before you escalate or reinstall Windows.
Suggested order
- Use Settings or the program’s own uninstaller.
- Reboot if services or drivers were involved.
- Open Revo, scan leftovers, delete only what clearly belongs to the app.
- Verify the app is gone: Start menu, startup, scheduled tasks.
The uninstaller crashes halfway
Try forced uninstall if the product is half-removed, then scan for leftovers. Stop related services, reboot, then delete locked files.
The app still appears in the Start menu
Shortcuts can outlive the executable. Use Hunter Mode on the shortcut or remove stale links after checking the target path.
Security software blocks removal
Allow the vendor uninstaller temporarily, finish removal, then turn protection back on. Log exceptions if your workplace requires it.
Unsure which registry keys are safe
Prefer keys that name the product or its install path. Avoid bulk-removing shared Microsoft or runtime hives.
“Access denied” on folders or DLLs
Take ownership only when you understand the path. Close the app, end stray processes in Task Manager, then retry. Sometimes a second reboot clears file locks from a failed update.
Multiple versions of the same runtime
Older games and CAD tools may need specific Visual C++ redistributable years. Uninstall only the version tied to the program you removed; leave the rest unless a dependency scanner says otherwise.
VPN, firewall, or filter drivers linger
Network stack software often ships a dedicated removal tool. Run it before deleting driver packages. Check adapter bindings and DNS after removal.
Cloud sync folders refuse to delete
Pause sync, sign out, uninstall the cloud client from official channels, then remove empty profile folders. Do not brute-delete occupied databases while the service is running.
Gaming clients and launchers
Uninstall games inside the client first to avoid huge orphaned libraries. Clear download caches only after you confirm no other account on the PC needs those files.
IDEs and dev stacks (Node, Python, Docker)
Remove extensions and global tools from the vendor’s own UI first. Virtual machines and WSL distros are separate: uninstall the guest OS or unregister distros before deleting big folder trees under your user profile.
Printer and scanner bundles
OEM packages often add monitor services and firewall rules. Use the manufacturer’s removal utility when available, then clear old driver packages from Print Management if you no longer own the device.
“Repair” vs “Uninstall” from Control Panel
If repair finishes cleanly, run uninstall again. If repair fails with the same error, log the code, try the vendor’s offline cleanup tool, then consider forced uninstall plus a cautious leftover scan.
Audio interfaces, ASIO, and DAW bundles
Drivers sit close to the kernel. Use the manufacturer’s uninstaller or driver package removal first. Reboot before you delete plugin folders; otherwise DAWs may hold DLL locks and look “stuck.”
Adobe-style creative clouds
Desktop helpers, sync agents, and license validators often outlive the editor. Sign out in-app, run the vendor’s cleaner if provided, then scan. Expect large caches under user profiles; delete only after sync is off.
Hypervisors (Hyper-V, VMware Workstation)
Remove virtual switches and checkpoints from the product UI. If Windows features were enabled for virtualization, turn them off from Optional Features after guests are gone, then reboot before deleting virtual disk folders.
Insider or beta builds of the same app
Side-by-side installs can register under similar names. Note build numbers in Add/Remove Programs. Uninstall the beta channel first, reboot, then scan so you do not remove stable binaries another shortcut still points to.
MSI-based vs custom EXE installers
MSI packages often respect standard logging and repair flags; EXE wrappers may hide nested steps. If the vendor documents silent uninstall switches, use them for scripting first, then let Revo handle stragglers. Mixed upgrade chains (MSI over old EXE) may need two passes.
Remote Desktop: uninstall looks “frozen”
Graphical installers sometimes wait for a dialog you cannot see over RDP. Switch to console session if policy allows, or run the vendor’s documented silent mode. Never force-kill msiexec.exe mid-transaction without understanding rollback state.
Low disk space during uninstall
Uninstallers may extract temporary payloads. Free a few gigabytes on the system drive first. Move large personal folders off the desktop only after you confirm they are not part of the program’s working directory.
Built-in Windows pages worth opening
- Settings → Apps → Installed apps for the primary uninstall entry.
- Settings → Apps → Startup to catch helpers that relaunch the product.
- Task Manager → Startup apps (older view) if you still see legacy entries.
Stop and research first
If leftovers mention System32, WinSxS, or broad Microsoft\Windows keys without a clear app name, close the scan and search each path. The goal is a working PC, not the shortest session.