So, you’re sitting at your PC (or a customer/user’s pc) minding your own beeswax, just installing an application, or perhaps uninstalling an application when… BAM! Something awful hits the fan! Now the bloody thing is all locked up and not responding to any key strokes or mouse clicks. It won’t even let you open up Task Manager to see what in the hell it might be up to, even though you’re pretty sure that it’s up to absolutely nothing…
Now, invariably, the user was standing, looking over your shoulder, absolutely clueless about the fact that you’re boned and about the fact that you too are absolutely clueless… (No, I’ve never been in that position!)
If you’ve been working with PCs for any appreciable amount of time, any good troubleshooter knows that sometimes, for one reason or another, an install or uninstall will get “borked” and that usually happens at just the wrong moment, of course. Thank you Murphy, for that little gem of a “law”… What happens during application installation or uninstallation?
Lots of stuff, really: files get copied, registry settings are potentially altered or created, active directory information may be read or altered, schema extensions may be initiated, operating system variables may be set, and Programs and Features registration is typically instantiated. Of course, it varies widely based on application demands and requirements… When, for various reasons, one of the necessary steps for an app install or uninstall doesn’t complete or fails outright, it can leave the app in a state of limbo, inhibiting the required re-installation of the app or, in extreme circumstances, it can inhibit the usefulness of the entire system. At the very least, it leaves administrators with a loss of confidence in the system and a dread that the problem is indicative of future time-consuming troubleshooting.
I’ve personally used many methods in the past including registry/file scraping where I try to find all references to the app and ruthlessly (albeit recklessly) remove all discovered instances, in a subtle homage to Orson Wells. I’ve also tried clearing temp files and have, of course, resorted to the time-tested “restart and see if that helps” method, usually followed immediately by, “Ok, let’s see if a hard boot helps”. What else? I’ve restored from Restore Points, run OS diagnostics; I’ve even run some very questionable, 3rd party applications to “reset” the registry. Basically, I’ve tried everything short of waving chicken bones, drenched in the blood of the vanquished, under a full moon at midnight on a solstice. I’m saving that one for a really critical situation!
Although some of these solutions have worked some of the time, most of them live in the “60% of the time, it works every time” category. Although there are not hard-and-fast, always effective methods, I’ve been made aware of some interesting tools from Microsoft and, so far, have had success with them. I thought others may appreciate knowing about them.
This tool is so simple to execute that I’m having difficulty elaborating, so perhaps for once, I won’t. Suffice it to say that the UI is intuitive.
When the process is complete, you’ll receive a results screen indicating that it was (or was not) able to resolve the problem. It’s that simple.
This tool is a bit more involved and, I presume, a bit more risky — think of “malware detection programs reminding you that removing some discovered items may result in the untimely death of your OS” risky. The tool removes all Windows Installer information for one or more applications on a PC through the clever use of Product Codes. With command line options, you can also elect to remove rollback information, remove the “In-Progress” key, or even change ACL’s to Admin Full Control.
Download MsiZap
As the command line nature of the application can be a bit unwieldy, I’ve included a link to examples of its use as well. Heads-up! You’ll need to be able to determine Product Codes for applications that you’d like to target. Fun!
Syntax Examples:
In summary, we all have our methods; some of those methods are more sound than others or at least more based in actual computer science and we’ll likely continue to employ what we perceive to have worked for us in the past. That’s great. Here are two more for your arsenal. Godspeed, John Glenn!
Oh, you’ve noticed? We’re blushing.
For those of you that didn’t catch it, our website got a little facelift complete overhaul this past week. In addition to a fresh look and the marriage of the once-separate Big Bang and UIU sites, our new slice of cyber real estate includes improved functionality and brand-new features (with more to come!)
In addition to our new desktop site, we’ve added both tablet and mobile versions, so you can browse easily from the device of your choice.
Whether you are using the UIU Classic (better known as the UIU 4.x to you lifers out there), the new UIU 5, or one of the UIU plug-ins for SCCM or MDT, you’ll find it all here.
Speed up your support experience with the improved UIU Support request form. Submit the form for your next technical support issue, and a ticket will be automatically generated and sent to our technical support team. You’ll receive an email notification that your case has been received and also get a reference number to include in future emails for speedy handling. Also, please remember to attach any applicable UIU log and setupapi files for faster resolution of your issue.
Browse the UIU Install and User Guides through each UIU version’s Table of Contents, or go old-school-but-effective with your browser’s built-in search capability.
Whether you are an existing customer or testing with the free UIU Trial, you can sign up to receive notifications of industry-related blog posts and news about UIU Updates (you can also, of course, follow us on Facebook and Twitter).
We’re adding new content and features every week, so check back for all-new UIU videos, case studies and additional resources. Let us know what you think below or email us here.