Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Update > Windows Installer 3.1 fails

Reply
Thread Tools Display Modes

Windows Installer 3.1 fails

 
 
Andy Jones
Guest
Posts: n/a

 
      01-09-2006
Hi,

I recently replaced the motherboard and did a repair install of XpSP2 in
order to keep my settings, etc. All well until I tried to access Windows
Update. It told me I needed to install the Windows Install 3.1 which it
download and installs but when the progress bar reaches about 3/4 it
tell me it failed.

The error seems to be Access Denied and here's the install log:

================================================== ==============================
0.109: 2006/01/09 16:53:20.062 (local)
0.109:
C:\WINDOWS\SoftwareDistribution\Download\ad9c4c2a7 79933f83b51a49a2c88838d\update\update.exe
(version 6.1.22.4)
0.109: Failed To Enable SE_SHUTDOWN_PRIVILEGE
0.109: Hotfix started with following command line: /norestart /quiet -er
/ParentInfo:280a12a6c3a7e448bc0514b4e5842349
2.500: In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed
with error 0x2
2.500: In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed
with error 0x2
2.500: DoInstallation: CleanPFR failed: 0x2
2.531: SetProductTypes: InfProductBuildType=BuildType.Sel
2.562: SetAltOsLoaderPath: No section uses DirId 65701; done.
2.687: DoInstallation: FetchSourceURL for
c:\windows\softwaredistribution\download\ad9c4c2a7 79933f83b51a49a2c88838d\update\update_wxp.inf
failed
2.687: CreateUninstall = 1,Directory =
C:\WINDOWS\$MSI31Uninstall_KB893803v2$
2.703: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll
failed: 0xe0000102
2.703: BuildCabinetManifest: update.url absent
2.703: Starting AnalyzeComponents
2.703: AnalyzePhaseZero used 0 ticks
2.719: No c:\windows\INF\updtblk.inf file.
2.719: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
2.719: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
9.297: SetupVerifyInfFile failed with error 0x490 for oem3.inf of device
DISPLAY\AOCA781\5&F603684&0&22446688&01&00
10.937: SetupVerifyInfFile failed with error 0x490 for oem32.inf of
device DISPLAY\VSC3513\5&376B3B4F&1&22446688&01&00
15.469: Third Party Provider = VIA Technologies, Inc. for
PCI\VEN_1106&DEV_0282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&00
15.859: Third Party Provider = VIA Technologies, Inc. for
PCI\VEN_1106&DEV_1282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&01
16.109: Third Party Provider = VIA Technologies, Inc. for
PCI\VEN_1106&DEV_2282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&02
19.469:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem9.CAT
trusts inf c:\windows\inf\oem9.inf of device
PCI\VEN_1106&DEV_3104&SUBSYS_31041106&REV_82\3&61A AA01&0&83
19.672:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem9.CAT
trusts inf c:\windows\inf\oem9.inf of device
PCI\VEN_1106&DEV_3104&SUBSYS_50041458&REV_86\3&13C 0B0C5&0&84
19.953: Third Party Provider = VIA Technologies, Inc. for
PCI\VEN_1106&DEV_3177&SUBSYS_00000000&REV_00\3&61A AA01&0&88
20.203: Third Party Provider = VIA Technologies, Inc. for
PCI\VEN_1106&DEV_3227&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&88
20.453: Third Party Provider = VIA Technologies, Inc. for
PCI\VEN_1106&DEV_3282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&03
20.703: Third Party Provider = VIA Technologies, Inc. for
PCI\VEN_1106&DEV_4282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&04
20.953: Third Party Provider = VIA Technologies, Inc. for
PCI\VEN_1106&DEV_7282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&07
21.484: Failed to query DriverPath of ROOT\LEGACY_EMU10K1\0000 0x2
21.500: Failed to query DriverPath of ROOT\LEGACY_SFMAN\0000 0x2
22.859: SetupVerifyInfFile failed with error 0x490 for
c:\windows\inf\wtablet.inf of device SERENUM\WAC0A50\4&23DE782&0&0000
28.687: SetupVerifyInfFile failed with error 0x490 for canondc2.inf of
device USB\VID_04A9&PID_3052\5&13F82F15&0&2
29.906: SetupOpenInfFile in IsThirdPartyInf Failed with error 0x2
29.906: SetupOpenInfFile in IsThirdPartyInf Failed with error 0x2
30.109: OEM file scan used 27390 ticks
30.562: AnalyzePhaseOne: used 27859 ticks
30.562: AnalyzeComponents: Hotpatch analysis disabled; skipping.
30.562: AnalyzeComponents: Hotpatching is disabled.
30.562: AnalyzePhaseTwo used 0 ticks
30.562: AnalyzePhaseThree used 0 ticks
30.562: AnalyzePhaseFive used 0 ticks
30.562: AnalyzePhaseSix used 0 ticks
30.562: AnalyzeComponents used 27859 ticks
30.562: Downloading 0 files
30.562: bPatchMode = FALSE
30.562: Inventory complete: ReturnStatus=0, 27875 ticks
30.578: Num Ticks for invent : 27891
30.609: Conditional load of section MSI.Reg.Install.Condition succeeded
30.609: Allocation size of drive C: is 4096 bytes, free space =
11436216320 bytes
30.609: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
30.609: Drive C: free 10906MB req: 5MB w/uninstall: NOT CALCULATED.
30.609: CabinetBuild complete
30.609: Num Ticks for Cabinet build : 31
30.609: DynamicStrings section not defined or empty.
30.625: FileInUse:: need to restart already, turn off
30.625: FileInUse:: Add to list - Service Name: msiserver
31.625: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll
failed: 0xe0000102
31.797: Num Ticks for Backup : 1188
39.703: Num Ticks for creating uninst inf : 7906
39.703: Registering Uninstall Program for -> KB893803v2, KB893803v2 , 0x0
39.703: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll
failed: 0xe0000102
39.719: System Restore Point set.
39.781: PFE2: Not avoiding Per File Exceptions.
39.797: GetCatVersion: Failed to retrieve version information from
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Tmp.0.KB893803v2_wxp.cat
with error 0x57
41.156: Copied file: C:\WINDOWS\system32\msi.dll
41.219: Copied file: C:\WINDOWS\system32\msiexec.exe
41.265: Copied file: C:\WINDOWS\system32\msihnd.dll
41.422: Copied file: C:\WINDOWS\system32\msimsg.dll
41.484: Copied file: C:\WINDOWS\system32\msisip.dll
41.625: Copied file: C:\WINDOWS\system32\DllCache\msi.dll
41.672: Copied file: C:\WINDOWS\system32\DllCache\msiexec.exe
41.687: Copied file: C:\WINDOWS\system32\DllCache\msihnd.dll
41.765: Copied file: C:\WINDOWS\system32\DllCache\msimsg.dll
41.765: Copied file: C:\WINDOWS\system32\DllCache\msisip.dll
41.781: DoInstallation: Installing assemblies with source root path:
c:\windows\softwaredistribution\download\ad9c4c2a7 79933f83b51a49a2c88838d\
41.781: Num Ticks for Copying files : 2078
42.031: DoRegistryUpdates:UpdSpInstallFromInfSection Failed for
MSI.Reg.Install: 0x5
42.031: DoInstallationoRegistryUpdates failed
42.078: Access is denied.
42.078: KB893803v2 installation did not complete.

Select 'OK' to undo the changes that have been made.
42.078: Starting process:
C:\WINDOWS\$MSI31Uninstall_KB893803v2$\spuninst\sp uninst.exe /~ -q -z
47.078: Software Update Rollback has completed with return code 0xbc2.
This rollback requires a reboot.
47.078: KB893803v2 installation did not complete.

Windows Installer has been partially updated and may not work properly.
47.078: Update.exe extended error code = 0x5
================================================== ==============================

Does anyone have any idea as to what's going wrong and how I can fix it?

Many thanks,

Andy

--
remove BRAIN to reply
 
Reply With Quote
 
 
 
 
Tom
Guest
Posts: n/a

 
      01-09-2006
you and me and thousands of other people.
I have spent over 100 hours on this now, with no help from MS.

Please open a Microsoft phone support call so they fix it.
Don't let them close the call, as they will try for no reason, until it's
fixed.

Thnx.


"Andy Jones" <> wrote in message
news:...
> Hi,
>
> I recently replaced the motherboard and did a repair install of XpSP2 in
> order to keep my settings, etc. All well until I tried to access Windows
> Update. It told me I needed to install the Windows Install 3.1 which it
> download and installs but when the progress bar reaches about 3/4 it tell
> me it failed.
>
> The error seems to be Access Denied and here's the install log:
>
> ================================================== ==============================
> 0.109: 2006/01/09 16:53:20.062 (local)
> 0.109:
> C:\WINDOWS\SoftwareDistribution\Download\ad9c4c2a7 79933f83b51a49a2c88838d\update\update.exe
> (version 6.1.22.4)
> 0.109: Failed To Enable SE_SHUTDOWN_PRIVILEGE
> 0.109: Hotfix started with following command line: /norestart /quiet -er
> /ParentInfo:280a12a6c3a7e448bc0514b4e5842349
> 2.500: In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed with
> error 0x2
> 2.500: In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed with
> error 0x2
> 2.500: DoInstallation: CleanPFR failed: 0x2
> 2.531: SetProductTypes: InfProductBuildType=BuildType.Sel
> 2.562: SetAltOsLoaderPath: No section uses DirId 65701; done.
> 2.687: DoInstallation: FetchSourceURL for
> c:\windows\softwaredistribution\download\ad9c4c2a7 79933f83b51a49a2c88838d\update\update_wxp.inf
> failed
> 2.687: CreateUninstall = 1,Directory =
> C:\WINDOWS\$MSI31Uninstall_KB893803v2$
> 2.703: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
> 0xe0000102
> 2.703: BuildCabinetManifest: update.url absent
> 2.703: Starting AnalyzeComponents
> 2.703: AnalyzePhaseZero used 0 ticks
> 2.719: No c:\windows\INF\updtblk.inf file.
> 2.719: SetupFindFirstLine in LoadExclusionList Failed with error:
> 0xe0000102
> 2.719: SetupFindFirstLine in LoadExclusionList Failed with error:
> 0xe0000102
> 9.297: SetupVerifyInfFile failed with error 0x490 for oem3.inf of device
> DISPLAY\AOCA781\5&F603684&0&22446688&01&00
> 10.937: SetupVerifyInfFile failed with error 0x490 for oem32.inf of device
> DISPLAY\VSC3513\5&376B3B4F&1&22446688&01&00
> 15.469: Third Party Provider = VIA Technologies, Inc. for
> PCI\VEN_1106&DEV_0282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&00
> 15.859: Third Party Provider = VIA Technologies, Inc. for
> PCI\VEN_1106&DEV_1282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&01
> 16.109: Third Party Provider = VIA Technologies, Inc. for
> PCI\VEN_1106&DEV_2282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&02
> 19.469:
> C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem9.CAT
> trusts inf c:\windows\inf\oem9.inf of device
> PCI\VEN_1106&DEV_3104&SUBSYS_31041106&REV_82\3&61A AA01&0&83
> 19.672:
> C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem9.CAT
> trusts inf c:\windows\inf\oem9.inf of device
> PCI\VEN_1106&DEV_3104&SUBSYS_50041458&REV_86\3&13C 0B0C5&0&84
> 19.953: Third Party Provider = VIA Technologies, Inc. for
> PCI\VEN_1106&DEV_3177&SUBSYS_00000000&REV_00\3&61A AA01&0&88
> 20.203: Third Party Provider = VIA Technologies, Inc. for
> PCI\VEN_1106&DEV_3227&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&88
> 20.453: Third Party Provider = VIA Technologies, Inc. for
> PCI\VEN_1106&DEV_3282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&03
> 20.703: Third Party Provider = VIA Technologies, Inc. for
> PCI\VEN_1106&DEV_4282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&04
> 20.953: Third Party Provider = VIA Technologies, Inc. for
> PCI\VEN_1106&DEV_7282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&07
> 21.484: Failed to query DriverPath of ROOT\LEGACY_EMU10K1\0000 0x2
> 21.500: Failed to query DriverPath of ROOT\LEGACY_SFMAN\0000 0x2
> 22.859: SetupVerifyInfFile failed with error 0x490 for
> c:\windows\inf\wtablet.inf of device SERENUM\WAC0A50\4&23DE782&0&0000
> 28.687: SetupVerifyInfFile failed with error 0x490 for canondc2.inf of
> device USB\VID_04A9&PID_3052\5&13F82F15&0&2
> 29.906: SetupOpenInfFile in IsThirdPartyInf Failed with error 0x2
> 29.906: SetupOpenInfFile in IsThirdPartyInf Failed with error 0x2
> 30.109: OEM file scan used 27390 ticks
> 30.562: AnalyzePhaseOne: used 27859 ticks
> 30.562: AnalyzeComponents: Hotpatch analysis disabled; skipping.
> 30.562: AnalyzeComponents: Hotpatching is disabled.
> 30.562: AnalyzePhaseTwo used 0 ticks
> 30.562: AnalyzePhaseThree used 0 ticks
> 30.562: AnalyzePhaseFive used 0 ticks
> 30.562: AnalyzePhaseSix used 0 ticks
> 30.562: AnalyzeComponents used 27859 ticks
> 30.562: Downloading 0 files
> 30.562: bPatchMode = FALSE
> 30.562: Inventory complete: ReturnStatus=0, 27875 ticks
> 30.578: Num Ticks for invent : 27891
> 30.609: Conditional load of section MSI.Reg.Install.Condition succeeded
> 30.609: Allocation size of drive C: is 4096 bytes, free space =
> 11436216320 bytes
> 30.609: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
> 30.609: Drive C: free 10906MB req: 5MB w/uninstall: NOT CALCULATED.
> 30.609: CabinetBuild complete
> 30.609: Num Ticks for Cabinet build : 31
> 30.609: DynamicStrings section not defined or empty.
> 30.625: FileInUse:: need to restart already, turn off
> 30.625: FileInUse:: Add to list - Service Name: msiserver
> 31.625: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll
> failed: 0xe0000102
> 31.797: Num Ticks for Backup : 1188
> 39.703: Num Ticks for creating uninst inf : 7906
> 39.703: Registering Uninstall Program for -> KB893803v2, KB893803v2 , 0x0
> 39.703: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll
> failed: 0xe0000102
> 39.719: System Restore Point set.
> 39.781: PFE2: Not avoiding Per File Exceptions.
> 39.797: GetCatVersion: Failed to retrieve version information from
> C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Tmp.0.KB893803v2_wxp.cat
> with error 0x57
> 41.156: Copied file: C:\WINDOWS\system32\msi.dll
> 41.219: Copied file: C:\WINDOWS\system32\msiexec.exe
> 41.265: Copied file: C:\WINDOWS\system32\msihnd.dll
> 41.422: Copied file: C:\WINDOWS\system32\msimsg.dll
> 41.484: Copied file: C:\WINDOWS\system32\msisip.dll
> 41.625: Copied file: C:\WINDOWS\system32\DllCache\msi.dll
> 41.672: Copied file: C:\WINDOWS\system32\DllCache\msiexec.exe
> 41.687: Copied file: C:\WINDOWS\system32\DllCache\msihnd.dll
> 41.765: Copied file: C:\WINDOWS\system32\DllCache\msimsg.dll
> 41.765: Copied file: C:\WINDOWS\system32\DllCache\msisip.dll
> 41.781: DoInstallation: Installing assemblies with source root path:
> c:\windows\softwaredistribution\download\ad9c4c2a7 79933f83b51a49a2c88838d\
> 41.781: Num Ticks for Copying files : 2078
> 42.031: DoRegistryUpdates:UpdSpInstallFromInfSection Failed for
> MSI.Reg.Install: 0x5
> 42.031: DoInstallationoRegistryUpdates failed
> 42.078: Access is denied.
> 42.078: KB893803v2 installation did not complete.
>
> Select 'OK' to undo the changes that have been made.
> 42.078: Starting process:
> C:\WINDOWS\$MSI31Uninstall_KB893803v2$\spuninst\sp uninst.exe /~ -q -z
> 47.078: Software Update Rollback has completed with return code 0xbc2.
> This rollback requires a reboot.
> 47.078: KB893803v2 installation did not complete.
>
> Windows Installer has been partially updated and may not work properly.
> 47.078: Update.exe extended error code = 0x5
> ================================================== ==============================
>
> Does anyone have any idea as to what's going wrong and how I can fix it?
>
> Many thanks,
>
> Andy
>
> --
> remove BRAIN to reply



 
Reply With Quote
 
FireWall2
Guest
Posts: n/a

 
      01-09-2006
Hello Tom,
Have read many of your Post within Communities, sincere question, are you
always an instigator of trouble or just most of the time? Most all your Post
include a repeated syntax something as telephone Microsoft before you are
aware of specific tech details.

All the folks that make Post within Communities work for free, including
MVPs. If a person is running older versions of Windows and/or OEM Windows,
there is not one single thing Microsoft Tech Support can assist that person.

The OEM Versions are the number one greatest trouble makers because they
slaughtered and infested Microsoft’s excellent OS by polluting the OS with
their OEM third party software that produces enormous application conflicts.
The OEM OS belongs to the builder of their machine; it is not an authentic
Microsoft OS. Hence, that being the situation it is an abuse of time
telephoning MS Tech Support; somewhat as some Posts are nothing more than a
flagrant abuse of readers time.


--
Firewall


"Tom" wrote:

> you and me and thousands of other people.
> I have spent over 100 hours on this now, with no help from MS.
>
> Please open a Microsoft phone support call so they fix it.
> Don't let them close the call, as they will try for no reason, until it's
> fixed.
>
> Thnx.
>
>
> "Andy Jones" <> wrote in message
> news:...
> > Hi,
> >
> > I recently replaced the motherboard and did a repair install of XpSP2 in
> > order to keep my settings, etc. All well until I tried to access Windows
> > Update. It told me I needed to install the Windows Install 3.1 which it
> > download and installs but when the progress bar reaches about 3/4 it tell
> > me it failed.
> >
> > The error seems to be Access Denied and here's the install log:
> >
> > ================================================== ==============================
> > 0.109: 2006/01/09 16:53:20.062 (local)
> > 0.109:
> > C:\WINDOWS\SoftwareDistribution\Download\ad9c4c2a7 79933f83b51a49a2c88838d\update\update.exe
> > (version 6.1.22.4)
> > 0.109: Failed To Enable SE_SHUTDOWN_PRIVILEGE
> > 0.109: Hotfix started with following command line: /norestart /quiet -er
> > /ParentInfo:280a12a6c3a7e448bc0514b4e5842349
> > 2.500: In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed with
> > error 0x2
> > 2.500: In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed with
> > error 0x2
> > 2.500: DoInstallation: CleanPFR failed: 0x2
> > 2.531: SetProductTypes: InfProductBuildType=BuildType.Sel
> > 2.562: SetAltOsLoaderPath: No section uses DirId 65701; done.
> > 2.687: DoInstallation: FetchSourceURL for
> > c:\windows\softwaredistribution\download\ad9c4c2a7 79933f83b51a49a2c88838d\update\update_wxp.inf
> > failed
> > 2.687: CreateUninstall = 1,Directory =
> > C:\WINDOWS\$MSI31Uninstall_KB893803v2$
> > 2.703: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
> > 0xe0000102
> > 2.703: BuildCabinetManifest: update.url absent
> > 2.703: Starting AnalyzeComponents
> > 2.703: AnalyzePhaseZero used 0 ticks
> > 2.719: No c:\windows\INF\updtblk.inf file.
> > 2.719: SetupFindFirstLine in LoadExclusionList Failed with error:
> > 0xe0000102
> > 2.719: SetupFindFirstLine in LoadExclusionList Failed with error:
> > 0xe0000102
> > 9.297: SetupVerifyInfFile failed with error 0x490 for oem3.inf of device
> > DISPLAY\AOCA781\5&F603684&0&22446688&01&00
> > 10.937: SetupVerifyInfFile failed with error 0x490 for oem32.inf of device
> > DISPLAY\VSC3513\5&376B3B4F&1&22446688&01&00
> > 15.469: Third Party Provider = VIA Technologies, Inc. for
> > PCI\VEN_1106&DEV_0282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&00
> > 15.859: Third Party Provider = VIA Technologies, Inc. for
> > PCI\VEN_1106&DEV_1282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&01
> > 16.109: Third Party Provider = VIA Technologies, Inc. for
> > PCI\VEN_1106&DEV_2282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&02
> > 19.469:
> > C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem9.CAT
> > trusts inf c:\windows\inf\oem9.inf of device
> > PCI\VEN_1106&DEV_3104&SUBSYS_31041106&REV_82\3&61A AA01&0&83
> > 19.672:
> > C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem9.CAT
> > trusts inf c:\windows\inf\oem9.inf of device
> > PCI\VEN_1106&DEV_3104&SUBSYS_50041458&REV_86\3&13C 0B0C5&0&84
> > 19.953: Third Party Provider = VIA Technologies, Inc. for
> > PCI\VEN_1106&DEV_3177&SUBSYS_00000000&REV_00\3&61A AA01&0&88
> > 20.203: Third Party Provider = VIA Technologies, Inc. for
> > PCI\VEN_1106&DEV_3227&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&88
> > 20.453: Third Party Provider = VIA Technologies, Inc. for
> > PCI\VEN_1106&DEV_3282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&03
> > 20.703: Third Party Provider = VIA Technologies, Inc. for
> > PCI\VEN_1106&DEV_4282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&04
> > 20.953: Third Party Provider = VIA Technologies, Inc. for
> > PCI\VEN_1106&DEV_7282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&07
> > 21.484: Failed to query DriverPath of ROOT\LEGACY_EMU10K1\0000 0x2
> > 21.500: Failed to query DriverPath of ROOT\LEGACY_SFMAN\0000 0x2
> > 22.859: SetupVerifyInfFile failed with error 0x490 for
> > c:\windows\inf\wtablet.inf of device SERENUM\WAC0A50\4&23DE782&0&0000
> > 28.687: SetupVerifyInfFile failed with error 0x490 for canondc2.inf of
> > device USB\VID_04A9&PID_3052\5&13F82F15&0&2
> > 29.906: SetupOpenInfFile in IsThirdPartyInf Failed with error 0x2
> > 29.906: SetupOpenInfFile in IsThirdPartyInf Failed with error 0x2
> > 30.109: OEM file scan used 27390 ticks
> > 30.562: AnalyzePhaseOne: used 27859 ticks
> > 30.562: AnalyzeComponents: Hotpatch analysis disabled; skipping.
> > 30.562: AnalyzeComponents: Hotpatching is disabled.
> > 30.562: AnalyzePhaseTwo used 0 ticks
> > 30.562: AnalyzePhaseThree used 0 ticks
> > 30.562: AnalyzePhaseFive used 0 ticks
> > 30.562: AnalyzePhaseSix used 0 ticks
> > 30.562: AnalyzeComponents used 27859 ticks
> > 30.562: Downloading 0 files
> > 30.562: bPatchMode = FALSE
> > 30.562: Inventory complete: ReturnStatus=0, 27875 ticks
> > 30.578: Num Ticks for invent : 27891
> > 30.609: Conditional load of section MSI.Reg.Install.Condition succeeded
> > 30.609: Allocation size of drive C: is 4096 bytes, free space =
> > 11436216320 bytes
> > 30.609: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
> > 30.609: Drive C: free 10906MB req: 5MB w/uninstall: NOT CALCULATED.
> > 30.609: CabinetBuild complete
> > 30.609: Num Ticks for Cabinet build : 31
> > 30.609: DynamicStrings section not defined or empty.
> > 30.625: FileInUse:: need to restart already, turn off
> > 30.625: FileInUse:: Add to list - Service Name: msiserver
> > 31.625: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll
> > failed: 0xe0000102
> > 31.797: Num Ticks for Backup : 1188
> > 39.703: Num Ticks for creating uninst inf : 7906
> > 39.703: Registering Uninstall Program for -> KB893803v2, KB893803v2 , 0x0
> > 39.703: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll
> > failed: 0xe0000102
> > 39.719: System Restore Point set.
> > 39.781: PFE2: Not avoiding Per File Exceptions.
> > 39.797: GetCatVersion: Failed to retrieve version information from
> > C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Tmp.0.KB893803v2_wxp.cat
> > with error 0x57
> > 41.156: Copied file: C:\WINDOWS\system32\msi.dll
> > 41.219: Copied file: C:\WINDOWS\system32\msiexec.exe
> > 41.265: Copied file: C:\WINDOWS\system32\msihnd.dll
> > 41.422: Copied file: C:\WINDOWS\system32\msimsg.dll
> > 41.484: Copied file: C:\WINDOWS\system32\msisip.dll
> > 41.625: Copied file: C:\WINDOWS\system32\DllCache\msi.dll
> > 41.672: Copied file: C:\WINDOWS\system32\DllCache\msiexec.exe
> > 41.687: Copied file: C:\WINDOWS\system32\DllCache\msihnd.dll
> > 41.765: Copied file: C:\WINDOWS\system32\DllCache\msimsg.dll
> > 41.765: Copied file: C:\WINDOWS\system32\DllCache\msisip.dll
> > 41.781: DoInstallation: Installing assemblies with source root path:
> > c:\windows\softwaredistribution\download\ad9c4c2a7 79933f83b51a49a2c88838d\
> > 41.781: Num Ticks for Copying files : 2078
> > 42.031: DoRegistryUpdates:UpdSpInstallFromInfSection Failed for
> > MSI.Reg.Install: 0x5
> > 42.031: DoInstallationoRegistryUpdates failed
> > 42.078: Access is denied.
> > 42.078: KB893803v2 installation did not complete.
> >
> > Select 'OK' to undo the changes that have been made.
> > 42.078: Starting process:
> > C:\WINDOWS\$MSI31Uninstall_KB893803v2$\spuninst\sp uninst.exe /~ -q -z
> > 47.078: Software Update Rollback has completed with return code 0xbc2.
> > This rollback requires a reboot.
> > 47.078: KB893803v2 installation did not complete.
> >
> > Windows Installer has been partially updated and may not work properly.
> > 47.078: Update.exe extended error code = 0x5
> > ================================================== ==============================
> >
> > Does anyone have any idea as to what's going wrong and how I can fix it?
> >
> > Many thanks,
> >
> > Andy
> >
> > --
> > remove BRAIN to reply

>
>
>

 
Reply With Quote
 
Tom
Guest
Posts: n/a

 
      01-09-2006
Sorry pal, but my OS is up to date and this is full retail version.
I was nice and polite on here for a very long week, until I started getting
**** from these guys.
That and the phone support deal, over 50 hours to be exact, was a complete
and total circus waste of both our time.


"FireWall2" <> wrote in message
news:5DEEEC8D-CA0B-42D0-89B3-...
> Hello Tom,
> Have read many of your Post within Communities, sincere question, are you
> always an instigator of trouble or just most of the time? Most all your
> Post
> include a repeated syntax something as telephone Microsoft before you are
> aware of specific tech details.
>
> All the folks that make Post within Communities work for free, including
> MVPs. If a person is running older versions of Windows and/or OEM Windows,
> there is not one single thing Microsoft Tech Support can assist that
> person.
>
> The OEM Versions are the number one greatest trouble makers because they
> slaughtered and infested Microsoft's excellent OS by polluting the OS with
> their OEM third party software that produces enormous application
> conflicts.
> The OEM OS belongs to the builder of their machine; it is not an authentic
> Microsoft OS. Hence, that being the situation it is an abuse of time
> telephoning MS Tech Support; somewhat as some Posts are nothing more than
> a
> flagrant abuse of readers time.
>
>
> --
> Firewall
>
>
> "Tom" wrote:
>
>> you and me and thousands of other people.
>> I have spent over 100 hours on this now, with no help from MS.
>>
>> Please open a Microsoft phone support call so they fix it.
>> Don't let them close the call, as they will try for no reason, until it's
>> fixed.
>>
>> Thnx.
>>
>>
>> "Andy Jones" <> wrote in message
>> news:...
>> > Hi,
>> >
>> > I recently replaced the motherboard and did a repair install of XpSP2
>> > in
>> > order to keep my settings, etc. All well until I tried to access
>> > Windows
>> > Update. It told me I needed to install the Windows Install 3.1 which it
>> > download and installs but when the progress bar reaches about 3/4 it
>> > tell
>> > me it failed.
>> >
>> > The error seems to be Access Denied and here's the install log:
>> >
>> > ================================================== ==============================
>> > 0.109: 2006/01/09 16:53:20.062 (local)
>> > 0.109:
>> > C:\WINDOWS\SoftwareDistribution\Download\ad9c4c2a7 79933f83b51a49a2c88838d\update\update.exe
>> > (version 6.1.22.4)
>> > 0.109: Failed To Enable SE_SHUTDOWN_PRIVILEGE
>> > 0.109: Hotfix started with following command line: /norestart
>> > /quiet -er
>> > /ParentInfo:280a12a6c3a7e448bc0514b4e5842349
>> > 2.500: In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed
>> > with
>> > error 0x2
>> > 2.500: In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed
>> > with
>> > error 0x2
>> > 2.500: DoInstallation: CleanPFR failed: 0x2
>> > 2.531: SetProductTypes: InfProductBuildType=BuildType.Sel
>> > 2.562: SetAltOsLoaderPath: No section uses DirId 65701; done.
>> > 2.687: DoInstallation: FetchSourceURL for
>> > c:\windows\softwaredistribution\download\ad9c4c2a7 79933f83b51a49a2c88838d\update\update_wxp.inf
>> > failed
>> > 2.687: CreateUninstall = 1,Directory =
>> > C:\WINDOWS\$MSI31Uninstall_KB893803v2$
>> > 2.703: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll
>> > failed:
>> > 0xe0000102
>> > 2.703: BuildCabinetManifest: update.url absent
>> > 2.703: Starting AnalyzeComponents
>> > 2.703: AnalyzePhaseZero used 0 ticks
>> > 2.719: No c:\windows\INF\updtblk.inf file.
>> > 2.719: SetupFindFirstLine in LoadExclusionList Failed with error:
>> > 0xe0000102
>> > 2.719: SetupFindFirstLine in LoadExclusionList Failed with error:
>> > 0xe0000102
>> > 9.297: SetupVerifyInfFile failed with error 0x490 for oem3.inf of
>> > device
>> > DISPLAY\AOCA781\5&F603684&0&22446688&01&00
>> > 10.937: SetupVerifyInfFile failed with error 0x490 for oem32.inf of
>> > device
>> > DISPLAY\VSC3513\5&376B3B4F&1&22446688&01&00
>> > 15.469: Third Party Provider = VIA Technologies, Inc. for
>> > PCI\VEN_1106&DEV_0282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&00
>> > 15.859: Third Party Provider = VIA Technologies, Inc. for
>> > PCI\VEN_1106&DEV_1282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&01
>> > 16.109: Third Party Provider = VIA Technologies, Inc. for
>> > PCI\VEN_1106&DEV_2282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&02
>> > 19.469:
>> > C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem9.CAT
>> > trusts inf c:\windows\inf\oem9.inf of device
>> > PCI\VEN_1106&DEV_3104&SUBSYS_31041106&REV_82\3&61A AA01&0&83
>> > 19.672:
>> > C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem9.CAT
>> > trusts inf c:\windows\inf\oem9.inf of device
>> > PCI\VEN_1106&DEV_3104&SUBSYS_50041458&REV_86\3&13C 0B0C5&0&84
>> > 19.953: Third Party Provider = VIA Technologies, Inc. for
>> > PCI\VEN_1106&DEV_3177&SUBSYS_00000000&REV_00\3&61A AA01&0&88
>> > 20.203: Third Party Provider = VIA Technologies, Inc. for
>> > PCI\VEN_1106&DEV_3227&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&88
>> > 20.453: Third Party Provider = VIA Technologies, Inc. for
>> > PCI\VEN_1106&DEV_3282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&03
>> > 20.703: Third Party Provider = VIA Technologies, Inc. for
>> > PCI\VEN_1106&DEV_4282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&04
>> > 20.953: Third Party Provider = VIA Technologies, Inc. for
>> > PCI\VEN_1106&DEV_7282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&07
>> > 21.484: Failed to query DriverPath of ROOT\LEGACY_EMU10K1\0000 0x2
>> > 21.500: Failed to query DriverPath of ROOT\LEGACY_SFMAN\0000 0x2
>> > 22.859: SetupVerifyInfFile failed with error 0x490 for
>> > c:\windows\inf\wtablet.inf of device SERENUM\WAC0A50\4&23DE782&0&0000
>> > 28.687: SetupVerifyInfFile failed with error 0x490 for canondc2.inf of
>> > device USB\VID_04A9&PID_3052\5&13F82F15&0&2
>> > 29.906: SetupOpenInfFile in IsThirdPartyInf Failed with error 0x2
>> > 29.906: SetupOpenInfFile in IsThirdPartyInf Failed with error 0x2
>> > 30.109: OEM file scan used 27390 ticks
>> > 30.562: AnalyzePhaseOne: used 27859 ticks
>> > 30.562: AnalyzeComponents: Hotpatch analysis disabled; skipping.
>> > 30.562: AnalyzeComponents: Hotpatching is disabled.
>> > 30.562: AnalyzePhaseTwo used 0 ticks
>> > 30.562: AnalyzePhaseThree used 0 ticks
>> > 30.562: AnalyzePhaseFive used 0 ticks
>> > 30.562: AnalyzePhaseSix used 0 ticks
>> > 30.562: AnalyzeComponents used 27859 ticks
>> > 30.562: Downloading 0 files
>> > 30.562: bPatchMode = FALSE
>> > 30.562: Inventory complete: ReturnStatus=0, 27875 ticks
>> > 30.578: Num Ticks for invent : 27891
>> > 30.609: Conditional load of section MSI.Reg.Install.Condition succeeded
>> > 30.609: Allocation size of drive C: is 4096 bytes, free space =
>> > 11436216320 bytes
>> > 30.609: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
>> > 30.609: Drive C: free 10906MB req: 5MB w/uninstall: NOT CALCULATED.
>> > 30.609: CabinetBuild complete
>> > 30.609: Num Ticks for Cabinet build : 31
>> > 30.609: DynamicStrings section not defined or empty.
>> > 30.625: FileInUse:: need to restart already, turn off
>> > 30.625: FileInUse:: Add to list - Service Name: msiserver
>> > 31.625: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll
>> > failed: 0xe0000102
>> > 31.797: Num Ticks for Backup : 1188
>> > 39.703: Num Ticks for creating uninst inf : 7906
>> > 39.703: Registering Uninstall Program for -> KB893803v2, KB893803v2 ,
>> > 0x0
>> > 39.703: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll
>> > failed: 0xe0000102
>> > 39.719: System Restore Point set.
>> > 39.781: PFE2: Not avoiding Per File Exceptions.
>> > 39.797: GetCatVersion: Failed to retrieve version information from
>> > C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Tmp.0.KB893803v2_wxp.cat
>> > with error 0x57
>> > 41.156: Copied file: C:\WINDOWS\system32\msi.dll
>> > 41.219: Copied file: C:\WINDOWS\system32\msiexec.exe
>> > 41.265: Copied file: C:\WINDOWS\system32\msihnd.dll
>> > 41.422: Copied file: C:\WINDOWS\system32\msimsg.dll
>> > 41.484: Copied file: C:\WINDOWS\system32\msisip.dll
>> > 41.625: Copied file: C:\WINDOWS\system32\DllCache\msi.dll
>> > 41.672: Copied file: C:\WINDOWS\system32\DllCache\msiexec.exe
>> > 41.687: Copied file: C:\WINDOWS\system32\DllCache\msihnd.dll
>> > 41.765: Copied file: C:\WINDOWS\system32\DllCache\msimsg.dll
>> > 41.765: Copied file: C:\WINDOWS\system32\DllCache\msisip.dll
>> > 41.781: DoInstallation: Installing assemblies with source root path:
>> > c:\windows\softwaredistribution\download\ad9c4c2a7 79933f83b51a49a2c88838d\
>> > 41.781: Num Ticks for Copying files : 2078
>> > 42.031: DoRegistryUpdates:UpdSpInstallFromInfSection Failed for
>> > MSI.Reg.Install: 0x5
>> > 42.031: DoInstallationoRegistryUpdates failed
>> > 42.078: Access is denied.
>> > 42.078: KB893803v2 installation did not complete.
>> >
>> > Select 'OK' to undo the changes that have been made.
>> > 42.078: Starting process:
>> > C:\WINDOWS\$MSI31Uninstall_KB893803v2$\spuninst\sp uninst.exe /~ -q -z
>> > 47.078: Software Update Rollback has completed with return code 0xbc2.
>> > This rollback requires a reboot.
>> > 47.078: KB893803v2 installation did not complete.
>> >
>> > Windows Installer has been partially updated and may not work properly.
>> > 47.078: Update.exe extended error code = 0x5
>> > ================================================== ==============================
>> >
>> > Does anyone have any idea as to what's going wrong and how I can fix
>> > it?
>> >
>> > Many thanks,
>> >
>> > Andy
>> >
>> > --
>> > remove BRAIN to reply

>>
>>
>>



 
Reply With Quote
 
FireWall2
Guest
Posts: n/a

 
      01-09-2006
Hello Tom,
After reading your Posts, the solution for you troubles is incredibly
simple, almost elementary, specifically re-activating; just simultaneously
press two keyboard keys. Try telephoning the Fee Based MS Tech Support, far
superior compared to free support.

--
Firewall 4


"Tom" wrote:

> Sorry pal, but my OS is up to date and this is full retail version.
> I was nice and polite on here for a very long week, until I started getting
> **** from these guys.
> That and the phone support deal, over 50 hours to be exact, was a complete
> and total circus waste of both our time.
>
>
> "FireWall2" <> wrote in message
> news:5DEEEC8D-CA0B-42D0-89B3-...
> > Hello Tom,
> > Have read many of your Post within Communities, sincere question, are you
> > always an instigator of trouble or just most of the time? Most all your
> > Post
> > include a repeated syntax something as telephone Microsoft before you are
> > aware of specific tech details.
> >
> > All the folks that make Post within Communities work for free, including
> > MVPs. If a person is running older versions of Windows and/or OEM Windows,
> > there is not one single thing Microsoft Tech Support can assist that
> > person.
> >
> > The OEM Versions are the number one greatest trouble makers because they
> > slaughtered and infested Microsoft's excellent OS by polluting the OS with
> > their OEM third party software that produces enormous application
> > conflicts.
> > The OEM OS belongs to the builder of their machine; it is not an authentic
> > Microsoft OS. Hence, that being the situation it is an abuse of time
> > telephoning MS Tech Support; somewhat as some Posts are nothing more than
> > a
> > flagrant abuse of readers time.
> >
> >
> > --
> > Firewall
> >
> >
> > "Tom" wrote:
> >
> >> you and me and thousands of other people.
> >> I have spent over 100 hours on this now, with no help from MS.
> >>
> >> Please open a Microsoft phone support call so they fix it.
> >> Don't let them close the call, as they will try for no reason, until it's
> >> fixed.
> >>
> >> Thnx.
> >>
> >>
> >> "Andy Jones" <> wrote in message
> >> news:...
> >> > Hi,
> >> >
> >> > I recently replaced the motherboard and did a repair install of XpSP2
> >> > in
> >> > order to keep my settings, etc. All well until I tried to access
> >> > Windows
> >> > Update. It told me I needed to install the Windows Install 3.1 which it
> >> > download and installs but when the progress bar reaches about 3/4 it
> >> > tell
> >> > me it failed.
> >> >
> >> > The error seems to be Access Denied and here's the install log:
> >> >
> >> > ================================================== ==============================
> >> > 0.109: 2006/01/09 16:53:20.062 (local)
> >> > 0.109:
> >> > C:\WINDOWS\SoftwareDistribution\Download\ad9c4c2a7 79933f83b51a49a2c88838d\update\update.exe
> >> > (version 6.1.22.4)
> >> > 0.109: Failed To Enable SE_SHUTDOWN_PRIVILEGE
> >> > 0.109: Hotfix started with following command line: /norestart
> >> > /quiet -er
> >> > /ParentInfo:280a12a6c3a7e448bc0514b4e5842349
> >> > 2.500: In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed
> >> > with
> >> > error 0x2
> >> > 2.500: In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed
> >> > with
> >> > error 0x2
> >> > 2.500: DoInstallation: CleanPFR failed: 0x2
> >> > 2.531: SetProductTypes: InfProductBuildType=BuildType.Sel
> >> > 2.562: SetAltOsLoaderPath: No section uses DirId 65701; done.
> >> > 2.687: DoInstallation: FetchSourceURL for
> >> > c:\windows\softwaredistribution\download\ad9c4c2a7 79933f83b51a49a2c88838d\update\update_wxp.inf
> >> > failed
> >> > 2.687: CreateUninstall = 1,Directory =
> >> > C:\WINDOWS\$MSI31Uninstall_KB893803v2$
> >> > 2.703: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll
> >> > failed:
> >> > 0xe0000102
> >> > 2.703: BuildCabinetManifest: update.url absent
> >> > 2.703: Starting AnalyzeComponents
> >> > 2.703: AnalyzePhaseZero used 0 ticks
> >> > 2.719: No c:\windows\INF\updtblk.inf file.
> >> > 2.719: SetupFindFirstLine in LoadExclusionList Failed with error:
> >> > 0xe0000102
> >> > 2.719: SetupFindFirstLine in LoadExclusionList Failed with error:
> >> > 0xe0000102
> >> > 9.297: SetupVerifyInfFile failed with error 0x490 for oem3.inf of
> >> > device
> >> > DISPLAY\AOCA781\5&F603684&0&22446688&01&00
> >> > 10.937: SetupVerifyInfFile failed with error 0x490 for oem32.inf of
> >> > device
> >> > DISPLAY\VSC3513\5&376B3B4F&1&22446688&01&00
> >> > 15.469: Third Party Provider = VIA Technologies, Inc. for
> >> > PCI\VEN_1106&DEV_0282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&00
> >> > 15.859: Third Party Provider = VIA Technologies, Inc. for
> >> > PCI\VEN_1106&DEV_1282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&01
> >> > 16.109: Third Party Provider = VIA Technologies, Inc. for
> >> > PCI\VEN_1106&DEV_2282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&02
> >> > 19.469:
> >> > C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem9.CAT
> >> > trusts inf c:\windows\inf\oem9.inf of device
> >> > PCI\VEN_1106&DEV_3104&SUBSYS_31041106&REV_82\3&61A AA01&0&83
> >> > 19.672:
> >> > C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem9.CAT
> >> > trusts inf c:\windows\inf\oem9.inf of device
> >> > PCI\VEN_1106&DEV_3104&SUBSYS_50041458&REV_86\3&13C 0B0C5&0&84
> >> > 19.953: Third Party Provider = VIA Technologies, Inc. for
> >> > PCI\VEN_1106&DEV_3177&SUBSYS_00000000&REV_00\3&61A AA01&0&88
> >> > 20.203: Third Party Provider = VIA Technologies, Inc. for
> >> > PCI\VEN_1106&DEV_3227&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&88
> >> > 20.453: Third Party Provider = VIA Technologies, Inc. for
> >> > PCI\VEN_1106&DEV_3282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&03
> >> > 20.703: Third Party Provider = VIA Technologies, Inc. for
> >> > PCI\VEN_1106&DEV_4282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&04
> >> > 20.953: Third Party Provider = VIA Technologies, Inc. for
> >> > PCI\VEN_1106&DEV_7282&SUBSYS_00000000&REV_00\3&13C 0B0C5&0&07
> >> > 21.484: Failed to query DriverPath of ROOT\LEGACY_EMU10K1\0000 0x2
> >> > 21.500: Failed to query DriverPath of ROOT\LEGACY_SFMAN\0000 0x2
> >> > 22.859: SetupVerifyInfFile failed with error 0x490 for
> >> > c:\windows\inf\wtablet.inf of device SERENUM\WAC0A50\4&23DE782&0&0000
> >> > 28.687: SetupVerifyInfFile failed with error 0x490 for canondc2.inf of
> >> > device USB\VID_04A9&PID_3052\5&13F82F15&0&2
> >> > 29.906: SetupOpenInfFile in IsThirdPartyInf Failed with error 0x2
> >> > 29.906: SetupOpenInfFile in IsThirdPartyInf Failed with error 0x2
> >> > 30.109: OEM file scan used 27390 ticks
> >> > 30.562: AnalyzePhaseOne: used 27859 ticks
> >> > 30.562: AnalyzeComponents: Hotpatch analysis disabled; skipping.
> >> > 30.562: AnalyzeComponents: Hotpatching is disabled.
> >> > 30.562: AnalyzePhaseTwo used 0 ticks
> >> > 30.562: AnalyzePhaseThree used 0 ticks
> >> > 30.562: AnalyzePhaseFive used 0 ticks
> >> > 30.562: AnalyzePhaseSix used 0 ticks
> >> > 30.562: AnalyzeComponents used 27859 ticks
> >> > 30.562: Downloading 0 files
> >> > 30.562: bPatchMode = FALSE
> >> > 30.562: Inventory complete: ReturnStatus=0, 27875 ticks
> >> > 30.578: Num Ticks for invent : 27891
> >> > 30.609: Conditional load of section MSI.Reg.Install.Condition succeeded
> >> > 30.609: Allocation size of drive C: is 4096 bytes, free space =
> >> > 11436216320 bytes
> >> > 30.609: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
> >> > 30.609: Drive C: free 10906MB req: 5MB w/uninstall: NOT CALCULATED.
> >> > 30.609: CabinetBuild complete
> >> > 30.609: Num Ticks for Cabinet build : 31
> >> > 30.609: DynamicStrings section not defined or empty.
> >> > 30.625: FileInUse:: need to restart already, turn off
> >> > 30.625: FileInUse:: Add to list - Service Name: msiserver
> >> > 31.625: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll
> >> > failed: 0xe0000102
> >> > 31.797: Num Ticks for Backup : 1188
> >> > 39.703: Num Ticks for creating uninst inf : 7906
> >> > 39.703: Registering Uninstall Program for -> KB893803v2, KB893803v2 ,
> >> > 0x0
> >> > 39.703: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll
> >> > failed: 0xe0000102
> >> > 39.719: System Restore Point set.
> >> > 39.781: PFE2: Not avoiding Per File Exceptions.
> >> > 39.797: GetCatVersion: Failed to retrieve version information from
> >> > C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Tmp.0.KB893803v2_wxp.cat
> >> > with error 0x57
> >> > 41.156: Copied file: C:\WINDOWS\system32\msi.dll
> >> > 41.219: Copied file: C:\WINDOWS\system32\msiexec.exe
> >> > 41.265: Copied file: C:\WINDOWS\system32\msihnd.dll
> >> > 41.422: Copied file: C:\WINDOWS\system32\msimsg.dll
> >> > 41.484: Copied file: C:\WINDOWS\system32\msisip.dll
> >> > 41.625: Copied file: C:\WINDOWS\system32\DllCache\msi.dll
> >> > 41.672: Copied file: C:\WINDOWS\system32\DllCache\msiexec.exe
> >> > 41.687: Copied file: C:\WINDOWS\system32\DllCache\msihnd.dll
> >> > 41.765: Copied file: C:\WINDOWS\system32\DllCache\msimsg.dll
> >> > 41.765: Copied file: C:\WINDOWS\system32\DllCache\msisip.dll
> >> > 41.781: DoInstallation: Installing assemblies with source root path:
> >> > c:\windows\softwaredistribution\download\ad9c4c2a7 79933f83b51a49a2c88838d\
> >> > 41.781: Num Ticks for Copying files : 2078
> >> > 42.031: DoRegistryUpdates:UpdSpInstallFromInfSection Failed for
> >> > MSI.Reg.Install: 0x5
> >> > 42.031: DoInstallationoRegistryUpdates failed
> >> > 42.078: Access is denied.
> >> > 42.078: KB893803v2 installation did not complete.
> >> >
> >> > Select 'OK' to undo the changes that have been made.
> >> > 42.078: Starting process:
> >> > C:\WINDOWS\$MSI31Uninstall_KB893803v2$\spuninst\sp uninst.exe /~ -q -z
> >> > 47.078: Software Update Rollback has completed with return code 0xbc2.
> >> > This rollback requires a reboot.
> >> > 47.078: KB893803v2 installation did not complete.
> >> >
> >> > Windows Installer has been partially updated and may not work properly.
> >> > 47.078: Update.exe extended error code = 0x5
> >> > ================================================== ==============================
> >> >
> >> > Does anyone have any idea as to what's going wrong and how I can fix
> >> > it?
> >> >
> >> > Many thanks,
> >> >
> >> > Andy
> >> >
> >> > --
> >> > remove BRAIN to reply
> >>
> >>
> >>

>
>
>

 
Reply With Quote
 
Robert Aldwinckle
Guest
Posts: n/a

 
      01-10-2006
"Andy Jones" <> wrote in message
news:
....
> 41.781: DoInstallation: Installing assemblies with source root path:
> c:\windows\softwaredistribution\download\ad9c4c2a7 79933f83b51a49a2c88838d\
> 41.781: Num Ticks for Copying files : 2078
> 42.031: DoRegistryUpdates:UpdSpInstallFromInfSection Failed for
> MSI.Reg.Install: 0x5
> 42.031: DoInstallationoRegistryUpdates failed
> 42.078: Access is denied.


....
> Does anyone have any idea as to what's going wrong and how I can fix it?




Yes, there is a permissions problem but unfortunately the default diagnostics
such as this log are inadequate for you to identify its exact nature.


It's possible that you might be able to get sufficient additional information
by invoking the update manually and using its /verbose option.
(I'm guessing that that update has a /verbose (or a /v) switch available
with it. Usually you can get a list of an update's options by starting it with
a /? switch.)

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.

If you use the tools' common options Clock Time and Show Milleseconds
you can further more easily correlate the additional trace information
with the messages in the install log(s). Although the granularity of the
timestamps in the install logs is not sufficient to directly identify
which message was being written when you notice FileMon
tracing a write to it, it is surprisingly easy to match them up based on
the pattern in the lengths of consecutive records. I use Notepad
with Word Wrap off and Status bar on to be able to see how long
each log record is.

Similarly, in the case of RegMon (which I suspect ultimately will show
you a problem key) it is very helpful having the the exact timestamp
for each log record down to the millesecond to be able to find
the correct context in it too. E.g. a procedure would be:

1. list the lengths of the messages you are interested in getting
more information about;
2. then search the FileMon trace for writes to the install log,
looking specifically for the set of them whose "write length:" values
match the lengths you observed using Notepad;
3. then take the timestamps from those trace records and prefix
them to the install log's records. (I actually open up a new Notepad
window and copy just the records I'm interested in to do this.)
4. (optionally) look at all the interleaved other file accesses which
may have had something to do with the production of the message
(e.g. in case the permissions problem is really an ACLS issue
and not a registry permissions issue after all.)
5. browse the RegMon log looking for records whose timestamps
fit within the same time period implied by the install log record
you are interested in and its preceding message.

Somewhere in those interleaved RegMon trace entries
you are bound to find the cause of the code 0x5


Good luck

Robert Aldwinckle
---


 
Reply With Quote
 
Andy Jones
Guest
Posts: n/a

 
      01-10-2006
Robert Aldwinckle wrote:

> 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.


Robert,

Many thanks for the help. I followed your advice and installed Regmon
and Filemon and filtered them for the update.exe. Sure enough it showed
a problem with permissions writing to the registry. A few mins spent in
Regedit and I discovered that the permissions were odd to say the least.
I copied the permissions across from another machine and I've just
installed 35 updates.

Thanks again.

If it helps anyone, here are the permissions I had to reset in order to
get this working.

HKEY_CLASSES_ROOT
In the advanced tab of permission I set:

Administrators Full Control
CREATOR OWNER Full Control (Subkeys only)
Power Users Special (Query, Set, Create Subkey, Enum. Subkey, Notify,
Delete, Read were all checked for allow)
SYSTEM Full Control
Users Read

I can't make any promises that this will fix the problem for anyone
else, but maybe it will help out.



--

Andy
(remove BRAIN to reply)
 
Reply With Quote
 
Tom
Guest
Posts: n/a

 
      01-10-2006
I am still waiting for someone to say thisis a safe maneuver.


"Andy Jones" <> wrote in message
news:P5ednXqEU_E1-...
> Robert Aldwinckle wrote:
>
>> 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.

>
> Robert,
>
> Many thanks for the help. I followed your advice and installed Regmon and
> Filemon and filtered them for the update.exe. Sure enough it showed a
> problem with permissions writing to the registry. A few mins spent in
> Regedit and I discovered that the permissions were odd to say the least. I
> copied the permissions across from another machine and I've just installed
> 35 updates.
>
> Thanks again.
>
> If it helps anyone, here are the permissions I had to reset in order to
> get this working.
>
> HKEY_CLASSES_ROOT
> In the advanced tab of permission I set:
>
> Administrators Full Control
> CREATOR OWNER Full Control (Subkeys only)
> Power Users Special (Query, Set, Create Subkey, Enum. Subkey, Notify,
> Delete, Read were all checked for allow)
> SYSTEM Full Control
> Users Read
>
> I can't make any promises that this will fix the problem for anyone else,
> but maybe it will help out.
>
>
>
> --
>
> Andy
> (remove BRAIN to reply)



 
Reply With Quote
 
Andy Jones
Guest
Posts: n/a

 
      01-10-2006
Tom wrote:
> I am still waiting for someone to say thisis a safe maneuver.


I can't answer that, but I feel fairly confident about it as I took the
settings from my mail server that is just an XP Pro SP2 install and only
runs MDaemon and anti-virus.

--

Andy
(remove BRAIN to reply)
 
Reply With Quote
 
Tom
Guest
Posts: n/a

 
      01-10-2006
but it's a server, right?
should have diff perms.

"Andy Jones" <> wrote in message
news:...
> Tom wrote:
>> I am still waiting for someone to say thisis a safe maneuver.

>
> I can't answer that, but I feel fairly confident about it as I took the
> settings from my mail server that is just an XP Pro SP2 install and only
> runs MDaemon and anti-virus.
>
> --
>
> Andy
> (remove BRAIN to reply)



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Co-installer fails(SetupDiGetSelectedDriver(....) fails on WIN VISTA) vpandey001@yahoo.com Windows Vista Drivers 3 03-24-2006 05:33 AM
Windows Installer 3.1 Update v1 to v2 fails tmp4@nigeno.de Windows Update 3 11-28-2005 02:31 PM
Windows Installer Generates 0x80242006 Error and Fails RDL1912 Windows Update 0 10-14-2005 08:20 PM
Windows Installer 3.1 fails with exit code 0x80070005 Belegdol Windows Update 1 08-17-2005 09:46 AM
Windows Installer 3.1 fails to install Peter Windows Update 1 06-25-2005 01:42 PM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59