Window update error 0x800f0985

[OCC]

Hi,
We've been having some issues with a windows server.
024-12 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5048661) can not be installed.
Error code 0x800f0985.

We've ran sfc /scannow, Dism /Online /Cleanup-Image /RestoreHealth and component scanner.

 

[OCC]

Here are the logs :)

 

[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.

 

[OCC]

Hi,
Here is the components hive.

Thank you.

 

[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. If it fails attach a new copy of the CBS logs.

 

[OCC]

Here is the .txt.
Will try updating and get back

 

[OCC]

Hi again Maxstar!
It looks like the fix worked. You're a life saver
Since the original server is in production environment, this was performed on a clone. The clone itself was outside the domain and on a different network. Can above fix be used safely on the original server or is it better to post a new post?

Once again, thank you!

 

[Maxstar]

Hi,

You're welcome. And when you've cloned the server 1:1 you can use the same fix on the production server, but make always a full backup / snapshot, just be sure you can rollback the system to the previous state!