Windows Update issue 0x80073701 (2025-05) on Windows Server 2022

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

Attachments

Here's the next fix for multiple components / LP's.

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

Attachments

Please run the following DISM command, it will complete but we'll need to remove some warnings as it seems. So please provide the new CBS logs.
Code: 
DISM /online /cleanup-image /RestoreHealth
 
Hi,

Step 1.
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.
650ef5dbdfd06-62151e1bebac4-SFCFix-Txt-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 a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Hi, thank you for your time.
Are you uploaded the correct file? You write about SFCFixScript.txt, but its fixlist.txt.
Done.
CBS: CBS.zip
 

Attachments

Hi,

Oops, I've posted the wrong canned for the Fixlist it should be:

Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST64.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 
And it's not even a Monday.... 🤦‍♂️

Please run DISM again and provide the CBS logs to see if all the warnings are fixed now.
 
The result of DISM looks good now, no warnings:

Rich (BB code): 
2025-06-07 13:26:31, Info                  CBS    =================================
2025-06-07 13:26:31, Info                  CBS    Checking System Update Readiness.
2025-06-07 13:26:31, Info                  CBS   
2025-06-07 13:26:31, Info                  CBS   
2025-06-07 13:26:31, Info                  CBS    Summary:
2025-06-07 13:26:31, Info                  CBS    Operation: Detect and Repair
2025-06-07 13:26:31, Info                  CBS    Operation result: 0x0
2025-06-07 13:26:31, Info                  CBS    Last Successful Step: Remove staged packages completes.
2025-06-07 13:26:31, Info                  CBS    Total Detected Corruption:    0

Please attempt to update again with Process Monitor running.

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. Stop Process Monitor as soon as it fails. You can simply do this by clicking the capture icon (CTRL +E) on the toolbar as shown below.

67c2dd018fcab-Process-Monitor.png


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 Fast and provide the link.
6. Upload also the latest CBS log for the time stamps.
 
I did. I came back later and procmon wasnt running.
So I did again and watched the process and I procmon crashes with error "out of memory" (screen.png).
But update fails with error 0x800f0831.
CBS: CBS.zip
 

Attachments

  • screen.webp
    screen.webp
    162.3 KB · Views: 3
How many free space is available on the system drive and how many memory is installed/assigned for this server?
 
The system has 25 GB free space from 80 GB.
Server has configured 10GB memory (its a virtual machine). Only 35% memory is used at this time.
 
25 GB should be enough, but let's check if we can free up some more space. So please post the result of the following command.
Code: 
DISM /online /cleanup-image /AnalyzeComponentStore
 
Result.
But its no problem to extend the space if needed.

Code: 
Deployment Image Servicing and Management tool
Version: 10.0.20348.2849

Image Version: 10.0.20348.3453

[==========================100.0%==========================]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 10.42 GB

Actual Size of Component Store : 10.09 GB

    Shared with Windows : 6.42 GB
    Backups and Disabled Features : 3.66 GB
    Cache and Temporary Data :  0 bytes

Date of Last Cleanup : 2025-06-07 14:58:19

Number of Reclaimable Packages : 0
Component Store Cleanup Recommended : No

The operation completed successfully.
 
Ok, I extend the space, there is 45GB.
I run update and procmon crashed again.
 
You must log in or register to reply here.

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

Back
Top