Slashdot Mirror

← Back to Stories (view on slashdot.org)

Microsoft .NET Patch May Make PCs Go "Haywire"

Posted by ryuzaki0 on from the danger-will-robinson-danger dept.

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."

8 of 212 comments (clear)

  1. Nickname for the Patch by Anonymous Coward · · Score: 5, Funny

    the MS07-040 patch May Make PCs Go "Haywire" Considering that "Haywire" is a way to describe chair throwing monkey dances, I propose we nickname this patch "The Ballmer Patch" maybe even tag it theballmerpatch since it could make your computer DEVELOPERSDEVELOPERSDEVELOPERSDEVELOPERS.
  2. CPU usage by Rik+Sweeney · · Score: 4, Funny

    While the recompilations are supposed to run as a background task, in some instances the recompilation will drive the processor to 100% usage.

    Sounds like Microsoft are Secretly Monopolizing the CPU Without Being Root

    They'd better not have nicked my code or they're in trouble. It's GPL 3 I'll have you know...

    --
    Summation 2
  3. Shit on it... by Anonymous Coward · · Score: 4, Funny

    And this is why I sit on patches for at least a couple of weeks. What's your IP address, my perpetually vulnerable friend?
    1. Re:Shit on it... by michrech · · Score: 4, Funny

      And this is why I sit on patches for at least a couple of weeks. What's your IP address, my perpetually vulnerable friend? 127.0.0.1
      --
      bork bork bork!
    2. Re:Shit on it... by utnapistim · · Score: 5, Funny

      And this is why I sit on patches for at least a couple of weeks.

      What's your IP address, my perpetually vulnerable friend?

      127.0.0.1

      Aha! Any second now your system will be shutti

      --
      Tie two birds together: although they have four wings, they cannot fly. (The blind man)
  4. Simple solution to the problem... (Funny) by tgatliff · · Score: 4, Funny

    Come on... We all know the routine here on M$ boxes... Reboot it a couple times until we realize it is shot... Stick in the repair cd so that it can finish the job of killing it... Then wax the whole thing and reinstall... Explain to the user that all their data is gone and when they get that "deer caught in headlights" look, tell them they should have backed up to their data... Hm... Missing anything here??

    Just a typical day in windows land...

  5. Re:Sonofa... by Opportunist · · Score: 5, Funny

    Should I just install Gentoo again!?!

    Didn't read the rest of your note, but yes.

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  6. Re:Sonofa... by J0nne · · Score: 5, Funny

    If your processor is going to be recompiling stuff constantly anyway, you might aswell use Gentoo ;).