Microsoft Refuses To Patch Rootkit-Compromised XP Machines
Barence writes "Microsoft has revealed that its latest round of patches won't install on XP machines if they're infected with a rootkit. In February, a security patch left some XP users complaining of endless reboots and Blue Screens of Death. An investigation followed and Microsoft discovered the problems occurred on machines infected with the Alureon rootkit, which interacted badly with patch KB977165 for the Windows kernel. Now Microsoft is blocking PCs with the rootkit from receiving its new patches. 'This security update includes package-detection logic that prevents the installation of the security update if certain abnormal conditions exist on 32-bit systems,' Microsoft cautions in the patch notes."
no! I need the newest microsoft patch so that there are not any new security holes in my computer! I'll deal with that huge gaping sucking chasm of a security hole that's already there, created by the rootkit, at some later date.
What ever happened to backwards compatibility? Why, I remember the day when any virus, worm, or piece of malware, would run no matter what!
#fuckbeta #iamslashdot #dicemustdie
This just proves that it's a great time for people who have been sticking with XP to take the plunge and upgrade to Windows 2000 Professional.
It most certainly does have an Operating System. In fact if it has disc brakes it even has a Disc Operating System...
Alexander Peter Kristopeit bought his basement from his mommy for one dollar.
So this is a vendor software issue? Those rootkit developers should have a better testing process. I'm not going to go to all of the trouble of rooting 100k servers just to have my botnet BSOD on the next update. I demand a refund
Truth: If it's not one thing, it's another
"I'm a people-person. What the hell is wrong with you people?"
*Still* negative function...
Just to be sure that we get this update, I am installing the newest Antivirus 2010 on all of our network machines. This version should pickup the rootkits that Antivirus 2009 left behind. Since I work at the IRS, our systems are absolutely critical to protect this month.
What if it hides in the documents?
The Tao of math: The numbers you can count are not the real numbers.
To do nothing? They need a mandate to not touch a system they don't own?