Conflicting Windows XP Conflicts

Whether you’re using a PC or a Mac, I think you’ll find today’s post most enjoyable.

If you’re not aware, by popular demand, Microsoft has released a second service pack installment (SP2), to their popular operating system Windows XP. The update is supposed to eliminate many of the problems associated with Windows security.

I was reluctant to install the new update for fear it may wreak havoc on our machines. (See eWeek’s article on IT admins not trusting XP2). But not installing it could produce even more disasters, so I decided to test an installation before loading it onto our production systems.

After downloading and installing SP2, I was asked to reboot my machine. (You know where this is going, don’t you)?

Upon reboot I got the following warning message:

“Microsoft Broadband Networking has a known compatibility issue with this version of Windows.”

Wait a minute! Microsoft is having a conflict with one of its own products? Oh boy.

I thought I might get some non-believers so I took a screenshot of the error.

So the install just blocked my internet access. I guess that’s Microsoft’s solution – just completely block all access to the internet. That’s like preventing heart disease by not eating.

Anyhoo…

It turns out I had to install the latest update for Microsoft Broadband Network. According to the directions, I was to update using the MS Broadband Network utility. Well, when I tried to load the utility via Internet Explorer, XP2’s pop-up blocker blocked access to my PC’s hard drive. Oh great, now I couldn’t even access my computer.

I eventually was able to gain access to my hard drive by right-clicking on the pop-up blocker toolbar and “allowing” access. I installed the update successfully and re-gained access to the internet. Whew!

I just thought it was incredibly ironic that the problems that were associated with installing a Microsoft update conflicted only with another Microsoft product. Go figure.

In conclusion, always test before you launch.

‘til next time.