[SOLVED] Cumulative updates keep failing on new Windows Server 2022 installation

[mpb88]

Hi there,

Hope you can help me out. We installed a new Windows Server 2022 Standard VM a few months ago, and updates started failing.
This happens only to cumulative updates, two months in a row now (june and july).

It is now failing on KB5028171 with error code 0x800f0905.

I already tried:
- How to fix Windows server 2022 cumulative update problem? Error, 0x800f0905 - Microsoft Q&A
- error windows update 0x800f0905 - Microsoft Q&A
- Additional resources for Windows Update - Windows Client
- Rebooting
- Manual install
- Disabling AV (default Windows Defender)
- SFC / DISM repair commands run fine and report no errors / things being fixed.

Attached is the result of Powershell command get-windowsupdatelog.

Also I ran sfcfix.exe, but it reports no errors:

AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.

Please advise! This server is a domain controller etc etc so reinstalling is not an option.

Greets M

 

[Maxstar]

Hi and welcome to Sysnative,

Step 1. Run the following DISM command and post the result, and attach the DISM.log (%WinDir%\Logs\DISM).

DISM /Online /Get-CurrentEdition

Step 2. Upload a copy of the CBS folder

• Open Windows Explorer and browse to the C:\Windows\Logs folder.
• Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
• Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
• Click on the Yes button here.

• Attach the file CBS.zip to your next reply.

Step 3. Export CBS (Component Based Servicing) hive

• Click on the Start button and type regedit
• When you see regedit on the list, right-click on it and select Run as administrator.
• When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
  

  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing

• Once selected, click File > Export....
• Change the Save as type: to Registry Hive Files (*.*).
  
  
  
  
  
• Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
• Right-click on the saved file and choose Send > Compressed (zipped) Folder.
• Attach the .ZIP file to your next post.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[mpb88]

Hi Maxstar,

Thanks for your reply.

I just tried to install the cumulative update for august 2023, same error:

2023-08 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5029250)
Download error - 0x800f0905

Result of the DISM command:

Deployment Image Servicing and Management tool
Version: 10.0.20348.681

Image Version: 10.0.20348.1726

Current edition is:

Current Edition : ServerStandard

The operation completed successfully.

Please see the requested files attached.

 

[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 reboot the server and attempt to update again. If it fails attach a new copy of the CBS logs.

 

[mpb88]

Hi Maxstar,

Thanks for the quick reply.
Please find SFCFix.txt attached.

This is an production server, can't reboot it now.
Will try to do so tonight.

Greets.

 

[Maxstar]

That's fine let me know the result after the reboot.

 

[mpb88]

Hi Maxstar,

I just rebooted the server and tried installing updates again. I'm sorry, still getting the same error 0x800f0905.

Please find logs attached.

Greets.

 

[Maxstar]

Hi,

Please attempt to update again with Process Monitor running, attach this this trace including a new copy of the CBS file to your next post.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Please wait 30 seconds and then Stop Process Monitor. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.



4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.

 

[mpb88]

Hi MaxStar,

Please find the log at WeTransfer

Greets M

 

[Maxstar]

Hi,

Hmmm, could you please run Process Monitor again while updating and then wait a minute before stopping the trace.

 

[mpb88]

Hi MaxStar,

Please see new attached logs through this link.

Some timestamps (accurate to a few seconds):
13:27:15 - Started Procmon capture
13:27:20 - Started the update installation command
13:27:30 - Windows Update started downloading the patch
13:27:52 - Windows Update started installing the patch
13:28:08 - Install status went to 20% and kept hanging there
13:33:18 - Install status went to 100%
13:34:31 - Error code 0x800f0905 was shown
+90 seconds - Kept Procmon running extra long

Greets M

 

[Maxstar]

Hi,

Run the following DISM command again and post the result, attach also a copy of the DISM.log (%WinDir%\Logs\DISM).

DISM /Online /Get-CurrentEdition

 

[mpb88]

Hi Maxstar,

Sure, here it is.

C:\Windows\system32>DISM /Online /Get-CurrentEdition

Deployment Image Servicing and Management tool
Version: 10.0.20348.681

Image Version: 10.0.20348.1726

Current edition is:

Current Edition : ServerStandard

The operation completed successfully.

 

[Maxstar]

Hi,

Please try the following steps to reactivate this server: Key Management Services (KMS) client activation and product keys for Windows Server and Windows
Open an elevated command prompt and copy / paste the following command and press enter.

Dism /online /Set-Edition:ServerStandard /ProductKey:VDYBN-27WPP-V4HQT-9VMD4-VMK7H /AcceptEula

Reboot the server and reactivate this system using your own product key.

slmgr /ipk ABCDE-FGHIJ-KLMNO-PQRST-UVWXY  
slmgr /ato

 

[mpb88]

Hi Maxstar,

I am sorry, that also did not work. Please find new Procmon and CBS logs here.

What I did:
- Reboot
- Changed code with your DISM command
- Reboot
- Changed code with your slmgr command with the correct key owned by customer
- Reboot
- Checked Windows activation status, OK
- Tried updating
- Same error. Installation hangs at 20% for a while, then pops to 100% for a while, then gives the error.

 

[Maxstar]

Hi,

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 SFCFixScript.txt and save it to your desktop.
• Drag the SFCFixScript.txt 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 again with Process Monitor running. If it fails attach a new copy of the CBS logs and the *.PML file.

 

[mpb88]

Hi,

Do I need to reboot for this to work?

 

[Maxstar]

Hi,

You could try to update without a reboot first to see what happens.

 

[mpb88]

I am sorry, it still fails. :-(

Although... the error code changed: It's now reporting 0x800700ea
Did not reboot yet, can't do that during working hours.

Please find requested logs here and in the attachment.

 

[mpb88]

Just did a reboot and tried again. Got 0x800700ea again.
Still goes to 20% then snaps to 100% then fails.
On the positive side, something changed, the error code. Could be a good sign.