problems with last 5 security updates lockup 10-16-03

  • Thread starter Thread starter Lincoln
  • Start date Start date
L

Lincoln

I am a Technology Support Analyst for Arizona State
University and I have been applying the patches released
For October (5 of them) but I have some machines W2k and
XP(2.4GHz) that take over an hour to install the patches
and they still freeze at the end is anyone else having
trouble with them. I have some machines that they
installed fine and others it does not. Also how do you
get a hold of Microsoft to tell them their patches are
screwed up. I am only having about a 20% success rate of
the installations of these patches.

thank for your help

-Lincoln
 
I'm having a similar problem, but seems to be with only 3
of the patches. I'm doing a scripted install, on W2k SP$
clients, using Altiris. I have tried different switches,
etc., but can't get them to work. Here's what I've tried,
and the results:

828750 /q /r:n (ok)
823182 /u /z (ok)
824141 /u /z (ok)
825119 /u /z (ok)
828026 /u /z (update.exe hangs after install)
828035 /u /z (update.exe hangs after install)
826232 /u /z (update.exe hangs after install)

I also tried using "/passive /norestart" switches, but
have the same problem. I've tried them chained all
together, and individually, same problem. I have also
tried using qchain.exe, but you're not supposed to need it
if you have W2K SP4.
 
I am having the exact same problem. Will look into it
further this weekend if Microsoft hasn't offered a
solution.
 
I am having the same problem with the same 3 patches. It
appears to be related to having applied security to the
system with a security template. If I load a clean Win2K
system at SP 4 with no security, the patches seem to
complete correctly. With security applied, Update.exe
hangs whenever I try to run any of those 3 patches. I
have seen a similiar problem with SP 4 when a certain
registry entry was locked down to prevent the
Administrator user from modifying the registry key. I am
going to load a clean system and apply security
incrementally to try to see what in particular is creating
the problem.
 
Back
Top