Batch file won't finish installing security updates

[Guest]

When running the following batch file I've run into a very
strange problem.

@echo off
setlocal
set PATHTOFIXES=Path
%PATHTOFIXES%\Windows2000-KB826232-x86-ENU.exe /z /q
%PATHTOFIXES%\Windows2000-KB825119-x86-ENU.exe /z /q
%PATHTOFIXES%\Windows2000-KB828035-x86-ENU.exe /z /q
%PATHTOFIXES%\Windows2000-KB824141-x86-ENU.exe /z /q
%PATHTOFIXES%\Windows2000-KB823182-x86-ENU.exe /z /q
%PATHTOFIXES%\qchain.exe qchainlog.txt

On most of the machine in my office it works fine, but on
about 20 Gateway 9500's and another 25 Dell GX150's I have
the following problem.
After the first patch is run the batch file stalls. What
seems to be happening is that update.exe keeps running
using 100% of the processor and never quits which keeps
the next file from running. If you go into task manager
and kill update.exe the next file runs but then stalls
just like the first. On all the rest of my machines
update.exe terminates and the batch file runs and finishes
the install of all the patches. I've searched the web high
and low but can't find any reference to this happening.
Does anyone have any idea what's going on with update.exe
and why it won't stop running???

MikeO

 

[David Adner]

Some users reported that if you grant the local Administrators group the
Debug programs (don't recall the exact name of the Right) User Right,
this stopped the never-ending-update problem.

 

[Mike O'Neill]

David,
You hit the nail on the head. When I looked at the
following
Local security policy > User Rights Assignment > Debug
programs
on users machines that didn't work, sure enough the "Debug
programs" policy was blank. As soon as I gave the local
Admin rights, bounced the box, the batch file ran fine.
Nice job!!!
Thanks...

MikeO

 

[David Adner]

According to ntbugtraq, the newer update.exe's check for the User Right
and if the user has it, will allow the patch to install without a
reboot. If it's not there, the patch will prompt for a reboot.
Apparently, there's a bug where under as yet to be determined
cirumstances, the update.exe just goes into high CPU utilization instead
of behaving properly.