Re: KB919029
- From: ingber <ingber@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 6 Jan 2007 18:49:00 -0800
This is the latest post on this problem I could find. After all the reports
so far, please stop telling people how they should give high colonics to
their computers, and instead notify Microsoftr to fix this damn problem by
correctly modifying the "update".
Thanks.
Lester
"Gerry Cornell" wrote:
Bob.
Select, Start, Help and Support, Keep your Windows up- to-date with
Windows Update, Review your Update History and click on the Failed
Icon in the Status Column. What does it say?
A thought. Download and Save. Reboot to Safe Mode and use the
Administrator not a User with Administrator's rights to install.
--
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
"BobH" <BobH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DDA55276-63F9-46C2-86FD-BBEE1CED3E2F@xxxxxxxxxxxxxxxx
I am still having trouble with KB919029 installing.
Windows 2003 Server R2;IE7 (I think - there isn't any obvious about
box on
mine) with restricted security; Office 2003 with SP2.
Logged in with administrator privileges; tried the office update
route;then
looked at http://support.microsoft.com/?id=884298.
I prefer to keep installation CDs locked up (costs too much when
someone
loses them or wrecks them) and instead copy them to an extra hard
drive with
the installation key making up part of the path name, then back this
up with
the rest of the tapes in secure storage in case the master license
code is
lost, etc.
I have tried to update the MSOCACHE using LISTOOL.EXE but this tool
couldn't
find DWDCW20.DLL or DWTRIG20.EXE despite drilling down to their
locations
several times. So I disabled MSO CACHE. (The path name is over 150
characters
long, but well with the file system max length of 260 characters.)
Currently, NONE of my Automatic Updates are listed in "Add/Remove
Programs".
My comment is: THIS IS SILLY!!! Microsoft should rewrite the install
and
check every single step. It is really dumb for Microsoft to tell
users to
check this , check that, try this, try that, etc. when the program
should be
doing it in the first place. The PROGRAM should be checking things
as it goes
and should give a proper error message whether it is a security
error,
registry error, filename error or whatever. Even if the error
message is
cryptic, at least we know where things are at, can report on it,
make
educated guesses; or at least focus in on some part of the process.
Like others, I have spent too much time on this and hope that MS
will
resolve the problem soon.
--
Bob
- Follow-Ups:
- Re: KB919029
- From: Gerry Cornell
- Re: KB919029
- Prev by Date: Re: DLL error
- Next by Date: Re: Same Here
- Previous by thread: Re: DLL error
- Next by thread: Re: KB919029
- Index(es):
Relevant Pages
|
