When the standard uninstall fails: writing silent removal commands

A record ticket week, and the PowerShell and WMIC commands that removed stubborn software the packaged uninstaller would not.

Some software does not want to leave. This week I hit a stretch of machines where the normal uninstall would not run, and I wrote my way past it.

For those devices I used silent removal commands, a PowerShell approach where it could reach the right service, and the older WMIC command as a fallback for the machines that resisted PowerShell. Getting these right is not about brute force. It is about understanding how the installer registers itself, so you can call the uninstaller directly and quietly instead of waiting for a GUI that never finishes.

That same week I fixed a recurring updater pop-up that had appeared for three users after a routine patch, and I processed several user deactivations plus access removal for another departure. It was, by the numbers, my busiest week yet: fifty-nine tickets, the most of any week so far.

The lesson is that fluency with two or three removal methods is a small skill with outsized value. Any IT person can click uninstall. The value is when the click does not work and you still get the job done without a rebuild or a trip to the user's desk. Knowing PowerShell and the old command-line tools both, and knowing when each will reach the machine, turned a wall of failures into a batch process.

If you support endpoints, rehearse the ways software can be removed when the installer will not cooperate. Script the ones that work. The day the packaged uninstall fails across a fleet, you will already have the tool in hand.

Busy weeks are the best teachers. This one taught me that the boring plumbing is where the real capability lives.

← All writing · Portfolio