An Upgrade that Isn’t

Analysis
Nov 5, 20082 mins

As many of you know, when you come to the end of your rope on a given system, you can try “upgrading” the operating system to… itself! I’ve done this on a few occasions and, while not especially convenient, it does sometimes work. (So does the System File Checker tool I mentioned in this space recently, and which you should definitely try first.)

The technique is to a) back up your data files for safety, b) pop in your Server 2008 DVD, c) choose the “upgrade” option, and d) go do something else for an hour and a half while your existing settings are exported, your system files recreated, and your old settings imported. At the end of this process, sometimes, if you’ve been living right, whatever was ailing your system will get repaired.

Which, wonder of wonder and miracle of miracles, actually worked on my system. After performing this Upgrade to Nowhere (apologies to Sarah Palin), which maybe we should call a “sidegrade,” I visited Windows Update with some considerable trepidation, but lo! The updates flowed without a single hitch or glitch. Emboldened, I proceeded to install Search Server Express 2008 – and will tell you about that experience next time, because I’ve already exceeded my space allotment for this week. But before I sign off for now, one warning: the server-to-server “upgrade” had some irritating side effects. It blew away the Hyper-V role and shut down my AERO interface. Nothing that couldn’t be fixed, though, and overall, the tradeoff of getting a working system again (and not having to spend any more time with the Component-Based Servicing log) was worth it.

Recent posts

An Error of Type 1 Has Occurred

Event 4375, or… The Terminator

Installing Search Server 2008 Express