Slashdot Mirror
Microsoft .NET Patch May Make PCs Go "Haywire"
yuna49 writes "Various people are reporting that the MS07-040 patch for .NET released on Tuesday can cause a variety of seemingly unrelated problems. According to the SANS Internet Storm Center 'the reports we got so far seem not to lead to any specific thing that happens in many cases, just various things going haywire.' Some commentators on The Register's report of this story indicate that the patch failed to install at all, while others report things like the mouse suddenly failing to work or long periods of hard drive thrashing. In some cases a hard reboot seems to fix the problem, but other reports suggest that a reinstallation of the .NET framework itself is required. The problems may be related to the MSCORSVW.EXE process which recompiles all the .NET assemblies when the patch is downloaded. While the recompilations are supposed to run as a background task, in some instances the recompilation will drive the processor to 100% usage."
When this 100% cpu utilization was happening I called up Process Explorer http://www.microsoft.com/technet/sysinternals/util ities/ProcessExplorer.mspx
I installed this on my Windows 2000 box yesterday and I haven't seen any problems so far. *shrug* Maybe it's just a Win XP thing.
On the other hand, a broken partition table due to a random hardware error (or any other bug causing a write there) would probably not be detected until the next reboot anyway.
If you follow the update KB article, you'll find MS has already found issues with the update.
.NET 2.0, reinstall .NET 2.0 and try to update again. Sounds kind of cyclical to me.
See:
http://support.microsoft.com/kb/928365/
Which leads to:
http://support.microsoft.com/kb/923100/
and
http://support.microsoft.com/kb/934711/
and
http://support.microsoft.com/kb/923101/
and
http://support.microsoft.com/kb/934793/
and
http://support.microsoft.com/kb/931846/
923100 says if you get hosed doing the update, uninstall
machinator omnis sine licentia