Error 0x80070003 (again)

Hi,

I am gettign 0x80070003 tried most things in this group with no luck, heres
the log I get can anyone PLEASE help:

KB898461.log]
1.342:
================================================== ==============================
1.342: 2005/07/22 13:16:52.907 (local)
1.342:
C:\WINDOWS\SoftwareDistribution\Download\e8f0bcd92 171c9af9c66928b3a749cec\update\update.exe (version 6.1.22.4)
1.342: Failed To Enable SE_SHUTDOWN_PRIVILEGE
1.362: Hotfix started with following command line: -q -z -er
/ParentInfo:d788356b4142b749a9770f6e9168c96d
1.772: In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed with
error 0x2
1.772: In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed with
error 0x2
1.772: DoInstallation: CleanPFR failed: 0x2
1.793: SetProductTypes: InfProductBuildType=BuildType.Sel
1.793: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.823: DoInstallation: FetchSourceURL for
c:\windows\softwaredistribution\download\e8f0bcd92 171c9af9c66928b3a749cec\update\update_SP2GDR.inf failed
1.823: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB898461$
1.823: LoadFileQueues: UpdSpGetSourceFileLocation for halacpi.dll failed:
0xe0000102
1.843: LoadFileQueues: QueueMigrationStageFiles failed: 0x00000003
1.843: InventoryThread: LoadFileQueues failed with error: 0x3
1.843: Inventory complete: ReturnStatus=3, 20 ticks
1.843: Num Ticks for invent : 20
2.003: The system cannot find the path specified.
2.013: KB898461 installation did not complete.
2.013: Update.exe extended error code = 0x3

"Dennisl" <> wrote in message
news:499D4700-3F50-44FC-B1C6-...
> Hi,
>
> I am gettign 0x80070003 tried most things in this group with no luck, heres
> the log I get can anyone PLEASE help:


> 1.843: LoadFileQueues: QueueMigrationStageFiles failed: 0x00000003

> 2.003: The system cannot find the path specified.



This is another example of a log which requires supplemental information
in order to understand the code.

The code means directory not found but the log gives no clue
which directory is not being found.

So, does this log come from an attempt at installing manually?
If so, presumably you haven't tried using its verbose option
(otherwise you probably would have posted the verbose log).

However, I haven't been very impressed with the quality of the verbose
diagnostics that I have seen; so what I usually recommend as a supplement
to the standard logging is to use SysInternals freeware tools FileMon and
RegMon. E.g. by using as simple a filter as the name of the update's
executable you could get a list of all the files being accessed and all the
registry keys being accessed.

Poster Andy Jones recently reported having some success with my
alternate technique for another issue which also had insufficient information
in the log. Try finding that thread if you want more information about it.


Good luck

Robert Aldwinckle
---