[SOLVED] Microsoft Windows Server 2022 - Updates are failing with error code 0x800f081f but are reporting successful

N

nva1986

Member
Joined
Aug 15, 2024
Posts
14
Hello everybody,

I've got an extremely weird issue with a Microsoft Windows Server 2022 installation. Ever since after the June 2024 update, the Microsoft Windows Cumulative updates keep failing (the .NET Framework updates seem to be working without a problem) Whenever I run Microsoft Windows Update, it states it's installing the update. The update takes approximately 20 - 30 seconds to complete, no reboot and reports it was successfully installed. Whenever I reboot and try to run Microsoft Windows Update again however, it simply starts installing the update again. Whenever I do this with Microsoft Windows Update it usually just hangs indefinitely or throws error code "0x800f081f". If I install the update manually it states it failed to install the update, but doesn't show any error in the "View update history" section of "Windows Update". This is 1 VM out of 16 VM's throwing this error.

Things I've tried so far:

- Various reboots
- sfc /scannow (reports all is clean)
- dism /online /scanhealth (reports all is clean)
- dism /online /checkhealth (reports all is clean)
- dism /online /restorehealth (reports all is clean)
- Running ComponentsScanner.exe - (The first run was all clean, the second run threw a minor weird warning, but nothing was fixed)
- Running sfcfix.exe (reports all is clean)
- Installing the update from the Microsoft Update Catalog
- Running the troubleshooting assistant
- Re-installed / updated VMware Tools update
- Removed the recovery partition (which is known to me to cause certain issues with certain updates)
- Cleaning the SoftwareDistribution folder

Could somebody give some advice or help me with matter?
Please see the attached log files. If further logging is required, then please don't hesitate to contact me / ask me.
 

Attachments

In order to give a better understanding (to avoid confusion) this is what Windows Update does. It says installed successfully within 30 seconds and does not ask for a reboot (the update is not installed of course). When you run the update manually or try again after, it shows the error (which is the latest top entry)
 

Attachments

  • Screenshot_20240815_094510.png
    Screenshot_20240815_094510.png
    27.5 KB · Views: 4
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.
 
Hi,

Here's the first fix.

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 again, if it fails attach a new copy of the CBS logs.
 

Attachments

Maxstar,

Thank you for the fast response. The SFCFix.txt as per your request. The update is running now. I will check back in 20 - 30 minutes to see if it finished successfully and I'll get back to you.
 

Attachments

You're welcome. However, the update will fail again because we'll need to replace a number of components in cases like this.
 
You were right about the fact that the update failed again. Here's a new copy of the CBS folder.
 

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.

Afterwards attempt to update again, if it fails attach a new copy of the 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.

Afterwards attempt to update again, if it fails attach a new copy of the CBS logs.
 

Attachments

There's slight progress. The update continues to 78% instead of 44%, but unfortunately the update failed again. Here's the renewed CBS log file
 

Attachments

Now the update failed with error 0x800f0982, so 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.

Afterwards attempt to update again, if it fails attach a new copy of the CBS logs.
 

Attachments

The renewed SFCFix.txt as per your request. The update is installing again, awaiting the result.
 

Attachments

The issues has been resolved. The update installed successfully and was able to reboot the system and it reports that there's no more available updates and that the update is installed. Thank you for your help. Is there any way that I can troubleshoot these log file myself? Is there any particular tooling that you're using to quickly analyze these log files for issues?
 
You must log in or register to reply here.
Back
Top