Tracking what patch caused the hiccups
If only I could trust that Windows Update icon to save me time. Instead, I’m far too much at ease with restore points, troubleshooting, all the joys of maintaining a system that seems bound to break.
Remember, I do take care of computers for a living. I’m not surprised by hiccups anymore. I had hoped for more with W7 (yes, I am hopelessly naive). For the last few weeks, every time I get the notification that updates are available, I sigh and square my shoulders against the wind from Redmond.
Here’s the deal; right now there’s a browser patch (KB980182) which promises to protect me against nasty-doers from beyond my castle walls. Instead, IE8 and Outlook 2007 simply cease working. No loud waving, or coloured screens. The programs start, twirl and fall flat on their faces. Now, deciding which patch wasn’t obvious.
Today, I had 10 new fixes that all wanted to climb on board. I split the load in two, created a couple of restore points for my own sanity and began. After five, epic fail. After ten, same old. I consulted the list of new updates, chose the one that promised to fix my browser and did the uninstall shuffle. Harmony has been restored, and I’ve “marked” the patch as hidden, as a future reference.
One incident, one hour. I work cheaply. Given the number of programs that require regular calls home, it’s only a matter of time before my next round of “Who did what where?”
More and more, Linux might be that proverbial safe harbour.
