New
#1
Odd, I've never had a problem with updates causing a crash, except once back when I first installed XP x64. If this is something inherent in x32, I'm glad that I no longer use it...except my XP MCE install.
Machines left unpatched so MS can avoid BSOD déja vu.
-
-
New #2
Why do these users that are having the BSOD have a rootkit installed on there system in the first place?
-
New #3
-
New #4
-
-
-
-
New #8
Gotta love'm though.Sounds exactly like my Mum, checking every single piece of e-mail she gets, including junk, and opening every link she gets in them.
Which reminds me, been a month or so since she last rang.......sshhhhh... listens for a ring.
-
Machines left unpatched so MS can avoid BSOD déja vu.
Posted: 15 Apr 2010
Source -Microsoft is seeking to avoid a repeat of February's blue-screen problems with this month's bumper crop of Patch Tuesday patches. After installing the February updates, some users of Windows XP found their systems wouldn't boot. After investigation, this turned out to be due to an interaction between the Alureon rootkit and the patch for KB977165 which updates the Windows kernel. Microsoft has subsequently released tools that attempt to detect the rootkit and prevent installation of the patch if a machine appears compromised.
This month's patches also contain kernel updates, and so have the same incompatibility with the rootkit. As the bulletin for MS10-021 states, "This security update includes package detection logic that prevents the installation of the security update if certain abnormal conditions exist on 32-bit systems. These abnormal conditions on a system could be the result of an infection with a computer virus that modifies some operating system files, which renders the infected computer incompatible with the kernel update."
Machines left unpatched so Microsoft can avoid BSOD dj vu
Quote
Related Discussions