[SOLVED] KB5036909 fails continuously with 0x800f081f on Windows Server 2022 Standard

clowg

Active member
Joined
Apr 22, 2024
Posts
33
I have been troubleshooting the failure of this KB to install on one of my W2k22 servers.
I have done the DISM and SFC checks, cleared the WU cache and rebooted.
I tried a In-place install, but it failed:

1713761810151.png

Here are the files you asked for:
 

Attachments

This is still happening every time WU refreshes and tries to install patches again.
 
Do I need to provide more details to get help? What else do you need?
 
This 0x800f081f error has happened again with this months Updates.
I have exhausted all the online searches for fixes for this error. I have read the CBS logs trying to understand what is going wrong but haven't found anything actionable.
What do I have to do to get some help from this forum? It seemed like I had found the exact right place when I discovered your site, but I've had no response after 2 months of waiting.

I have tried the usual recommendations with sfc /scannow and Dism /Online /Cleanup-Image /RestoreHealth and no errors are reported. Even tried the trick of DISM referencing another successfully patched server.
 
I see others are raising similar issues. Can the fixes that are used in those threads be used by others?
 
And now the same failure on July's update.
What am I doing wrong to not even get a single reply on this thread???
 
Hi,

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.
 
Hi,

Download
6530fbb0f4101-56f31e53c97da-SFCFix.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.
650c22f99662d-6190d993a26f3-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.

Afterwards attempt to update and attach a new copy of the CBS when it fails.
 

Attachments

The SFCFix command window included this msg:
"Stage 1 of 6 failed on server"

This error was in the SFCFix log:
"Failed to generate a complete zip file. Upload aborted."

CBS (4) logs attached.
 

Attachments

And 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.
650c22f99662d-6190d993a26f3-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.

Attempt to update again and post the result as well as the latest CBS logs.
 

Attachments

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.
650c22f99662d-6190d993a26f3-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.

Attempt to update again and post the result as well as the latest CBS logs.
 

Attachments

Yes, we'll need to replace multiple components and for the next one I'll need to update my Server 20222 VM.
 
So, what is wrong with the server? What have your fixes been fixing so far? And whats still to go?
I don't understand how this server got into this state months ago.
 
This is a common issue with Server 2022, for now I've replaced all the RTM (slb-mux) components, now I'll need a newer SPP component for your server, and that should be the last fix.
 
Back
Top