Slashdot Mirror

← Back to Stories (view on slashdot.org)

Microsoft Telling Users To Uninstall Bad Patch

Posted by Soulskill on from the but-thanks-for-testing-it dept.

msm1267 writes "Microsoft announced last night that it has stopped pushing a security update originally released on Patch Tuesday because the fix is causing some PCs to blue-screen. Microsoft recommends users uninstall the patch, which is also causing compatibility issues with some endpoint security software. MS13-036 was part of this week's Patch Tuesday update. It addressed three vulnerabilities in the Windows Kernel-Mode Driver, which if exploited could allow an attacker to elevate their privileges on a compromised machine. Users began reporting issues earlier this week with some systems failing to recover from restarts, or applications failing to load, after the patch was installed."

13 of 154 comments (clear)

  1. Here's how to uninstall it.. by americamatrix · · Score: 5, Informative

    Just incase your having the problem, here is the easiest way to uninstall the update.

    Open an elevated Command Prompt and type "wusa.exe /uninstall /kb:2823324 /quiet /norestart" without the quotes.

    You should be good to go now :)


    -americamatrix

    1. Re:Here's how to uninstall it.. by Anonymous Coward · · Score: 5, Funny

      I thought it was:

      • 0) unlock secure boot
      • 1) reboot to FreeDOS
      • 2) format C: /q
      • 3) install another OS

      Windows 8 itself is the "patch" no?

    2. Re:Here's how to uninstall it.. by Anonymous Coward · · Score: 5, Funny

      How is that easier than navigating through four dozen menus and dialogs of advanced options? I really don't understand you command-line people.

    3. Re:Here's how to uninstall it.. by Anonymous Coward · · Score: 5, Funny

      You missed the whoosh step.

    4. Re:Here's how to uninstall it.. by Toreo+asesino · · Score: 5, Insightful

      Kudos for providing some actual useful info for an MS product on Slashdot. Unfortunately it's a rarity around these parts.

      --
      throw new NoSignatureException();
    5. Re:Here's how to uninstall it.. by Anonymous Coward · · Score: 5, Funny

      Have you tried turning it off and then on again?

    6. Re:Here's how to uninstall it.. by Anonymous Coward · · Score: 5, Informative

      The command in americamatrix’s post is intended for use after you’ve install the windows update(s), but before you’ve rebooted your system to fully apply them. It may also work after rebooting if the update doesn’t prevent a successful reboot, but does cause other problems (e.g. causing Kapersky to lose its license). It’s basically the same thing as using the Programs Control Panel “View Install Updates” feature to uninstall it.

      Also, I’d recommend leaving off the “/quiet” flag so that you get some comforting feedback that it has actually worked. So: “wusa /uninstall /kb:2823324 /norestart” (no need for “.exe” either, of course).

      If you’ve already rebooted your system and now cannot get into it because of the update (symptoms may include a false indication of file system corruption on a hard drive [Event ID 55], STOP: c000021a {Fatal System Error} status 0xC000003a, or “Windows failed to start Status: 0xc000000e”), there are other ways to remove it, involving either using System Restore or Boot to Command Prompt and issuing a command.

      Full details at: http://support.microsoft.com/kb/2839011

      Note that this update is apparently only applied to systems running Windows 7 pre-SP1 or SP1, Windows Server 2008 R2 pre-SP1 or SP1, or Windows Server 2008 non-R2 SP2 (any edition of any of these). If you’re running Windows XP, Vista, or 8, presumably this won’t be an issue as the update would never even have been offered via Windows Update.

  2. Reminds me of another patch . . . by smooth+wombat · · Score: 4, Interesting

    Microsoft put out years ago which killed ones network connection.

    The solution? Go back to Microsoft's site to get the updated patch.

    Erm, yeah. Great idea. You kill my network connection then want me to go back to your site to fix the issue.

    So much for the vaunted "best and brightest" following standard project processes such as TESTING.

    --
    We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
    1. Re:Reminds me of another patch . . . by Anonymous Coward · · Score: 5, Funny

      Hello. My name is Anonymous Coward. You killed my network connection. Prepare to die.

  3. Why I never auto-install updates by Anonymous Coward · · Score: 5, Interesting

    I set Windows Update to notify and download updates, but never to auto-install them. I also usually hold updates a few days before installing. Use the same policy with my Linux boxes and have never run into problems.

    1. Re:Why I never auto-install updates by Endo13 · · Score: 4, Insightful

      And if your business is worth a shit, their own strategy is even more careful and rigorous than what the GP posted.

      --
      There is no -1 Disagree mod. Slashdot.org/faq defines mod options. USE IT.
  4. Re:Windows versions affected by gewalker · · Score: 5, Insightful

    I don't know that answer, but I would hope that the answer was "quite a lot of it". Old cold is not bad code, it is the code that has generally stood the test of time. Not that it is defect free, but that the defect rates are generally lower than the newly written code. Even such basic steps as recompiling for 64-bit, causes new breakage (old code was defective, but the problem was masked). This appears likely to be one of those old problems that became unmasked with the latest patch.

  5. Re:Windows versions affected by Dins · · Score: 5, Funny

    How much code from Windows XP is still used in Windows 8??

    You know how chimpanzees share something like 98% of their DNA with humans? It's like that...