Microsoft Telling Users To Uninstall Bad Patch

← Back to Stories (view on slashdot.org)

Microsoft Telling Users To Uninstall Bad Patch

Posted by Soulskill on Friday April 12, 2013 @03:40AM 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."

88 of 154 comments (clear)

Min score:

Reason:

Sort:

Here's how to uninstall it.. by americamatrix · 2013-04-12 03:44 · 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 · 2013-04-12 03:59 · 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 · 2013-04-12 04:00 · 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 · 2013-04-12 04:18 · Score: 5, Funny
  
  You missed the whoosh step.
4. Re:Here's how to uninstall it.. by Toreo+asesino · 2013-04-12 04:24 · 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 · 2013-04-12 04:27 · Score: 1
  
  That's definitely not the easiest, that's what you do when you're too fucking stupid to fix the problem by uninstalling the patch.
6. Re:Here's how to uninstall it.. by Anonymous Coward · 2013-04-12 04:35 · Score: 5, Funny
  
  Have you tried turning it off and then on again?
7. Re:Here's how to uninstall it.. by Anonymous Coward · 2013-04-12 04:40 · 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.
8. Re:Here's how to uninstall it.. by malakai · 2013-04-12 04:42 · Score: 2
  
  You're only human...
  http://www.telegraph.co.uk/science/science-news/9989623/Feeling-of-being-watched-hardwired-in-brain.html
  
  --
  -Malakai
  A Dragon Lives in my Garage
9. Re:Here's how to uninstall it.. by GigaBurglar · 2013-04-12 04:44 · Score: 2
  
  It's actually easier to take a leaf out of the book of the majority and forgo updating at all; indefinitely.
10. Re:Here's how to uninstall it.. by GigaBurglar · 2013-04-12 04:45 · Score: 1
  
  cleer ur cashey
11. Re:Here's how to uninstall it.. by Molochi · 2013-04-12 04:52 · Score: 2
  
  Remember, you need to restart the machine three times.
  
  --
  "The Adobe Updater must update itself before it can check for updates. Would you like to update the Adobe Updater now?"
12. Re:Here's how to uninstall it.. by synapse7 · 2013-04-12 04:56 · Score: 1
  
  Then sifting through the list(is it even sortable) of installed updates for the proper kb to be removed.
13. Re:Here's how to uninstall it.. by hairyfeet · 2013-04-12 05:07 · Score: 2
  
  What is useful? Another posted his CLI doesn't work, and for another neither he nor MSFT said WHAT HARDWARE CAUSES THE FAULT which frankly without THAT knowledge is worth fuck and all because I've applied the patch to a couple dozen bog standard desktops and laptops and? I got nothing. Its gotta either be a funky driver or a piece of funky hardware that is causing this because if its anything bog standard I usually run into it but so far AMD, Intel and Nvidia graphics, Realtek and Sigmatel sound, AMD and Intel chipsets (don't have any Nvidia chipsets on hand ATM) and I haven't seen squat, just been another patch Tues round here.
  Oh I did have to reboot my old nettop a couple of times but considering the fact the hard drive already has some bad sectors and the entire system is older than dirt and I'm just waiting on the hardware to finally die because i REALLY don't want to deal with one of my own machines on top of all the other machines I got to deal with? I honestly can't say it was the patch, might have just tried to write to a failing sector. Its an old XP box and XP never was great at dealing with failing sectors...meh its working fine now, left it on for 3 days and its still going when I came in so who cares.
  So if anybody knows what actual hardware or software actually causes the thing it would be nice to know, then I'd at least know if any of these systems are at risk, because right now they seem to be running fine and the 2 that got picked up I haven't heard squat from the owners so I'm guessing they are running fine as well.
  
  --
  ACs don't waste your time replying, your posts are never seen by me.
14. Re:Here's how to uninstall it.. by Thornburg · 2013-04-12 05:07 · Score: 1
  
  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.
  If that's the case, then why does the linked bulletin list every version of Windows under the sun (including RT and Server 2012!) as affected?
15. Re:Here's how to uninstall it.. by toph2223 · 2013-04-12 05:23 · Score: 1
  
  Nice work man.. Really appreciate that :D
16. Re:Here's how to uninstall it.. by HybridST · 2013-04-12 05:24 · Score: 1
  
  I use an eight-pound sledge myself. YMMV.
  
  --
  Ever notice that Cobra Commander sounds an awful lot like Star scream?
17. Re:Here's how to uninstall it.. by TheRealMindChild · 2013-04-12 05:25 · Score: 2
  
  Well, they may not be able to single out exact hardware, just some examples which fail. This patch was to win32k.sys which, among other things, provides the hardware abstraction layer to the NT/Win32 API. It could have made assumptions that turned out not true on corner-case hardware, could have been a problem with actual buggy hardware that didn't follow published specs (not uncommon), or any number of crazy things.
  
  --
  
  "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
18. Re:Here's how to uninstall it.. by AnotherAnonymousUser · 2013-04-12 05:26 · Score: 1
  
  Most helpful comment on Slashdot ever!
19. Re:Here's how to uninstall it.. by Tharkkun · 2013-04-12 05:44 · Score: 1
  
  What is useful? Another posted his CLI doesn't work, and for another neither he nor MSFT said WHAT HARDWARE CAUSES THE FAULT which frankly without THAT knowledge is worth fuck and all because I've applied the patch to a couple dozen bog standard desktops and laptops and? I got nothing. Its gotta either be a funky driver or a piece of funky hardware that is causing this because if its anything bog standard I usually run into it but so far AMD, Intel and Nvidia graphics, Realtek and Sigmatel sound, AMD and Intel chipsets (don't have any Nvidia chipsets on hand ATM) and I haven't seen squat, just been another patch Tues round here.
  Oh I did have to reboot my old nettop a couple of times but considering the fact the hard drive already has some bad sectors and the entire system is older than dirt and I'm just waiting on the hardware to finally die because i REALLY don't want to deal with one of my own machines on top of all the other machines I got to deal with? I honestly can't say it was the patch, might have just tried to write to a failing sector. Its an old XP box and XP never was great at dealing with failing sectors...meh its working fine now, left it on for 3 days and its still going when I came in so who cares.
  So if anybody knows what actual hardware or software actually causes the thing it would be nice to know, then I'd at least know if any of these systems are at risk, because right now they seem to be running fine and the 2 that got picked up I haven't heard squat from the owners so I'm guessing they are running fine as well.
  The article says it's conflicting with certain endpoint security software. That would be antivirus or encryption and I know from using McAfee EPE modifying a kernel driver can cause your machine to blue screen. So it makes perfect sense. Then again if you have an Endpoint Encryption suite running and you aren't testing your Windows updates prior to pushing them you should be asking yourself if you're qualified to do your job.
20. Re:Here's how to uninstall it.. by Sponge+Bath · 2013-04-12 05:45 · Score: 1
  
  Why would you want to uninstall this Blue Screen of Defense security patch? Nothing is more secure than a non-functioning system.
21. Re:Here's how to uninstall it.. by Anonymous Coward · 2013-04-12 06:06 · Score: 1
  
  And killing people is a capital offense, yet the government has people whose job it is to kill. I bet MS has professional trolls who are exempt from your rule.
22. Re:Here's how to uninstall it.. by rot26 · 2013-04-12 06:06 · Score: 1
  
  How could anyone be fired for doing something that 0% of them do?
  
  --
  
  To ensure perfect aim, shoot first and call whatever you hit the target
23. Re:Here's how to uninstall it.. by hawkinspeter · 2013-04-12 06:28 · Score: 1
  
  That's why they outsource it to a different company. They're not employed directly by Microsoft, so they don't have to disclose anything.
  
  --
  You're a temporary arrangement of matter sliding towards oblivion in a cold, uncaring universe
24. Re:Here's how to uninstall it.. by DigiShaman · 2013-04-12 06:34 · Score: 2
  
  According to MS KB2829011, the security updates breaks Kaspersky anti-virus in that the license is not valid. Kaspersky also has an endpoint product as well. I have a feeling that MS is purposefully hiding the fact that using Kaspersky is what's itching the bug in ntfs.sys.
  
  --
  Life is not for the lazy.
25. Re:Here's how to uninstall it.. by Trax3001BBS · 2013-04-12 07:33 · Score: 1
  
  It's actually easier to take a leaf out of the book of the majority and forgo updating at all;
  That's what I've done in the past, disabling auto updating, I'd go and get the ones
  that were really needed. Never using IE skip those and firewall the one installed.
  It's also what I advised others to do, Usenet.
  Before an update could take down your system, it's been so long since an update
  caused any problems; that just recently I've started downloading them, figuring
  they'd finally got their act together.
  As fate may have it I passed on the one mentioned here.
  
  Indefinitely.
  Yes indeed.
26. Re:Here's how to uninstall it.. by GaratNW · 2013-04-12 07:38 · Score: 1
  
  When they said uninstall a bad patch, I just thought that was a euphemism for Windows 8.
27. Re:Here's how to uninstall it.. by DontBlameCanada · 2013-04-12 07:56 · Score: 1
  
  O Hai there paid M$ shill.
28. Re:Here's how to uninstall it.. by dcollins117 · 2013-04-12 08:17 · Score: 1
  
  They are fired preemptively, before they are even hired.
29. Re:Here's how to uninstall it.. by sapgau · 2013-04-12 08:51 · Score: 1
  
  It's all good except for Windows XP users, T_T
30. Re:Here's how to uninstall it.. by Ol+Olsoc · 2013-04-12 09:23 · Score: 1
  
  There is *precisely* 0% chance there's any Microsoft marketing people in discussions here, commenting on anything related to Microsoft, without disclosing that. People are regularly fired for it.
  How can people be regularly fired for something there is a 0 percent chance of them doing?
  
  --
  The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
31. Re:Here's how to uninstall it.. by hairyfeet · 2013-04-12 10:52 · Score: 1
  
  Well that makes sense, I don't have any customers using that software, they are all using Comodo AV which hasn't had a problem with this. I uninstalled anyway, just in case, but none of the systems showed any kind of issues so I figured it was a corner case thing.
  
  --
  ACs don't waste your time replying, your posts are never seen by me.
32. Re:Here's how to uninstall it.. by Black+LED · 2013-04-12 11:57 · Score: 1
  
  That's what I do. I have auto update disabled and only manually update to the latest patches after they've been out for a while.
33. Re:Here's how to uninstall it.. by DigiShaman · 2013-04-12 12:17 · Score: 1
  
  Same here. I just performed server maintenance this week on about 12 units. They're a mix of Server 2008 and 2008 R2. We use Trend Micro WFB and VIPRE Business. No problems yet *knock on wood*.
  
  --
  Life is not for the lazy.
34. Re:Here's how to uninstall it.. by NemoinSpace · 2013-04-12 12:29 · Score: 1
  
  People are regularly fired for it.
  You mean Microsoft regularly fires people for NOT doing it?
35. Re:Here's how to uninstall it.. by hairyfeet · 2013-04-12 18:04 · Score: 1
  
  This is why I never understood how anybody could bitch about MSFT patches. I mean do you have ANY idea how many times I updated my laptop or desktop when I was running Linux and had an update break something? More than I could possibly count, wireless and sound the worse though, I don't think I ever had sound AND wireless come through completely unscathed once, one or the other would ALWAYS get broken. And this was bog standard hardware too, nothing exotic.
  Considering the amount of hardware that Windows runs on and software that runs on it? Love 'em or hate 'em everybody should give them credit for this because its fricking amazing how little breakage occurs with their updates. And when there IS breakage like in TFA it is nearly always some weird corner case, like in this case a funky kernel hooking driver (which how many times has MSFT asked companies not to use weird kernel hooks for precisely this reason?) which went nuts most likely because it expects the kernel to be X size or behave in X manner which it doesn't now. which if they would have just used the APIs frankly they wouldn't have had to care, but hey what can ya do.
  
  --
  ACs don't waste your time replying, your posts are never seen by me.
36. Re:Here's how to uninstall it.. by GigaBurglar · 2013-04-12 19:52 · Score: 1
  
  It's like walking the plank.. abandon ship!
37. Re:Here's how to uninstall it.. by Douglas+Goodall · 2013-04-13 05:51 · Score: 1
  
  I got through step 2, but when it came to step 3 the computer wouldn't boot. I need to access my data on the computer, what do I do now?
38. Re:Here's how to uninstall it.. by TheRealDevTrash · 2013-04-13 16:43 · Score: 1
  
  What it is, is LUPUS.
  
  --
  I used to be /dev/trash but Slashdot no longer allows slashes for usernames.
39. Re:Here's how to uninstall it.. by RockDoctor · 2013-04-14 09:59 · Score: 1
  
  Just incase your having the problem, here is the easiest way to uninstall the update. Open an elevated Command Prompt and type "apt-get install Linux" without the quotes.
  
  FTFY
  
  --
  Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"
Re:One driver eh? by BitZtream · 2013-04-12 03:46 · Score: 2, Insightful

FAIL ... yes, I know, if you're going to edit troll it helps if you can post a properly written post yourself ... I failed :(

--
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
Reminds me of another patch . . . by smooth+wombat · 2013-04-12 03:48 · 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 · 2013-04-12 03:57 · Score: 5, Funny
  
  Hello. My name is Anonymous Coward. You killed my network connection. Prepare to die.
2. Re:Reminds me of another patch . . . by Anonymous Coward · 2013-04-12 04:11 · Score: 1
  
  It turned out it killed the network connection /except for the Administrator account/ so downloading the fix was very feasible.
3. Re:Reminds me of another patch . . . by Endo13 · 2013-04-12 04:14 · Score: 3, Funny
  
  STOP SAYING THAT!
  
  --
  There is no -1 Disagree mod. Slashdot.org/faq defines mod options. USE IT.
4. Re:Reminds me of another patch . . . by lord_rob+the+only+on · 2013-04-12 05:13 · Score: 1
  
  If you have problems with your network, contact your company's IT team by email.
  (ok stupid joke I know, couldn't resist :)
5. Re:Reminds me of another patch . . . by green1 · 2013-04-12 05:38 · Score: 1
  
  If only my company would figure out that this is a joke! They frequently send us emails to notify us that the network is down and not to call support because they are aware of it... Great idea guys, but if I could get to my email I wouldn't be calling support!
6. Re:Reminds me of another patch . . . by interval1066 · 2013-04-12 06:25 · Score: 2
  
  I doan thin that word means wat you thin it means.
  
  --
  Python: 'And then suddenly you have a language which says "we're all stuck with whatever the whiniest coder wants".'
7. Re:Reminds me of another patch . . . by Endo13 · 2013-04-12 06:57 · Score: 1
  
  Inconceivable!
  
  --
  There is no -1 Disagree mod. Slashdot.org/faq defines mod options. USE IT.
8. Re:Reminds me of another patch . . . by TheLink · 2013-04-12 09:28 · Score: 1
  
  I think many ISPs do the reverse - they don't invest in proper network monitoring and let their customers and call centre do the network monitoring for them ;).
  --
  
  Too many replies beneath your current threshold
Why I never auto-install updates by Anonymous Coward · 2013-04-12 03:53 · 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 O('_')O_Bush · 2013-04-12 03:57 · Score: 3, Insightful
  
  That is a good strategy, but, unfortunately, many of us using business computers (issued laptops, etc) don't have that kind of control over the update policy.
  
  --
  while(1) attack(People.Sandy);
2. Re:Why I never auto-install updates by Endo13 · 2013-04-12 04:10 · 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.
3. Re:Why I never auto-install updates by The+Rizz · 2013-04-12 04:35 · Score: 1
  
  I do the same. Unfortunately, Windows will attempt to install them by default whenever you shut down the computer - you have to choose a special "shut down without installing" option while there are any critical updates waiting for install.
4. Re:Why I never auto-install updates by ultranova · 2013-04-12 04:37 · Score: 1
  
  But then again, is a problem with an issued computer your problem? Surely you have your own computer and only use the business computer for business matters? Who knows what spyware it might have, after all.
  
  --
  Forget magic. Any technology distinguishable from divine power is insufficiently advanced.
5. Re:Why I never auto-install updates by Frontier+Owner · 2013-04-12 04:42 · Score: 1
  
  That is a good strategy, but, unfortunately, many of us using business computers (issued laptops, etc) don't have that kind of control over the update policy.
  or better yet, windows update is disabled. We only get updated when out IT department deems it necessary.
6. Re:Why I never auto-install updates by Brucelet · 2013-04-12 04:47 · Score: 1
  
  Exactly! Wait for the first adopters, or "gamma testers", to demonstrate that something is actually safe to use.
7. Re:Why I never auto-install updates by datavirtue · 2013-04-12 06:24 · Score: 1
  
  Yeah, Windows 8 will straight sneak up and fuck you. On my laptop I've started it up to find that updates where applying-- half a fucking hour until I could use my laptop. What if If I was popping it open top start a [presentation? This has happened several times now without notification of any kind.
  
  --
  I object to power without constructive purpose. --Spock
8. Re:Why I never auto-install updates by Dunbal · 2013-04-12 07:22 · Score: 1
  
  Not many actually. Windows 7 is pretty good. All these vulnerabilities they are patching only work when the attacker has local access to your machine. And everyone will tell you that if someone has local access, that machine is compromised, period, no matter what OS you are running.
  
  --
  Seven puppies were harmed during the making of this post.
9. Re:Why I never auto-install updates by dehole · 2013-04-12 09:10 · Score: 1
  
  Microsoft knows better than you whats good for you, apparently.
10. Re:Why I never auto-install updates by TheLink · 2013-04-12 09:44 · Score: 1
  
  Doesn't even have to be more careful or rigorous. Set the autoupdates to be on Monday then there'd be 6 days for others to notice the problem and for the update to be pulled. Can't remember the last time where Microsoft pulled a BSOD level Windows update more than 6 days after it was released.
  
  Of course it doesn't work if everyone starts doing that ;).
  
  The other problem with the "Download updates and let me choose when to install them" option is many versions of Windows have a nasty habit of changing the shutdown menu to default to "shutdown and install updates" or something like that. It's not good to have Windows apply updates when the machine is shutting down due to a low battery situation...
  --
  
  Too many replies beneath your current threshold
11. Re:Why I never auto-install updates by Endo13 · 2013-04-12 14:24 · Score: 2
  
  Or, ya know, have your IT team install it on a test box for a few days to see if anything breaks. That's how most businesses would do it. Well, the ones that care enough to set policies on downloading windows updates anyway.
  
  --
  There is no -1 Disagree mod. Slashdot.org/faq defines mod options. USE IT.
Re:Points at Microsoft by Chris+Mattern · 2013-04-12 03:55 · Score: 1, Funny

Hideki!
Chi!
So, based on the linked garb, this only... by gatesstillborg · 2013-04-12 04:06 · Score: 1

...affects Vista, 7, /Server? Shoot, perhaps we're already seeing the impact of failing to support XP! :)
Windows versions affected by felipou · 2013-04-12 04:06 · Score: 3, Interesting

All versions of Windows since Windows XP are affected! How much code from Windows XP is still used in Windows 8??
1. Re:Windows versions affected by gewalker · 2013-04-12 04:15 · 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.
2. Re:Windows versions affected by Dins · 2013-04-12 04:20 · 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...
3. Re:Windows versions affected by Anonymous Coward · 2013-04-12 04:29 · Score: 1
  
  It's a kernel mode driver change/error. It would be like God doing a bad update on hydrogen.
4. Re:Windows versions affected by Minwee · 2013-04-12 04:37 · Score: 2
  
  You know how chimpanzees share something like 98% of their DNA with humans? It's like that...
  Has anyone told Prenda Law about this? Those chimpanzees may have to pay a bundle to avoid being sued for all that unauthorized sharing.
5. Re:Windows versions affected by GigaBurglar · 2013-04-12 04:48 · Score: 1
  
  And 50% with a banana - you are what you eat as 'they' say..
6. Re:Windows versions affected by mikazo · 2013-04-12 05:00 · Score: 1
  
  You'd be surprised to find that some old code from 16-bit Windows is still kicking around in Windows 8... things just get ported to the next OS so that they work. Code is only re-written or developed from scratch if it's for new features or the old code was so broken or impossible to port that it had to be re-written.
  
  --
  I was only 28,931 registrations away from having a 6-digit UID
7. Re:Windows versions affected by Ravaldy · 2013-04-12 06:00 · Score: 1
  
  I would think that whatever didn't need changing would use the same code. You wouldn't recode the calculator if it worked.
8. Re:Windows versions affected by Curate · 2013-04-12 06:46 · Score: 1
  
  There's no 16-bit code in the 64-bit versions of Windows. 16-bit code requires the NTVDM (virtual DOS machine) to run, and NTVDM is not present in 64-bit Windows. Now 32-bit Windows still has NTVDM, and a handful of old 16-bit command line programs (command.com, edit.com, etc.) are thrown in as well, but none of these are essential to Windows. These are old DOS commands that have been dropped in Windows.
9. Re:Windows versions affected by mikazo · 2013-04-12 07:00 · Score: 1
  
  I meant as I wrote it, "old code from 16-bit Windows" that is compiled into 64-bit binaries (obviously with some modification to make it work). Some of the code has been around since the 16-bit days and just molded to make it keep working in 32-bit and 64-bit Windows.
  
  --
  I was only 28,931 registrations away from having a 6-digit UID
10. Re:Windows versions affected by marvinglenn · 2013-04-12 07:56 · Score: 1
  
  And Windoze 95 is an ancestory of yours.
  
  --
  The whores get mad when the sluts give it away for free.
11. Re:Windows versions affected by StormReaver · 2013-04-12 09:04 · Score: 1
  
  You know how chimpanzees share something like 98% of their DNA with humans?
  I'm always having to tell the chimpanzees to keep their DNA to themselves, thank you very much.
Re:something is causing windows to bluescreen by Anonymous Coward · 2013-04-12 04:37 · Score: 1

Quick! While you have them on the line, tell them about 9/11, the 2004 Boxing Day Tsunami, the 2010 Haiti Earthquake, 2011 Thoku earthquake / tsunami and Fukushima Daiichi disaster! Oh, and see if you can have them drop a note in the mail to 1999 me that says "12-03-30: 46-23-38-04-02/M23", he'll know what to do with it.
Re:One driver eh? by __aaqvdr516 · 2013-04-12 04:56 · Score: 2

The original knowledge base article which is linked to the fix contains the kernel mode drivers. It makes sense in the context of the linked articles, so the fault with the confusion lies with threatpost.com for not providing all the relevant information.
This link is the knowledge base article in question:
https://support.microsoft.com/kb/2829996
The kernel mode drivers are: ntfs.sys and win32k.sys.
I guess that's what happens when you use a summary of a bugfix to write an article.
hmmm looky there what was lurking in my updates... by Greg01851 · 2013-04-12 04:58 · Score: 1

Good thing I saw this article, THEN looked at my pending updates... I had just set up my new computer with Win7 64bit yesterday... and of course had tons of updates to do... Wonder why it stayed in the list even after I refreshed if there's such an issue with it?
Windows - Destroying hardware and helping sales! by oxidus60659 · 2013-04-12 05:00 · Score: 1

Windows update has fried at least two pieces of my hardware in the last year. First it torched my videocard immediately after restarting for a windows update. Next, the PCI express slot wouldn't register on my motherboard, good thing I had another one!
Re:something is causing windows to bluescreen by flimflammer · 2013-04-12 05:03 · Score: 1

No, fuck that. I don't want the future to change and all humans growing like spider legs or something.
GFD microsoft! by AndyKron · 2013-04-12 05:09 · Score: 1

So they push out updates all the time to the point where I'm ready to throw my computer out the window, and now we get BSOD? God fucking damnit Microsoft!
1. Re:GFD microsoft! by Sponge+Bath · 2013-04-12 05:50 · Score: 1
  
  It certainly seems to happen more often than one a week. The wife of a guy I work with leaves her Window laptop in sleep mode at night and it will wake up on its own at 3AM to update, flooding the bedroom with light from the screen. I suppose that feature is this one http://support.microsoft.com/kb/979878. Fun with Windows.
Re:Windows - Destroying hardware and helping sales by Tharkkun · 2013-04-12 05:53 · Score: 2

Windows update has fried at least two pieces of my hardware in the last year. First it torched my videocard immediately after restarting for a windows update. Next, the PCI express slot wouldn't register on my motherboard, good thing I had another one!
That's very similar to my laptop which tries to kill me during the Winter months. I try very hard to sneak up on it by wearing socks on a soft carpet but it always seems to hear me coming and zaps me the moment I touch it.
I suspected as much by Control-Z · 2013-04-12 06:22 · Score: 1

A lightly-used XP machine blue-screened on me this week for the first time, and wouldn't boot without blue-screening. I put it through memory and hard drive checks which it passed just fine. I suspected it might have been a MS patch. Somehow it finally rebooted after 4 or 5 tries, but I haven't rebooted it since. Now I know what patch did it, I can uninstall it. Sheesh.
Re:Windows - Destroying hardware and helping sales by Quirkz · 2013-04-12 08:58 · Score: 1

Once at the office I touched my laptop and the static shock was strong enough it made the computer reboot. That one was a little scary.

--
The Quirkz Handbook of Self-Improvement for People Who Are Already Pretty Okay
This must be the reason for the delay ... by Skapare · 2013-04-12 09:26 · Score: 1

... of North Korea's nuclear missile launch.

--
now we need to go OSS in diesel cars
Repair released for the patch by JRHelgeson · 2013-04-22 09:04 · Score: 1

There is a bootable disk that MS has released to help users recover from this nightmare.
Link: http://www.microsoft.com/en-us/download/details.aspx?id=38435

Repair Disk for KB2823324 and KB2782476 (KB2840165)
To help customers who are experiencing difficulties restarting their systems after installation of security update 2823324, Microsoft is making available a bootable media ISO image through the Microsoft Download Center (DLC). Clicking Download means you agree to the MICROSOFT SOFTWARE LICENSE TERMS.

--
Good security is based upon reality and common sense. Common sense is a function of having common knowledge.