Can't install Rollup Update 2

[Redwight]

HMM, thats odd; unless error logging has been disabled. I've been tempted to kill it off but the error logs give me enough information to be usefull occasionally unlike everybodes old favourite the blue screen of death which is worthless.

[Jackal]

Does that mean no one knows what is wrong?

[Redwight]

As another suggestion go to C:\Windows and see if there is a text file called KB891593.log there and see if the errors listed in it make sense.

[ExtremePC]

I have heard from a couple of customers who have encountered an error during setup for Update Rollup 2 for Media Center 2005, and setup then fails with a generic message (which simply states that setup failed). In the cases I have seen so far, one of the prereqisite packages for Update Rollup 2 (a DShow hotfix described by KB891593) failed to install because there was another hotfix installed that updates the same file (another DShow hotfix described by KB904706).

This does not happen on all computers that have KB904706 installed before attempting to install Update Rollup 2, but since it has been seen by multiple people now I wanted to post a workaround here just in case anyone else runs into it.

How do I know if this issue is the one affecting my machine?

You can diagnose this issue by looking at a couple of the log files that Update Rollup 2 setup creates. First, you can open %windir%\mcsetup.log in a text editor such as Notepad. If KB891593 is the package that fails on your system, you will see the following entry in mcsetup.log:

Generic Package: 09/20/05. 09:00:44
Looking for existing install of the generic package
Creating Process: WindowsXP-KB891593-x86.exe /quiet /norestart
Process returned 0x00000643

The 0x00000643 return code (which translates to 1603 in decimal) represents the return code for a generic error in a Windows hotfix package.

Now, you can look at %windir%\kb891593.log to determine the exact reason why this hotfix failed to install. In the cases I have seen so far, the error in kb891593.log looks like the following:

3.437: DoInstallation: Installation was canceled because migration is blocked by following files:
3.437: Package KB904706, File c:\windows\system32\dllcache\quartz.dll, Version 6.5.2600.2749, Branch SP2GDR
3.437: Package KB904706, File c:\windows\system32\quartz.dll, Version 6.5.2600.2749, Branch SP2GDR
3.453: KB891593 Setup encountered an error: Failed to migrate dependent packages.

How can I workaround this issue?

In the cases I have seen so far, uninstalling KB904706 and then attempting to reinstall Update Rollup 2 has proven successful. The following steps can be used to accomplish this:

1. Go to the Control Panel and choose Add or Remove Programs
2. Check the box labeled Show updates in the top middle of the Add or Remove Programs window
3. Locate the section named Windows XP - Software Updates and choose to uninstall the package named Security Update for Windows XP (KB904706)
4. Attempt to install Update Rollup 2 again by returning to Windows Update or running the setup package located

[Jackal]

I found the log it says

[KB891593.log]
4.593: ================================================================================
4.593: 2008/06/22 17:26:12.793 (local)
4.640: g:\f2e4285986e86cabd9eb90\update\update.exe (version 6.1.22.4)
4.640: Hotfix started with following command line: 
4.687: CheckSystem: ServicePack version Mismatch
4.687: DoInstallation: CheckSystem Failed: 0xf06b 
4.703: Setup has detected that the Service Pack version of this system
is newer than the update you are applying.

There is no need to install this update.
12.375: Message displayed to the user: Setup has detected that the Service Pack version of this system
is newer than the update you are applying.

There is no need to install this update.
12.375: User Input: OK
12.375: Update.exe extended error code = 0xf06b
12.375: Update.exe return code was masked to 0x643 for MSI custom action compliance.
5.703: ================================================================================
5.703: 2008/06/22 18:08:46.562 (local)
5.766: g:\4467723d68bcc74d93fc430b32\update\update.exe (version 6.1.22.4)
5.766: Hotfix started with following command line: 
9.547: In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed with error 0x2
9.547: In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed with error 0x2
9.547: ---- Old Information In The Registry ------
9.547: Source:C:\Config.Msi\63fb5.rbf (9.0.1407.1107)
9.547: Destination: 
9.547: ---- New Information In The Registry ------
9.547: Source:C:\Config.Msi\63fb5.rbf (9.0.1407.1107)
9.547: Destination: 
9.609: SetProductTypes: InfProductBuildType=BuildType.IP
9.641: SetAltOsLoaderPath: No section uses DirId 65701; done.
9.844: DoInstallation: FetchSourceURL for g:\4467723d68bcc74d93fc430b32\update\update_SP2QFE.inf failed
9.875: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
9.891: BuildCabinetManifest: update.url absent
9.891: Starting AnalyzeComponents
9.891: AnalyzePhaseZero used 0 ticks
9.891: No c:\windows\INF\updtblk.inf file.
9.891: OEM file scan used 0 ticks
10.359: AnalyzePhaseOne: used 468 ticks
10.359: AnalyzeComponents: Hotpatch analysis disabled; skipping.
10.359: AnalyzeComponents: Hotpatching is disabled.
10.359: FindFirstFile c:\windows\$hf_mig$\*.*
11.422: CreateUninstall = 0,Directory = C:\WINDOWS\$NtUninstallKB891593$ 
13.250: AnalyzeForBranching used 141 ticks.
13.281: AnalyzePhaseTwo used 31 ticks
13.281: AnalyzePhaseThree used 0 ticks
13.281: AnalyzePhaseFive used 0 ticks
13.797: AnalyzePhaseSix used 516 ticks
13.797: AnalyzeComponents used 3906 ticks
13.797: Downloading 0 files
13.797: bPatchMode = FALSE
13.797: Inventory complete: ReturnStatus=0, 3953 ticks
13.797: Num Ticks for invent : 3953
14.031: VerifySize: Unable to verify size: Source = NULL: c:\windows\inf\HFX51.tmp 
14.172: Copied file:  c:\windows\inf\branches.inf
43.391: Allocation size of drive C: is 4096 bytes, free space = 17613193216 bytes
43.391: Drive C: free 16797MB req: 5MB w/uninstall 0MB
43.391: CabinetBuild complete
43.391: Num Ticks for Cabinet build : 29594
43.391: DynamicStrings section not defined or empty.
43.391: FileInUse:: need to restart already, turn off
44.406: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
57.547: System Restore Point set.
57.594: Copied file:  C:\WINDOWS\system32\spmsg.dll
57.641: PFE2: Not avoiding Per File Exceptions.
57.984: GetCatVersion:  Failed to retrieve version information from C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\KB891593.cat with error 0x80092004
58.141: DoInstallation: Installing assemblies with source root path: g:\4467723d68bcc74d93fc430b32\
58.141: Num Ticks for Copying files : 14750
58.156: Num Ticks for Reg update and deleting 0 size files : 15	
58.156: DoInstallation: ApplyAdminSystemAclsRecursive for c:\windows\$hf_mig$\KB891593 failed; error=0x00000003
58.156: ---- Old Information In The Registry ------
58.156: Source:C:\Config.Msi\63fb5.rbf (9.0.1407.1107)
58.156: Destination: 
58.156: ---- New Information In The Registry ------
58.156: Source:C:\Config.Msi\63fb5.rbf (9.0.1407.1107)
58.156: Destination: 
58.156: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is empty; nothing to do.
62.016: RebootNecessary = 0,WizardInput = 0 , DontReboot = 1, ForceRestart = 0

What does that mean?

[Jackal]

I fixed it. I unistalled SP3 and then installed all the updates from windows update. No idea what the problem was but it now works. Thanks for the help.

[Redwight]

Sorry about missing that log post but the answer is in there,

4.687: DoInstallation: CheckSystem Failed: 0xf06b
4.703: Setup has detected that the Service Pack version of this system
is newer than the update you are applying.

There is no need to install this update.
12.375: Message displayed to the user: Setup has detected that the Service Pack version of this system
is newer than the update you are applying.

The update reasons that if the newer version is better then don't bother with the old one. The problem you have had however is that another patch (SP2) was looking for a must have this flag in the registry. It's a failing of microsoft's that comes up from time to time, in that the new patch should also kick the same trigger to make your life easier but doesn't.
On to better news glad you have sorted it out.