Interestingly enough, I guess I’ve been lucky and none of the pc’s I worked with have experienced this problem with regard to the monthly updates. I’m sure it’s more people than have posted in the forum at Microsoft that are having this issue.
They just aren’t sure yet if the patches themselves are the real problem, or maybe something they’ve possibly installed, hardware issues…etc. It’s great that it’s being brought to the surface so quickly. Not so great, however for those experiencing the problems. Thanks so very much for the link. I have a netbook, haven’t checked into it yet with Windows XP on it. :o
Thank you SO much for posting this info. I’ve been wracking my brain trying to work it out because my XP Pro 64 bit PC is continually BSOD ing and I’m still on Avast 4.8. My notebook’s fine (XP Pro 32 bit) but after uninstalling printer, other peripherals and heaps of software on the PC, I’m still getting BSODs which did indeed start after MS Updates. Now I may have a clue as to a fix. Sounds spooky though the fix…the one suggested by maxyimus. Do you think this is necessary or will MS put out a fix please? Do you have any other links to this problem please? Thank you for posting this waking. Much appreciated.
Thanks so very much PhilR for the links. Well, my netbook gave me no problems with the updates.
Rootkits, a true menace. They hide in your system and are sometimes extremely hard to eliminate. Infected systems will always create problems for security updates. The security forums are having a time of it right now, I’m sure of that.
Thanks so very much for the link Polonus. Looks like possible driver issues on some of the other boards I’ve finally been able to read on as well where the BSOD’s were concerned with Windows Updates. Very glad your problem was fixed.
Thanks so very much waking and sunrisecc for the links. This is quite interesting, and intriguing. To patch or not to patch, that is the question? ;D I’m doing a bit of research on my own with this one. As long as you’re not experiencing any problems, I wouldn’t worry about it just yet.
They (Microsoft) may or may not let you know where the problem lies. Sometimes, it’s better they don’t let “the cat out of the bag” as it were. Even after they find out what they need to know. Keeps the hounds (hackers) at bay for a while longer.
Regardless of what turns out the be the root cause of the problems that update KB977165 seems to have triggered, the recovery problems being faced by those who have been affected once again highlights the value of having frequent partition imaging as a primary part of any backup system.
I manually downloaded and installed the latest batch of MS updates early on the 11th Feb when they still included KB977165. So far I have experienced no problems at all - hope it stays that way.
No problem here. Applied all patches on Patch Tuesday. I have a Dell XPS system purchased in 2005. The link above indicated that the affected systems may have been infected with malware already. Maybe that’s just Microsoft’s story, but some of the malware doesn’t like being neutered.
I updated last night, and 977165 was included. But so far, no problems.
I think I saw somewhere that there’s some evidence that the BSOD associated with this patch may only affect systems infected with a particular trojan, I forget which one.
referenced in the last PC World article I posted indicates that avast! 4.8 (1351? - not the latest!)
with VPS 100211 does NOT detect the bad atapi.sys file. Does anyone know whether or not
avast! 5.0.418 will catch it?