Troubleshoot update failure


Go Back   Computer Help Articles > Windows Update
User Name
Password
FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 01-05-2006, 05:02 PM
DLS
 
Posts: n/a
Default Troubleshoot update failure

I get the following failure log for an update. How do I troubleshoot? I
reviewed KB906602 and KB902093.

[KB905414.log]
1.172:
================================================== ==============================
1.172: 2005/10/15 15:13:03.962 (local)
1.172:
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\c7c7973bf3758bace159edd33f582d4c\update\update. exe (version 6.1.22.4)
1.203: Hotfix started with following command line: /si
/ParentInfo:6e3386d121331e4ca0658259bbd30a12
2.016: DoInstallation: CleanPFR failed: 0x2
2.032: SetProductTypes: InfProductBuildType=BuildType.IS
2.032: SetAltOsLoaderPath: No section uses DirId 65701; done.
2.047: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB905414$
2.047: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
2.063: ref tag c:\windows\system32\sp4.cab does not exist
2.063: ref tag c:\windows\system32\sp3.cab does not exist
2.063: ref tag c:\windows\system32\sp2.cab does not exist
2.063: ref tag c:\windows\system32\sp1.cab does not exist
2.063: ref tag c:\windows\system32\driver.cab does not exist
2.063: ref tag c:\windows\system32\fp40ext.cab does not exist
2.063: ref tag c:\windows\system32\fp40ext1.cab does not exist
2.063: ref tag c:\windows\system32\wms4.cab does not exist
2.063: ref tag c:\windows\system32\wms41.cab does not exist
2.063: ref tag c:\windows\system32\ims.cab does not exist
2.063: ref tag c:\windows\system32\ims1.cab does not exist
2.063: ref tag c:\windows\system32\ins.cab does not exist
2.063: ref tag c:\windows\system32\ins1.cab does not exist
2.078: Starting AnalyzeComponents
2.078: AnalyzePhaseZero used 0 ticks
2.078: OEM file scan used 0 ticks
2.282: AnalyzePhaseOne: used 204 ticks
2.282: AnalyzeComponents: Hotpatch analysis disabled; skipping.
2.282: AnalyzeComponents: Hotpatching is disabled.
2.282: FindFirstFile c:\windows\$hf_mig$\*.*
2.360: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.360: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.360: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.360: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.360: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.360: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.360: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.360: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.360: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.360: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.360: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.360: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.375: AnalyzeForBranching used 15 ticks.
2.375: AnalyzePhaseTwo used 0 ticks
2.375: AnalyzePhaseThree used 0 ticks
2.391: AnalyzePhaseFive used 16 ticks
2.391: AnalyzePhaseSix used 0 ticks
2.391: AnalyzeComponents used 313 ticks
2.391: Downloading 2 files
2.391: bPatchMode = TRUE
2.391: Inventory complete: ReturnStatus=0, 344 ticks
2.391: Num Ticks for invent : 344
2.469: [dumpDownloadTask] Update.exe posting request file to download a
total of 5889 bytes (5889 bytes in patches and 0 bytes in fallbacks)
2.485: dumpDownloadTask returned 0xf200 (more files to download)
2.735: KB905414 installation did not complete.
2.735: Update.exe extended error code = 0xf200
1.125:
================================================== ==============================
1.125: 2005/10/15 15:14:03.619 (local)
1.141:
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\c7c7973bf3758bace159edd33f582d4c\update\update. exe (version 6.1.22.4)
1.141: Hotfix started with following command line: /si
/ParentInfo:f48107254fffd64bbecfde66c91447e7
2.375: DoInstallation: CleanPFR failed: 0x2
2.391: SetProductTypes: InfProductBuildType=BuildType.IS
2.391: SetAltOsLoaderPath: No section uses DirId 65701; done.
2.422: Express: 5,889 bytes were downloaded.
2.594: [PatchFilesFromResponseBlob] returning STATUS_READY_TO_INSTALL
2.704: KB905414 installation did not complete.
2.704: Update.exe extended error code = 0xf201
1.172:
================================================== ==============================
1.172: 2005/10/19 07:44:26.277 (local)
1.172:
C:\WINDOWS\SoftwareDistribution\Download\22944015f 08223278b8b5671cbd364c8\update\update.exe (version 6.1.22.4)
1.172: Failed To Enable SE_SHUTDOWN_PRIVILEGE
1.172: Failed To Enable SE_SECURITY_PRIVILEGE
1.188: Setup encountered an error: You do not have permission to update
Windows Server 2003.
Please contact your system administrator.
1.188: You do not have permission to update Windows Server 2003.
Please contact your system administrator.
1.188: Update.exe extended error code = 0xf004
1.110:
================================================== ==============================
1.110: 2005/10/23 05:19:15.220 (local)
1.110:
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\c7c7973bf3758bace159edd33f582d4c\update\update. exe (version 6.1.22.4)
1.125: Hotfix started with following command line: /si
/ParentInfo:fe92d80fd798c54a86e60fc849ca7131
1.703: DoInstallation: CleanPFR failed: 0x2
1.719: SetProductTypes: InfProductBuildType=BuildType.IS
1.719: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.735: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB905414$
1.735: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
1.750: ref tag c:\windows\system32\sp4.cab does not exist
1.750: ref tag c:\windows\system32\sp3.cab does not exist
1.750: ref tag c:\windows\system32\sp2.cab does not exist
1.750: ref tag c:\windows\system32\sp1.cab does not exist
1.750: ref tag c:\windows\system32\driver.cab does not exist
1.750: ref tag c:\windows\system32\fp40ext.cab does not exist
1.750: ref tag c:\windows\system32\fp40ext1.cab does not exist
1.750: ref tag c:\windows\system32\wms4.cab does not exist
1.750: ref tag c:\windows\system32\wms41.cab does not exist
1.750: ref tag c:\windows\system32\ims.cab does not exist
1.750: ref tag c:\windows\system32\ims1.cab does not exist
1.750: ref tag c:\windows\system32\ins.cab does not exist
1.750: ref tag c:\windows\system32\ins1.cab does not exist
1.750: Starting AnalyzeComponents
1.750: AnalyzePhaseZero used 0 ticks
1.750: OEM file scan used 0 ticks
1.844: AnalyzePhaseOne: used 94 ticks
1.844: AnalyzeComponents: Hotpatch analysis disabled; skipping.
1.844: AnalyzeComponents: Hotpatching is disabled.
1.844: FindFirstFile c:\windows\$hf_mig$\*.*
1.922: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.922: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.922: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.922: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.922: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.922: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.922: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.922: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.922: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.922: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.922: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.922: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.938: AnalyzeForBranching used 16 ticks.
2.000: AnalyzePhaseTwo used 62 ticks
2.000: AnalyzePhaseThree used 0 ticks
2.000: AnalyzePhaseFive used 0 ticks
2.000: AnalyzePhaseSix used 0 ticks
2.000: AnalyzeComponents used 250 ticks
2.000: Downloading 0 files
2.000: bPatchMode = TRUE
2.000: Inventory complete: ReturnStatus=0, 265 ticks
2.000: Num Ticks for invent : 265
2.000: [dumpDownloadTask] We have all necessary files for the package to
install. Return STATUS_READY_TO_INSTALL
2.000: dumpDownloadTask returned 0xf201 (ready to install)
2.032: KB905414 installation did not complete.
2.032: Update.exe extended error code = 0xf201
1.172:
================================================== ==============================
1.187: 2005/10/26 18:14:48.454 (local)
1.203:
C:\WINDOWS\SoftwareDistribution\Download\22944015f 08223278b8b5671cbd364c8\update\update.exe (version 6.1.22.4)
1.203: Failed To Enable SE_SHUTDOWN_PRIVILEGE
1.203: Failed To Enable SE_SECURITY_PRIVILEGE
1.203: Setup encountered an error: You do not have permission to update
Windows Server 2003.
Please contact your system administrator.
1.203: You do not have permission to update Windows Server 2003.
Please contact your system administrator.
1.203: Update.exe extended error code = 0xf004
1.125:
================================================== ==============================
1.125: 2005/10/26 18:16:28.033 (local)
1.125:
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\c7c7973bf3758bace159edd33f582d4c\update\update. exe (version 6.1.22.4)
1.125: Hotfix started with following command line: /si
/ParentInfo:4c32ce5f3e17c849b04ab87eb0ba48a2
1.750: DoInstallation: CleanPFR failed: 0x2
1.750: SetProductTypes: InfProductBuildType=BuildType.IS
1.750: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.765: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB905414$
1.781: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
1.796: ref tag c:\windows\system32\sp4.cab does not exist
1.796: ref tag c:\windows\system32\sp3.cab does not exist
1.796: ref tag c:\windows\system32\sp2.cab does not exist
1.796: ref tag c:\windows\system32\sp1.cab does not exist
1.796: ref tag c:\windows\system32\driver.cab does not exist
1.796: ref tag c:\windows\system32\fp40ext.cab does not exist
1.796: ref tag c:\windows\system32\fp40ext1.cab does not exist
1.796: ref tag c:\windows\system32\wms4.cab does not exist
1.796: ref tag c:\windows\system32\wms41.cab does not exist
1.796: ref tag c:\windows\system32\ims.cab does not exist
1.796: ref tag c:\windows\system32\ims1.cab does not exist
1.796: ref tag c:\windows\system32\ins.cab does not exist
1.796: ref tag c:\windows\system32\ins1.cab does not exist
1.796: Starting AnalyzeComponents
1.796: AnalyzePhaseZero used 0 ticks
1.796: OEM file scan used 0 ticks
1.890: AnalyzePhaseOne: used 94 ticks
1.890: AnalyzeComponents: Hotpatch analysis disabled; skipping.
1.890: AnalyzeComponents: Hotpatching is disabled.
1.890: FindFirstFile c:\windows\$hf_mig$\*.*
1.953: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.968: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.968: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.968: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.968: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.968: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.968: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.968: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.968: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.968: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.968: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.968: KB905414 Setup encountered an error: The update.ver file is not
correct.
1.984: AnalyzeForBranching used 16 ticks.
2.046: AnalyzePhaseTwo used 62 ticks
2.046: AnalyzePhaseThree used 0 ticks
2.046: AnalyzePhaseFive used 0 ticks
2.046: AnalyzePhaseSix used 0 ticks
2.046: AnalyzeComponents used 250 ticks
2.046: Downloading 0 files
2.046: bPatchMode = TRUE
2.046: Inventory complete: ReturnStatus=0, 281 ticks
2.046: Num Ticks for invent : 281
2.046: [dumpDownloadTask] We have all necessary files for the package to
install. Return STATUS_READY_TO_INSTALL
2.046: dumpDownloadTask returned 0xf201 (ready to install)
2.093: KB905414 installation did not complete.
2.109: Update.exe extended error code = 0xf201
1.187:
================================================== ==============================
1.203: 2005/11/04 14:25:58.670 (local)
1.219:
C:\WINDOWS\SoftwareDistribution\Download\22944015f 08223278b8b5671cbd364c8\update\update.exe (version 6.1.22.4)
1.234: Failed To Enable SE_SHUTDOWN_PRIVILEGE
1.234: Failed To Enable SE_SECURITY_PRIVILEGE
1.234: Setup encountered an error: You do not have permission to update
Windows Server 2003.
Please contact your system administrator.
1.234: You do not have permission to update Windows Server 2003.
Please contact your system administrator.
1.234: Update.exe extended error code = 0xf004
1.172:
================================================== ==============================
1.188: 2005/11/10 08:04:33.113 (local)
1.219:
C:\WINDOWS\SoftwareDistribution\Download\22944015f 08223278b8b5671cbd364c8\update\update.exe (version 6.1.22.4)
1.219: Failed To Enable SE_SHUTDOWN_PRIVILEGE
1.219: Failed To Enable SE_SECURITY_PRIVILEGE
1.219: Setup encountered an error: You do not have permission to update
Windows Server 2003.
Please contact your system administrator.
1.219: You do not have permission to update Windows Server 2003.
Please contact your system administrator.
1.219: Update.exe extended error code = 0xf004
1.141:
================================================== ==============================
1.156: 2005/11/10 08:08:04.054 (local)
1.156:
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\c7c7973bf3758bace159edd33f582d4c\update\update. exe (version 6.1.22.4)
1.156: Hotfix started with following command line: /si
/ParentInfo:0e3c3f804ee67841af05fb152a71457d
1.859: DoInstallation: CleanPFR failed: 0x2
1.859: SetProductTypes: InfProductBuildType=BuildType.IS
1.875: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.891: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB905414$
1.891: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
1.906: ref tag c:\windows\system32\sp4.cab does not exist
1.906: ref tag c:\windows\system32\sp3.cab does not exist
1.906: ref tag c:\windows\system32\sp2.cab does not exist
1.906: ref tag c:\windows\system32\sp1.cab does not exist
1.906: ref tag c:\windows\system32\driver.cab does not exist
1.906: ref tag c:\windows\system32\fp40ext.cab does not exist
1.906: ref tag c:\windows\system32\fp40ext1.cab does not exist
1.906: ref tag c:\windows\system32\wms4.cab does not exist
1.906: ref tag c:\windows\system32\wms41.cab does not exist
1.906: ref tag c:\windows\system32\ims.cab does not exist
1.906: ref tag c:\windows\system32\ims1.cab does not exist
1.906: ref tag c:\windows\system32\ins.cab does not exist
1.906: ref tag c:\windows\system32\ins1.cab does not exist
1.906: Starting AnalyzeComponents
1.906: AnalyzePhaseZero used 0 ticks
1.906: OEM file scan used 0 ticks
2.016: AnalyzePhaseOne: used 110 ticks
2.016: AnalyzeComponents: Hotpatch analysis disabled; skipping.
2.016: AnalyzeComponents: Hotpatching is disabled.
2.016: FindFirstFile c:\windows\$hf_mig$\*.*
2.094: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.094: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.094: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.094: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.109: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.109: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.109: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.109: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.109: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.109: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.109: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.109: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.109: KB905414 Setup encountered an error: The update.ver file is not
correct.
2.109: AnalyzeForBranching used 0 ticks.
2.172: AnalyzePhaseTwo used 63 ticks
2.172: AnalyzePhaseThree used 0 ticks
2.188: AnalyzePhaseFive used 16 ticks
2.188: AnalyzePhaseSix used 0 ticks
2.188: AnalyzeComponents used 282 ticks
2.188: Downloading 0 files
2.188: bPatchMode = TRUE
2.188: Inventory complete: ReturnStatus=0, 297 ticks
2.188: Num Ticks for invent : 297
2.188: [dumpDownloadTask] We have all necessary files for the package to
install. Return STATUS_READY_TO_INSTALL
2.188: dumpDownloadTask returned 0xf201 (ready to install)
2.234: KB905414 installation did not complete.
2.234: Update.exe extended error code = 0xf201

Reply With Quote
  #2  
Old 01-05-2006, 05:03 PM
Robert Aldwinckle
 
Posts: n/a
Default Re: Troubleshoot update failure

"DLS" <DLS@discussions.microsoft.com> wrote in message
news:1E8CDA1E-0C08-43C0-91C4-3CC65E0551F8@microsoft.com...
>I get the following failure log for an update. How do I troubleshoot? I
> reviewed KB906602 and KB902093.
>
> [KB905414.log]

....
================================================== ==============================
> 1.188: 2005/11/10 08:04:33.113 (local)
> 1.219:
> C:\WINDOWS\SoftwareDistribution\Download\22944015f 08223278b8b5671cbd364c8\update\update.exe (version 6.1.22.4)
> 1.219: Failed To Enable SE_SHUTDOWN_PRIVILEGE
> 1.219: Failed To Enable SE_SECURITY_PRIVILEGE
> 1.219: Setup encountered an error: You do not have permission to update
> Windows Server 2003.
> Please contact your system administrator.
> 1.219: You do not have permission to update Windows Server 2003.
> Please contact your system administrator.
> 1.219: Update.exe extended error code = 0xf004
> 1.141:
>

....

Check out KB909444?

(MSN search for
(permission OR permissions) "windows update" site:microsoft.com language:en

Alternatively, you could supplement the log's messages with traces from
FileMon and (if necessary) RegMon. E.g. if the permission problem is
in the file system FileMon may help uncover a more specific symptom;
if the permission problem is in the registry RegMon could help. I suggest
running both though and filtering such that writes to the log are captured
by FileMon. (E.g. use the update's executable name as the filter for both.)
It also helps to use the tools' Options: Clock Time and Show Milleseconds
since that can allow you to correlate information in all three files more easily.


Good luck

Robert Aldwinckle
---


Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Re: failure to install DirectX security update ghanwani@gmail.com Windows Update 4 01-05-2006 05:16 PM
Automatic Updates Windows 2000 Problem Lude Windows Update 16 01-05-2006 05:06 PM
Re: Downloaded files don't install Alias Windows Update 13 01-05-2006 05:05 PM
Re: failure to install DirectX security update Radrick Windows Update 0 01-05-2006 05:03 PM
Windoes update failure Dennis Windows XP Perform Maintain 2 01-05-2006 06:02 AM


All times are GMT. The time now is 07:44 AM.


Powered by vBulletin Version 3.5.2
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd. SEO by vBSEO 2.3.2 © 2005, Crawlability, Inc.

Troubleshoot update failure