Updates Fail to install

[gbjordan]

I'm having a number issues with my sbs 2008 domain controller but I will start with the windows update problem first.

 

I am unable to install Windows updates. A week after deployment I received the dreaded, installing update 3 of 3 lock up. I applied a Microsoft hotfix and was free of that issue. Since then I have been unable to install any updates. At one point yesterday I was given an 0x8000FFFF error within Windows updates. I rebooted (Which takes 25 minutes due to services failing to stop or start) and then went back in to Windows update. I was advised that there were 4 updates to install. I click start installation and walked away. I come back 20 minutes later to windows update stating "Preparing to Install..." I check back 4 hrs later only to see the same thing. I left it running over night only to come in and see the same "Prepating to Install..."

on my display.

 

If there is any additional information I can give you to help let me know. Below I have pasted an excerpt from the windows update log file which once again brings up that 8000FFFF error

code.

Thanks in Advance

 

2010-03-23 13:24:15:003 324 1908 Setup SelfUpdate handler update NOT required: Current version: 7.1.6001.65, required version: 7.1.6001.65

2010-03-23 13:24:15:003 324 1908 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.1.6001.65"

2010-03-23 13:24:19:746 324 1908 Handler FATAL: UH: 0x8000ffff: EvaluateApplicability failed in CCbs::EvaluateApplicability

2010-03-23 13:24:19:746 324 1908 Setup WARNING: CBS EvaluateApplicability returned error, error = 0x8000FFFF

2010-03-23 13:24:19:746 324 1908 Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.1.6001.65" failed, error = 0x8000FFFF

2010-03-23 13:24:19:746 324 1908 Setup FATAL: SelfUpdate check failed, err = 0x8000FFFF

2010-03-23 13:24:19:746 324 1908 Agent * WARNING: Skipping scan, self-update check returned 0x8000FFFF

2010-03-23 13:24:20:432 324 1908 Agent * WARNING: Exit code = 0x8000FFFF

2010-03-23 13:24:20:432 324 1908 Agent *********

2010-03-23 13:24:20:432 324 1908 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]

2010-03-23 13:24:20:432 324 1908 Agent *************

2010-03-23 13:24:20:432 324 1908 Agent WARNING: WU client failed Searching for update with error 0x8000ffff

2010-03-23 13:24:20:432 324 1a00 AU >>## RESUMED ## AU: Search for updates [CallId = {8ABFD32D-57F4-43A9-82FD-CC76525F3DA8}]

2010-03-23 13:24:20:432 324 1a00 AU # WARNING: Search callback failed, result = 0x8000FFFF

2010-03-23 13:24:20:432 324 1a00 AU # WARNING: Failed to find updates with error code 8000FFFF

2010-03-23 13:24:20:432 324 1a00 AU #########

2010-03-23 13:24:20:432 324 1a00 AU ## END ## AU: Search for updates [CallId = {8ABFD32D-57F4-43A9-82FD-CC76525F3DA8}]

2010-03-23 13:24:20:432 324 1a00 AU #############

2010-03-23 13:24:20:432 324 1a00 AU Need to show Unable to Detect notification

2010-03-23 13:24:20:432 324 1a00 AU AU setting next detection timeout to 2010-03-23 18:14:56

2010-03-23 13:24:24:753 324 1908 Report REPORT EVENT: {2D50AC2E-5FC8-4B7D-82D1-2C4290C6D57D} 2010-03-23 13:24:19:746-0400 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.

2010-03-23 13:30:23:446 324 1908 Report Uploading 3 events using cached cookie, reporting URL = http://:8530/ReportingWebService/ReportingWebService.asmx

2010-03-23 13:30:23:446 324 1908 Report Reporter successfully uploaded 3 events.

[gbjordan]

Forgot to add, Server standard SP2

[anyweb]

where's it getting the updates from ? windowsupdate or wsus or sccm ?

[gbjordan]

Windows update but I finally found a solution. A prior update had failed which caused a corrupted registry entry. Look in HKLM\COMPONENTS and if you have the following 3 entries, delete them

 

PendingXmldentifier 
NextQueueEntryIndex 
AdvancedInstallersNeedResolving

[anyweb]

nice find, thanks for sharing

 

cheers

niall

[Phylum]

Windows update but I finally found a solution. A prior update had failed which caused a corrupted registry entry. Look in HKLM\COMPONENTS and if you have the following 3 entries, delete them

 

PendingXmldentifier 
NextQueueEntryIndex 
AdvancedInstallersNeedResolving

 

Agreed - nice find and we do appreciate you sharing!

 

I do have some questions if you can recall any details at this point:

1. What was the troubleshooting process that led you there?
2. What update(s) failed?
3. What process is responsible for writing out those keys: The updates themselves? Windows Update Agent? Windows?
4. Do all three keys need to be present for this condition (problem) to exist, or is it any combination of one or more?

Thanks!