[SOLVED] Windows Server 2019 - Failing to install KB5055519 - 0x800F0985

Mark_S

Member
Joined
May 2, 2025
Posts
5
Hi, been having an issue installing CU on 1 server for a few months now, getting error 0x800f0954.

Have tried SFC (no corruption found) and DISM which is failing (including using a mounted ISO of the installation media as a source). DISM seems to be failing to find certain packages (0x800f0954 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT_WSUS), hence trying to specify the installation media as a source but still get an error about them, albeit slightly different (0x800f081f - CBS_E_SOURCE_MISSING)

I've attached CBS logs and ComponentScanner log.

Any help would be greatly appreciated.
 

Attachments

Hi @Mark_S,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team
 
Realised I cleared out the CBS logs which were missing the failed attempt to install the update. They're now attached to this reply.
 

Attachments

Hi and welcome to Sysnative,

Please don't remove logs...

Step 1. Download
67139f7e69a58-SFCFix-ico.PNG
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.
67139f52b3c1e-SFCFix-Zip-Eng.gif

  • 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.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Hi and welcome to Sysnative,

Please don't remove logs...

Step 1. Download
67139f7e69a58-SFCFix-ico.PNG
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.
67139f52b3c1e-SFCFix-Zip-Eng.gif

  • 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.
Code:
DISM /online /cleanup-image /RestoreHealth
Thank you, this worked perfectly. The DISM completed successfully and the Windows update successfully applied.

I have 2 other servers which seem to have similar issues, but with different corrupted payloads. Would it be best to create new thread for each individually? I couldn't see anything about the rules regarding this in the posting instructions.
 
Hi,

You're welcome. Gad to hear the issue has been resolved... (y)

Please start a new thread for the other servers just to avoid any confusions.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top