[SOLVED] Server 2008 R2 SP1 "CBS called Error with 0x80004005"

[adamcook]

CBS called Error with 0x80004005 in WindowsUpdate.log

Trying to install KB4489878 (2019-03) or KB4103718 (2018-05) I get the below in WindowsUpdate.log on a Windows Server 2008 R2 SP1 server:

2019-04-01    16:09:20:595     800    544    Handler    Installing self-contained with source=C:\Windows\SoftwareDistribution\Download\98fb16fa475dbcd684e862b511a27970\Windows6.1-KB4489878-x64.cab, workingdir=C:\Windows\SoftwareDistribution\Download\98fb16fa475dbcd684e862b511a27970\inst

2019-04-01    16:09:25:197     916    13ec    Report    REPORT EVENT: {B1AC6675-E37B-4A5D-833F-C0C8758229C1}    2019-04-01 16:09:20:168+0200    1    181    101    {00B91A79-94CE-4E82-BA5F-5E8CE88C0F64}    501    0    wusa    Success    Content Install    Installation Started: Windows successfully started the following update: Security Update for Windows (KB4489878)

2019-04-01    16:11:06:032     800    cdc    Handler    FATAL: CBS called Error with 0x80004005,

2019-04-01    16:11:13:251     800    544    Handler    FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x80004005

Attached is WindowsUpdate.log from trying to install 2019-04 rollup.

sfc /scannow: "Windows Resource Protection did not find any integrity violations."

kb947821: installed ok but same result for both updates when trying to install.

Below is result of SFCFix when I tried to install 2019-03 rollup last month:

SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-04-01 17:13:54.762
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
   CBS & SFC total detected corruption count:     0
   CBS & SFC total unimportant corruption count:  0
   CBS & SFC total fixed corruption count:        0
   SURT total detected corruption count:          6
   SURT total unimportant corruption count:       0
   SURT total fixed corruption count:             0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2019-04-01 17:18:02.296
----------------------EOF-----------------------

Attached are CBS logs from my attempt of 2019-04. Interestingly, having just reran SFCFIX, it suggested there were 0 "SURT total detected corruption", whereas there were 6 a couple of weeks ago when I tried 2019-03 rollup.

I tried the below script (without a reboot inbetween running + retry) but no success:

winadminsdotorg/SystemCenterConfigMgr

 

[Sysnative Windows Update]

Hello and welcome!

FRST Registry Search
1. Click your Start button and choose Control Panel.
2. In the upper right corner ensure the View by: is set to Category.
3. Select the Programs group.
4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog. Wait until this dialog populates with information. If this does not happen for some reason, please continue with the steps anyway.
Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps.
5. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
7. Copy and paste KB4088875 into the Search box and click the Search Registry button.
8. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
9. You may close any remaining open windows now.

 

[adamcook]

Hello and welcome!

FRST Registry Search
1. Click your Start button and choose Control Panel.
2. In the upper right corner ensure the View by: is set to Category.
3. Select the Programs group.
4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog. Wait until this dialog populates with information. If this does not happen for some reason, please continue with the steps anyway.
Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps.
5. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
7. Copy and paste KB4088875 into the Search box and click the Search Registry button.
8. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
9. You may close any remaining open windows now.

Hello!

Thank you for your reply. I hope the attached is OK!

 

[Sysnative Windows Update]

Sure!

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Try updates and if any fail, attach CBS.log.

 

[adamcook]

Sure!

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Try updates and if any fail, attach CBS.log.

It installed! Thank you so much.

I knew there wasn't anything fundamentally wrong with WUA or anything like that because over the last year, .NET and IE updates have installed no issues. Even for testing the Previews and Security Only updates have installed too. I had a hunch it was something about the KB4088875 2018-03 rollup.

I'm going to be asked what the root cause was, and what specifically about deleting the registry keys in fixlist.txt that helped solve the issue. Perhaps you could summarise this to me? I'd love to become more independent with this.

 

[Sysnative Windows Update]

Sure. The system had some partially installed components of an incorrectly installed update in the registry, so instead of targeting them one by one, I just scanned the system for the remnants, targeted the whole update and ripped it right out. :)

 

[adamcook]

Sure. The system had some partially installed components of an incorrectly installed update in the registry, so instead of targeting them one by one, I just scanned the system for the remnants, targeted the whole update and ripped it right out. :)

Thank you for your time. Incredibly valuable.