[SOLVED] Windows Server 2022 21H2 - Update error 0x8024200B when installing CU

[Kinglearjet]

Hi, really hoping you can help with this one.

This server has not been installing any OS CU's every month, either via SCCM or manully, however .net and definition updates install no problem. We have tried all the usual fixes, SFC, DISM, renamed the software distribution folder, catroot folder etc but all fail. I have tried installing older CU's and the latest February CU but they all fail to install.

Thanks in advance.

 

[Kinglearjet]

Bump

 

[Maxstar]

Hi and welcome to Sysnative,

Upload your COMPONENTS hive.

• Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
• Please copy this file to your desktop.
• Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
• Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[Kinglearjet]

Hi Maxstar. Thanks for replying!

Attached is the zipped Components file as requested.

 

[Maxstar]

Hi,

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 SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip 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.

Afterwards attempt to update and post the result. If it fails attach a new copy of the CBS logs.

 

[Kinglearjet]

Attached is the SFCFix.txt file. I then attempted to update the server and the updates failed again with the same error code, 0x8024200B.

Here is a WeTransfer link to the latest CBS Logs CBS.zip

 

[Maxstar]

Here's the next fix.

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 SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip 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.

Afterwards attempt to update and post the result. If it fails attach a new copy of the CBS logs.

 

[Kinglearjet]

Attached is the latest SFCFix.txt file. I then again attempted to update the server and the updates failed again with the same error code, 0x8024200B.

Here is a WeTransfer link to the latest CBS Logs CBS.zip

 

[Maxstar]

Here's the next fix for another corrupt component.

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 SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip 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.

Afterwards attempt to update and post the result. If it fails attach a new copy of the CBS logs.

 

[Kinglearjet]

@Maxstar we've made some progress so thank you for your help so far. The server doesn't think it has any new updates available when checking in with SCCM or directly from Microsoft, however I was able to manually install Septembers server CU successfully without error. We do know its not up to date so at least its now a different issue.

 

[Maxstar]

Great, I would suggest to reboot this server when possible and then attempt to update again to see which updates are offered.

 

[Kinglearjet]

Thanks for all your help so far. Out of interest, what components were corrupted? I'll report back tomorrow if the restart has been a success. SCCM will also continue to try to update the server overnight, so fingers crossed it will finally succeed.

 

[Maxstar]

You're welcome and glad we make some progress so far in fixing this server. To see which components (registry keys / payload files) were corrupted/missing you can take a look inside the provided ZIP-files. Some general info on how such fixes are created can be found in this tutorial: Troubleshooting 0x800f081f / 0x800f0982 Error

 

[Kinglearjet]

Maxstar. Server is all sorted. Thanks for your help. You saved us a migration of a key service to another server so we are extremely grateful.

 

[Maxstar]

Hi,

You're welcome. Glad to hear this server is up-and-running again...
I will mark this thread as solved.