Offices accumulate software the way cupboards accumulate cables. A clean remote uninstall — right command, right targets, data protected — removes the old app from every PC without touching the files your users still need.
Uninstalling looks simpler than installing, and that is the trap. The wrong uninstall can rip out a shared component another app needs, delete a user's data folder along with the program, or fail silently on half the fleet while reporting cheerfully on the console. Endpoint Central uses the same package and configuration machinery for removal — the discipline below is what makes it clean.
Start from inventory, not from a guess. Endpoint Central's software inventory tells you exactly which PCs report the application and which version. Build your target group from that list. Deploying an uninstall at machines that never had the app produces pointless failures — including the classic MSI error 1605, which simply means this product is not installed here.
msiexec /x {PRODUCT-CODE} /qn /norestart — find the code in the registry uninstall key or from the original package/norestart on the command and let your reboot policy decide when restarts happen — an uninstall that reboots a user mid-presentation teaches the office to fear ITPrograms and data are neighbours, not twins. Before removing an old version ahead of a new one, decide explicitly:
App in use: the uninstall cannot remove files a running program holds open. Schedule the removal after hours, or pair it with a user notification asking people to close the app — then retry the skipped machines. Broken old install: a half-corrupted previous version may refuse both repair and removal; on that one PC, use the vendor's cleanup tool or remove it manually over a remote session. Two manual fixes in a fleet of forty is a good ratio, not a defeat.
A console that says success is a claim; the inventory is the evidence. After the uninstall configuration completes, re-run the inventory view: the application should be gone from the target group, and the freed licence count should match. Report both numbers. Software removal is also a security task — every forgotten old version you clear is one less unpatched thing on your network, and the inventory proves it stayed cleared.
See an uninstall configuration and its verification in the full video.
▶️ Watch Full VideoYes — that is what pre-deployment activities are for. Many admins add the old version's removal as a pre-step to the new package, or deploy two configurations back to back: uninstall everywhere first, verify, then install. The two-step version is easier to troubleshoot.
Not always. Leftover empty folders and the odd dead shortcut are cosmetic; most vendors leave some traces by design. If the application no longer appears in inventory and cannot run, the uninstall did its job. Clean the cosmetic leftovers with a small script only if they confuse users.
On a PC that has the software, look under the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall — each subkey named with braces is a product code, and its DisplayName tells you which app it belongs to. The same code is what msiexec /x expects.