There is a BUG in patch B835732

[Raymo]

On hearing about the SASSER worm I used "Automatic Live
Update" to download the latest security patches for
Windows 2000 on my laptop PC. It installed patches 837001,
835732 and 828741. After the installation it re-started
the computer.

It took 1 hour to re-start, and then the task manager
indicated that it was running at 100% CPU, and the main
problem was the process SYSTEM which seemed to be grabbing
all available CPU. I managed, by increasing the priority
of the process EXPLORER.EXE to high, to identify the three
patches that the update had installed. I then un-installed
them one at a time (this process took nearly 2 days!).

The problem was solved by the removal of update B835732.
It wasn't the worm that got me, it was the Microsoft
patch. There is a bug in it relating to W2K service pack 4
running on a laptop computer - from other postings in
newsgroups I can see I am not the only one to have had
this problem.

 

[Scott Kolya]

-----Original Message-----
On hearing about the SASSER worm I used "Automatic Live
Update" to download the latest security patches for
Windows 2000 on my laptop PC. It installed patches 837001,
835732 and 828741. After the installation it re-started
the computer.

It took 1 hour to re-start, and then the task manager
indicated that it was running at 100% CPU, and the main
problem was the process SYSTEM which seemed to be grabbing
all available CPU. I managed, by increasing the priority
of the process EXPLORER.EXE to high, to identify the three
patches that the update had installed. I then un-installed
them one at a time (this process took nearly 2 days!).

The problem was solved by the removal of update B835732.
It wasn't the worm that got me, it was the Microsoft
patch. There is a bug in it relating to W2K service pack 4
running on a laptop computer - from other postings in
newsgroups I can see I am not the only one to have had
this problem.
.

 

[Scott Kolya]

Just wasted a few hours fighting the same problem
myself...

Since Microsoft restrict the number of their
staff who are allowed to poke about in the 'kernal'
you'd hope those select few were talented
enough to avoid this sort of thing... an infinite loop
of trying to load a driver is a fairly basic mistake.....

 

[Bjorn Simonsen]

Just wasted a few hours fighting the same problem
myself... [...]
... an infinite loop of trying to load a driver is a
fairly basic mistake.....

Wonder if this is why it takes so long to load/log-on to
my Win2k Sp4 system (standalone workstation) after
applying KB835732. Takes a minute or two longer now than
before, and I can hear my HD being read/searched while it
happens, so maybe it is as you suggest looking for a driver
not there - although it does not end in a infinite loop here
(maybe so since I am not connected to a network, searching local
disk only (?))

All the best,
Bjorn Simonsen

 

[yankele]

Me too! Log on to Windows sits on my screen now for about 15 seconds
whereas it took less than a second before this update. In addition,
the Event Viewer -- Applications now gives me this:

Warning

PlugPlayManager

Event ID 256

Timed out sending notification of device interface change to window of
""

15 instances of it(!) which accounts, no doubt, for the long delay.
MSKB says this warning message is of no consequence and should be
ignored. Yeah, sure....

 

[robin]

installed the patch had 20 error messages in event viewer besides the cpu
was at 100% and log on took up to 15min
Uninstalled the patch- everything turned back to normal and no more error
messages
robin