Blogs

Leftover scan workflow

Updated for Windows 10/11

Run the vendor uninstaller first, ideally elevated. Reboot if the installer demands it; skipping that step often leaves services locked.

Hunter mode without guesswork

Use Hunter-style targeting when you see a window or tray icon but cannot find the product in the plain list. Drag the sight onto the element and confirm the uninstall entry before proceeding.

MSI error 1722 and rollback

Error 1722 usually means the installer script could not finish, often because files are locked or a custom action failed. Stop other installs, close the app, retry from an elevated command prompt if the vendor documents one.

Ghost “already installed” entries

Some installers register under the 32-bit uninstall hive even on 64-bit Windows. Check both views before assuming the entry is gone.

Registry backup rhythm

Export relevant keys with a timestamp in the filename. Store the .reg file outside the system drive if you can.

Disk space after uninstall

Large games and creative suites often cache under ProgramData or user AppData. Sort folders by size only after quitting related launchers.

Browser extensions cleanup

Extensions can reinstall from sync the moment you sign back into Chrome or Edge. Disable sync temporarily, remove the add-on, then clear the browser’s local extension folder only if you recognize the publisher path.

Telemetry and opt-out debris

Turning off telemetry in settings does not always delete historical logs. Look for vendor-named folders under ProgramData and LocalAppData that contain .log or .db files tied to the product you removed.

Multi-user Windows PCs

Per-user installs drop binaries under each profile. Removing them while logged in as Administrator might miss another family member’s copy. Switch users or load the profile before scanning.

Microsoft Store loops

Store apps can come back because the same Microsoft account owns the license, or because a “required” package is part of a larger suite. Remove the visible tile first, then check optional related packages in the app list before you run a forced path.

Services and drivers

Many suites register a Windows service with a generic name. The uninstaller may stop it, or it may restart under a parent process. Open Services (or the shortcut from Revo’s Windows tools), set the startup type to disabled only after you confirm nothing else depends on that service.

Optional features and caps

Windows optional features (WSL, Virtual Machine Platform, Hyper-V management tools) stack on top of each other. Removing WSL distributions from inside wsl --unregister is separate from turning off the platform feature in Settings.

Remote sessions and elevation

Over RDP, User Account Control and split admin tokens behave like a local console, but some installers refuse to elevate across a network logon. If Uninstall stays gray, try the same action from a local admin session or use runas only when your policy allows it.

Shared and family PCs

One Windows box often holds several profiles. An app may install per user under C:\Users\… while still dropping a machine-wide service or driver. Before you remove folders, confirm which account owns the data and whether anyone still logs in with that profile.