| By Susan Bradley |
While everyone was in a tizzy over IE7 hitting the streets, the rest of us mortals were still tracking issues with the patches we got earlier this month.
There are times IT folks overreact to technology changes, such as IE 7 — but I guess that’s what makes us human.
.NET patch has some issues installing
First up, the .NET patch, MS06-056 (922770), is still having some issues getting installed. I’m currently tracking separate three issues.
So far, the only consistent solution to all three is to uninstall .NET 2.0 and reinstall it. If you can’t remember whether or not you installed it, chances are that a line-of-business application did. Knowledge Base article 922770 points to several resolutions. Meanwhile, a blog post on the MSDN site points to a few other ideas.
XML bulletin reissued for kill-bit error
The XML patch known as MS06-061 (924191) was re-released for Windows 2000 platforms on Oct. 19. It turns out that the “kill bit” that had been included as an additional security measure didn’t actually kill anything. Thus, it wasn’t doing what it was supposed to do in the XML parser 2.6.
The patch has been reissued to fix this issue. You may have noticed that on some servers you were offered up several versions of the XML patch. This means that you probably had XML from several different applications that had installed it.
Hotfix stops Microsoft Update’s 100% CPU usage
For several months now, I’ve been tracking two annoying issues. It looks like we finally have a resolution to one of the two (the other is described in my next item below).
Hotfix 916089 appears to solve an issue with Microsoft Update. When you run MU, the CPU usage of a machine may shoot up to 100%. This appears to freeze up the machine for a few moments.
Remote shutdown when a machine won’t reboot
The other issue that I’m still tracking involves patching a machine remotely over a Remote Desktop or Terminal Services session. The problem is that the machine doesn’t successfully reboot. Because it doesn’t restart, but it takes down the remote session, we’re left with a machine that we can’t remote back. We’re left with sending a remote shutdown command via a domain-attached machine to remotely reboot the box.