[SOLVED] Windows Server 2019 unable to install cumulative updates - CBS error 0x8007000d

[porffor]

All files are here: Sysnative - Google Drive

I have a Windows Server 2019 Standard (17763.5696) machine where cumulative updates (i.e. 'Security Update for Microsoft Windows) have been failing since April. Other update types like 'Update for Microsoft Windows' and 'Servicing Stack' install fine. It's had many reboots in this time.

Trying to manually install the .msu file fails to install. The windowsupdate.log file (attached) says "CBS called Error with 0x8007000d".

The CBS.log file (attached) says:

Failed to initialize package: Microsoft-Windows-NetFx4-OC-Package~31bf3856ad364e35~amd64~~10.0.17763.1, from path: \\?\C:\WINDOWS\Servicing\Packages\Microsoft-Windows-NetFx4-OC-Package~31bf3856ad364e35~amd64~~10.0.17763.1.mum, existing package: 1 [HRESULT = 0x8007000d - ERROR_INVALID_DATA]

So I tried copying the .cat and .mum files from a known good machine of the same Windows version (just guessing at this point, to be honest) but that didn't make a difference to the above error or to the overall outcome.

Running 'DISM /Online /Cleanup-Image /RestoreHealth' comes out clean, as does 'sfc /scannow'.

Running 'DISM /Online /Cleanup-Image /AnalyzeComponentStore' gives "Error 13. The data is invalid". The dism.log is attached.

The ComponentScanner report is attached.

I ran the standard SFCFix downloaded from your site. After running DISM in Stage 3, it stayed there for a good few hours, where it looked in Task Manager like there was nothing happening - see screenshot. I saw a thread here where someone said that you just press Enter to get past that. So I did that a couple of times, but the results screen showed only the 3 stages. No corruptions were found. Text output attached.

Zipped COMPONENTS file is attached.

Any help would be appreciated.

 

[Maxstar]

Hi,

Export CBS (Component Based Servicing) hive

• Click on the Start button and type regedit
• When you see regedit on the list, right-click on it and select Run as administrator.
• When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
  

  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing

• Once selected, click File > Export....
• Change the Save as type: to Registry Hive Files (*.*).
  
  
  
  
  
• Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
• Right-click on the saved file and choose Send > Compressed (zipped) Folder.
• Attach the .ZIP file to your next post.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[porffor]

Hi, I've now added the zipped registry hive to the above Google Drive folder.

I also noticed that I'd originally forgotten to add the zipped COMPONENTS file, so I've done that now too.

Thanks!

 

[Maxstar]

Hi,

Step 1. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFixScript.txt and save it to your desktop.
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[porffor]

Hello,

There was one error in the SFCFix.txt - attached.

The DISM command came out clean.

Thank you.

 

[porffor]

However, I've just tried the cumulative update again now, and it's working now!!

Many thanks for your help. Excellent work!

 

[Maxstar]

Hi,

You're welcome. Glad to hear the latest update installed without any issues this time..
I will mark this thread as solved.

 

[porffor]

Hi,

Just for my understanding, I noticed that the fix removed a reg key and recreated it with new reg values. Could you explain how you knew what those reg values were supposed to be?

 

[Maxstar]

Hi,

Yes, I removed the complete key because it contained corrupt values which were only visible in Registry Explorer. So I've only readd the good values.

"¸P}êt†É°5-AiÑJÞü-”exm{nÉL2EÝV[C[s¥W«cÒÔES…p C¯a¢e?3ñb?35aŒ3 4o3Ž~«mŒÙ4~~10.0.17763.1"=
"Microsoft-Windows-NetFx4ëoc
Pack~ï){1bf3856ad364e35~amd64~en-US~10.0.17€¿1"=dword:00000002

 

[porffor]

Ah I see, so the re-added values are the same ones as were there before, but doing it this way gets rid of the corrupt data? Did I understand it right?

 

[Maxstar]

Regedit wasn't able to read those values, so I've used an offline registry editor to export the corrupted key and removed the corrupt values which I couldn't rebuild. And glad it worked without any further issues.

 

[porffor]

Great, thank you for the explanation too.

 

[Maxstar]

You're welcome..