MICROSOFT IS LOOKING AT the KB835732 issue now

[Scott]

Hi All:

I just received and e-mail from Microsoft and forwarded some of the
isseus we have been having. They are investingating now.

I will post follow-ups here as they become available.



Scott Wickham

 

[Jerry]

Hi All:

I just received and e-mail from Microsoft and forwarded some of the
isseus we have been having. They are investingating now.

I will post follow-ups here as they become available.



Scott Wickham

In our environment, we found some systems had an incorrect audio driver
which conflicted with KB835732 (MS04-011), causing long boot up times,
spontaneous reboots, and high CPU usage. Updating the audio driver fixed
the problem.

These were Intel BR2 motherboards, 2.4 GHz P4, with integrated audio.
The default driver that Windows 2000 installed had the problems. The
driver downloaded from Intel fixes it.

 

[Scott]

Thank Jerry (see below)
Also...

Microsoft at the moment suggests that the benefit of waiting (for a fix)
may not be worth the risk of waiting (worms). This problem isn't
happening on every machine - just certain (to be determined) machines.

The following (posted from another fine member earlier) may help resolve
most problems.

Best of Luck

Scott


After installing Security fix KB835732, the SYSTEM.exe process uses up
99% of CPU time, and make the system non-responsive.

To unistall it, I did the following
(1) Boot into Safe mode.
(2) Run TaskManager - and noticed that the SYSTEM process
was using 99% of the CPU time.
(3) From TaskManager set the Priority of the EXPLORER
process to REALTIME, so that I can get to the control
panel.
(4) Run ADD/REMOVE PROGRAM from control panel.
(5) Go back to TaskManager and set the Priority of
MSHTA.exe to REALTIME, so that the ADD/REMOVE PROGRAM can
get some CPU time.
(6) Select and Remove "Windows 2000 Hotfix - KB835732".
(7) Go back to TaskManager and set the Priority
of "SPUNIST.exe" to REALTIME, for the uninstall program to
run.
(8) Wait a few minutes, and the uninstall program will
eventually ask you to click FINISH to reboot the machine.
It took a long time for the system to shutdown and I just
unplugged the power.
(9) The machine should become normal after reboot.

 

[Sambo]

Well I am glad people will not be able to run viruses ion my soundcard.
Just like when under W95 and ASUS P5A I wanted to install AGP drivers and
had to install USB first and waste an interrupt.
Besides I thought I installed very much the same "FIXES" 3 months ago.
Did my sound driver screw up IE 6.0 installation too? Hmmm.
AAAAAaaaaaaaaaaaaaaaaaaahhhhhhhhh.

I have Crystal SoundFusion in my system, why under MIDI I have Microsoft GS
wavetable instead of the
Sound fusion "external?" MIDI. Somehow I can't believe there is no MIDI
device on that card.
Another attempt to do something in software that hardware does just fime?

O man o man o man o man.

 

[Guest]

I posted this note earlier today to Bigjohn in another news item on the same topic and I copy it here to register my input
I have been trying for 4 days now to succcessfully install KB835732 on my Win2KPro system (I am right up to date with every update available other than this one). When I reboot my system it locks up and I've had everything from a bluescreen to momentary messages (that I do not get time to read) popping into my screen so it seems to me that this update is arguable the most unreliable upgrade that Microsoft have issued for Win2K since I bought my Dell PC 2 years ago. Thankfully I installed Roxio "GO BACK" shortly after I bought the machine and I am able to quickly revert my C drive to a point before I tried to install this update. Roxio has proved my salvation after trying to download this update for the 6th and final time. I have decided that until Microsoft get off their backsides and admit they have a problem with this update I do not intend trying to install it again. Sorry this doesn't help you BigJohn but frustration has now set in and I want you to feel you are not the only one with a problem on this item (as I thought I was)
The point is, how long are MS going to take to remove/replace this update so that it works effictively and does not cause the problems (bluescreens, 99% use of the CPU, etc) that this upgrade inflicts after it is installed
Kind regards to al

 

[Scott]

I have't heard back from MS yet re all the postings I sent them. I do
want to give you the current fix strategies that I've seen here on the
board.

Emergency Security Patch removal process

After installing Security fix KB835732, the SYSTEM.exe process uses up
99% of CPU time, and make the system non-responsive.

1/2
To uninstall it, I did the following
(1) Boot into Safe mode.
(2) Run TaskManager - and noticed that the SYSTEM process
was using 99% of the CPU time.
(3) From TaskManager set the Priority of the EXPLORER
process to REALTIME, so that I can get to the control
panel.
(4) Run ADD/REMOVE PROGRAM from control panel.
(5) Go back to TaskManager and set the Priority of
MSHTA.exe to REALTIME, so that the ADD/REMOVE PROGRAM can
get some CPU time.
(6) Select and Remove "Windows 2000 Hotfix - KB835732".
(7) Go back to TaskManager and set the Priority
of "SPUNIST.exe" to REALTIME, for the uninstall program to
run.
(8) Wait a few minutes, and the uninstall program will
eventually ask you to click FINISH to reboot the machine.
It took a long time for the system to shutdown and I just
unplugged the power.
(9) The machine should become normal after reboot.

2/2
The way Dr.Ray posted didn't do the trick for me, I just couldn't log on
even after trying for about 3 hours. I removed it this way:

1. Boot the system from the W2k installation cd and start the recovery
console
2. go to the directory %WINNT%\$UnInstallKB835732$\spunst
3. type: "Batch spuninst.txt". this will uninstall the SP but not all the
files will be copied (probably in use)
4. Reboot the computer (yes, it will start normaly)
5. Go the the configuration screen and remove the service pack from the
software list to replace the files that were in use

 

[Geir Horn]

Excellent!

I installed KB835732 today just to experience just this
misbehaviour. Presumably the bug causing it has not been
fixed since this original posting 22nd of April.

One problem remains, though: I installed KB835732 to plug
the system against future Sasser attacks - removing the
KB835732 will probably re-install my vulnerability. Any
ideas on how to protect without running a firewall on the
local machine or installing KB835732?

Thanks a million!

--- Geir