Windows Update Error 0x80073712 on 4 of my Windows Server 2025 PC's

Question

Windows Update Error 0x80073712 on 4 of my Windows Server 2025 PC's

Justin Matthews 20

I upgraded 60 servers in my environment from Windows Server 2022 to Windows Server 2025 back in March. Four of those servers have given Windows Update Error 0x80073712 on each monthly security update ever since. I have tried running all of the recommended troubleshooting steps (sfc /scannow, DISM, resetting the Windows Update services, renaming the SoftwareDistribution and catroot2 folders) multiple times. I also tried an in-place upgrade. Nothing works. I am trying to avoid a clean new install and having to reinstall all of my applications on each of these servers. I tried to open a purchase a support plan, but my MS business account says I need to open the case with a personal login and my personal account says I need to open a case with a business login. I'm about to just call a Microsoft number to open a case, but figured I'd try this Q/A forum first. Any assistance would be greatly appreciated.

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Answer 1

The following steps end up working for me after opening a case with Microsoft.....

Dism /Online /Cleanup-Image /RestoreHealth /Source:\W.X.Y.Z\C$\windows /LimitAccess - (W.X.Y.Z = IP address of a working Windows VM with no issues) to replace any corrupt windows files from a valid source.
Delete the folder C:$WINDOWS.~BT if it is present.
Open msconfig and perform a clean boot by disabling all non-Microsoft services, leaving only VMware services enabled.
Restart the server.
After the reboot, verify that the third-party services remain disabled and stop any SQL-related services again if SQL is installed (no need to change SQL services Startup Type to Disabled).
Mount the Windows Server 2025 ISO. I actually got the latest Windows Server ISO with the most recent cumulative updates added (June 2026) from my M365 Account.
Launch the in-place upgrade from an elevated Command Prompt using command: setup.exe /auto upgrade /dynamicupdate disable /compat ignorewarning

Install completed normally and all of the Windows Updates were already installed.

Answer 2

Scott Nguyen 1,965 Independent Advisor

Hi Justin, error 0x80073712 means some assembly files in the WinSxS folder has missing or corrupted package manifests that standard DISM commands cannot automatically resolve. To see the exact failure, open %windir%\Logs\CBS\CBS.log and search for lines containing Failed to resolve execution or error code 0x80073712 to identify the specific missing package identities. You can repair these corruptions by leveraging one of your 56 working Windows Server 2025 machines as a direct repair source. Also I'd suggest to run Dism /Online /Cleanup-Image /StartComponentCleanup Dism /Online /Cleanup-Image /RestoreHealth

Justin Matthews 5 Reputation points

2026-06-18T11:09:58.43+00:00

Hey Scott, I tried running the two DISM commands, ran SFC /Scannow and then hit Retry on the Windows Update install. Same error. Can you provide the name and location of the WIM file where I can find it on one of my successful installations so I can try that? I did a google search and it told me the file name is Winre.wim, is stored in the C:\Windows\System32\Recovery, but looking in that path on a couple of my servers, that file does not show, even after making sure I show hidden files and unchecking any option that hides files in that folder. Thanks in advance for any help you can provide.
Justin Matthews 5 Reputation points

2026-06-18T11:43:10.4766667+00:00

Sorry for the confusion. Saw where you can just share the entire Windows folder. I shared it and am running the command Dism /Online /Cleanup-Image /RestoreHealth /Source:\OtherPC\mount\windows /LimitAccess. After that, I will reboot and retry the Windows update.
Justin Matthews 20 Reputation points

2026-06-18T16:37:32.2666667+00:00

I tried the upgrade after using another working server as the repair source and rebooting the problem server, and it still didn't work. Attached is the first half of the CBS log file where the errors started occurring. it seems like there are alot of required files missing, but shouldn't the DISM Repair command bring the missing files in?
Justin Matthews 20 Reputation points

2026-06-18T16:38:01.58+00:00

CBS Log Clip Part 1.txt
Justin Matthews 20 Reputation points

2026-06-18T16:38:28.58+00:00

Part 2 is attached to this commentCBS Log Clip Part 2.txt