Re: Can't install the BITS 2.0 and WinHTTP 5.1 Update (KB842773), error 0x80070005

There's likely permissions issue involved here. This is a work-around.
Download the update from Download Center & install as per following. This link & item is for Windows 2000.

<http://www.microsoft.com/downloads/details.aspx?FamilyId=3EE866A0-3A09-4FDF-8BDB-C906850AB9F2&amp;displaylang=en>


Download it, and just Save it to disk; do not run it in normal mode.
Reboot to Safe mode. Login with administrator account.
Then run it to install.

While still in safe mode, deleted files in this folder
C:\WINNT\SoftwareDistribution\Download

--
Maurice N
MVP Windows - Shell / User
-----


Christian Fersch wrote:
> I can't use windowsupdate v6, for the above mentioned update won't
> install.
>
> Content of WINNT\KB842773.log:
> ================================================== ==============================
> 0.015: 2005/08/13 22:11:42.765 (local)
> 0.015:
> C:\WINNT\SoftwareDistribution\Download\d977fa35054 137a2c4ca986dc8156202\update\UPDATE.EXE
> (version 5.5.33.0)
> 0.015: Failed To Enable SE_SHUTDOWN_PRIVILEGE
> 0.015: Das Service Pack wurde mit folgender Befehlszeile gestartet:
> /quiet /norestart /er /ParentInfo:12e6f8efec2886478f4fdf623d6acd71
> 0.593: PrepareToTrustInfFile: MySetupCopyOEMInf failed: 0x5
> 0.593: IsInfFileTrusted: PrepareToTrustInfFile Failed: 0x5
> 0.593: Zugriff verweigert
> 0.593: Die Installation des KB842773 wurde nicht abgeschlossen.
> 0.593: Update.exe extended error code = 0x5
> ================================================== ==============================
>
>
> I'm using Win2k.

If you ran using Admin, I don't think I have more suggestions at this time.

--
Maurice N
MVP Windows - Shell / User
-----


Christian Fersch wrote:
> Maurice N ~ MVP wrote:
>> There's likely permissions issue involved here. This is a
>> work-around.
>
> This is definetly a permissions issue.
>
>> Download the update from Download Center & install as per following.
>> This link & item is for Windows 2000.
>>
>> Download it, and just Save it to disk; do not run it in normal mode.
>> Reboot to Safe mode. Login with administrator account.
>> Then run it to install.
>
> Did just that. Installer died with a "Zugriff verweigert" message
> (that means "access denied").
>
> Any other suggestions?

"Christian Fersch" <> wrote in message
news:ddnt6m$cbp$02$...
> Maurice N ~ MVP wrote:
>> There's likely permissions issue involved here. This is a work-around.
>
> This is definetly a permissions issue.
>
>> Download the update from Download Center & install as per following.
>> This link & item is for Windows 2000.
>>
>> Download it, and just Save it to disk; do not run it in normal mode.
>> Reboot to Safe mode. Login with administrator account.
>> Then run it to install.
>
> Did just that. Installer died with a "Zugriff verweigert" message (that
> means "access denied").
>
> Any other suggestions?


I think you are going to have to do some diagnosis.

Since you have the same problem running it manually
try running it manually with the /verbose option specified.
Unfortunately it is not clear exactly where the additional
logging is supposed to be found. Here's the latest revision
of my suggestions about capturing better diagnostics for such
symptoms.

<quote>
If you don't get anywhere trying to change permissions (e.g. the way that
others have done successfully) I would try adding /verbose to the
command line options of a manual install (as described above)
and see if that gives you any clearer picture of what's wrong.
Note: so far people who have tried this suggestion with me haven't had
much luck finding where the /verbose log is going. In that case I have
suggested that they do a file find (e.g. Win-F) for all files which were
changed on the day of the update and sort that result by Date Modified
(thus sorting the list by timestamp and allowing you to see files listed within
the minutes that the install was active.) Alternatively or in addition, I would
run FileMon filtering on SoftwareDistribution;Update;CatRoot to supplement
(and identify) any logs which the install produces. There is also a verbose
option for the download and install (if done by WU) documented in KB902093.

In order to get the best match for install log records with FileMon trace
entries it is very useful to use FileMon's Clock Time and Milleseconds
options. E.g. provided the FileMon filter includes writes to the install log
you will then see a timestamp down to the millesecond tied to the length
of an install log record. Then it is simply a matter of checking the length
of the records in that context to figure out what the more accurate timestamp
for that install record would be. This is particularly useful if you are doing
concurrent RegMon tracing with the same options set. E.g. then you can
match a context of the FileMon trace with a context of the RegMon trace.

Hopefully a /verbose log would have sufficient context but the FileMon
and RegMon idea is more general and may still be necessary if it turns
out that there is insufficient detail even in the /verbose log.


HTH

Robert Aldwinckle
---
</quote>

"Christian Fersch" <> wrote in message
news:...
> Robert Aldwinckle wrote:
>> "Christian Fersch" <> wrote
>>> Did just that. Installer died with a "Zugriff verweigert" message (that
>>> means "access denied").
>>>
>>> Any other suggestions?
>>
>> I think you are going to have to do some diagnosis.
>>
>> the minutes that the install was active.) Alternatively or in addition, I would
>> run FileMon filtering on SoftwareDistribution;Update;CatRoot to supplement
>> (and identify) any logs which the install produces. There is also a verbose
>> option for the download and install (if done by WU) documented in KB902093.
>
> Thx a Lot. FileMon did the trick. There was a file
> "C:\WINNT\inf\oem27.PNF" that had write access denied to my Admin user.
> Gave me full access, ran windowsupdate again and worked like a charm.
>
> Thx


Thanks for the feedback. Nice to know this idea works for some.
I've felt a bit like a "snake oil salesman" when it hasn't worked for others.


<w>


Robert
---