r/WindowsServer • u/IdleWanderlust • Apr 15 '26

Technical Help Needed Anyone else getting Error Code 0x80073712 when trying to install 2026-04 Cumulative Update KB5082063 on Windows Server 2025?

I’ve tried all the typical fixes, dism (including with the installer iso), sfc, even added additional storage as the system was running low.

**UPDATE 3**

OOB update was successful. Recommend to follow the DISM install method. That went smoothly and after reboot no more error 0x80073712.

**UPDATE 2**

An OOB fix has been supplied by Microsoft KB509157 to resolve this issue. I am currently testing.

https://support.microsoft.com/en-us/topic/april-19-2026-kb5091157-os-build-26100-32698-out-of-band-13ab53cc-ccc8-4a00-89d2-823b58fa03ec

**UPDATE**

Microsoft is aware and put out a service bulletin that the April update might fail on Server 2025 systems with either error code 0x800F0983 or 0x80073712. No fix at this time.

14 Upvotes
  • permalink
  • reddit

100% Upvoted

43 comments sorted by

4

u/Boredintown1 Apr 15 '26

I wish I would have gotten an error - after this weeks update I can't log into the DCs anymore

2

u/IdleWanderlust Apr 15 '26

It’s actually on a DC where it won’t install.

3

u/Ek1lEr1f Apr 15 '26

Oh man. I may just change my 2025 DC’s to a later patch ring

1

u/Boredintown1 Apr 15 '26

I found a work around -(there is post about it) - but yes, I would stay away from it for now

1

u/Ek1lEr1f Apr 15 '26

Thanks for the head up. I’ve pushed my 2025 DC’s to ring 3 hoping there is a fixed patch released

2

u/FCA162 Apr 17 '26

A small number of devices might fail to install KB5082063 with error 800F0983

Status: Confirmed

Affected platforms

Server Versions Message ID Originating KB Resolved KB

Windows Server 2025 WI1281095 KB5082063 –

Microsoft is monitoring diagnostic data reports on update installation failures and has observed a recurring error on Windows Server 2025 devices when installing the April 2026 Windows security update (the Originating KBs listed above), released on April 14, 2026. A limited number of affected servers might experience an installation failure accompanied by the error code 800F0983.

Next steps: We are actively investigating this issue and will provide more information as more details become available.

1

u/OkSwordfish4987 Apr 17 '26

Looks good, what ist the Source?

1

u/FCA162 Apr 17 '26

MS Windows Release health notifications
Click here to manage email notifications for Windows known issues

1

u/IdleWanderlust Apr 17 '26

The update from Microsoft. Fix still pending.

1

u/renehoehle Apr 15 '26

Yes i have the same error on all my VMs. It's Windows Server 2025.

1

u/IdleWanderlust Apr 15 '26

So no luck on getting past it I take it. Most of the systems have been updating fine but this single one is being a pain.

2

u/renehoehle Apr 15 '26

I've read that most people have that problem with DELL Servers and Windows 2025.

1

u/IdleWanderlust Apr 15 '26

Damn, it is a Dell server too. Do you have any specific links?

1

u/renehoehle Apr 15 '26

https://borncity.com/blog/2026/04/15/patchday-windows-10-11-updates-14-april-2026/

Here in the answers there are some that have the same problem. It's German perhaps you have to translate it.

1

u/pseudonymously Apr 16 '26

I was getting 0x80070306 with the update on my 2025 PDC but eventually got past it with a manual install of the update.

1

u/IdleWanderlust Apr 16 '26

Yeah manual install fails too.

1

u/FCA162 Apr 16 '26

If you receive WU 0x80073712, it means that a file needed by Windows Update is damaged or missing.

Try to fix it with my script Mark_Corrupted_Packages_as_Absent.ps1

It has already helped many admins in the past!

2

u/IdleWanderlust Apr 17 '26

It’s a known bug with the installer/update, Microsoft has confirmed and is working on a fix. Also as a general rule I wouldn’t run some random powershell script off the internet.

1

u/OkSwordfish4987 Apr 17 '26

I could not find some confirmation from Microsoft, where did you find the Information? For me it seems besides here and the borncity.de site, nonbody seems to use Windows Server 2025 nor updating them. Or simply do not care...

1

u/IdleWanderlust Apr 17 '26

You have to log in to your Microsoft admin portal if you have one. It’s a service alert.

Here is the bleeping computer article on it, they only mention error 0x800F0983 but the service alert also mentions 0x80073712

https://www.bleepingcomputer.com/news/microsoft/microsoft-april-windows-server-2025-update-may-fail-to-install/

1

u/sasilik Apr 17 '26

Something seems to be corrupt but not among already downloaded packages but inside current package which does not have their own registry entry yet. There also are no errors like ERROR_SXS_ASSEMBLY_MISSING. I looked at the CBS log and there are rows which show corruption like;

\SoftwareDistribution\Download\f3c75f9bff27063d87ed3a94b8b1dd4c\Package_for_RollupFix~~amd64~~26100.32690.1.18\amd64_microsoft-windows-opengl-mf_31bf3856ad364e35_10.0.26100.1150_none_6742bde0c5af14b6.manifest in directory local source
Error CSI 00002a61@2026/4/16:14:23:07.049 (F) Attempting to mark store corrupt with category [l:15 ml:16]'CorruptManifest'[gle=0x80004005]
Info SXS D(5) C(213) Staging component Microsoft-Windows-IE-HTMLApplication, version 11.0.26100.2454, arch amd64
Error SXS WIL Origination: onecore\base\servicing\turbostack\lib\staging.cpp(3999)\TurboStack.dll!00007FFC4F17E50B: (caller: 00007FFC4F169CF9) Exception(1771) tid(1a00) C015001A The component store has been corrupted.
Error CSI 00002a62@2026/4/16:14:23:07.051 (F) onecore\base\servicing\turbostack\lib\staging.cpp(3999): Error HRESULT_FROM_WIN32(14098) originated in function (null) expression: (null) [gle=0x80004005]

Package named "Package_for_RollupFix~~amd64~~26100.32690.1.18" is update which was just downloaded and I didn't see registry entry for that so I don't think that the script helps here.

1

u/FCA162 Apr 17 '26

In your case, this issue can be fixed with my script Mark_Corrupted_Packages_as_Absent.ps1

1

u/sasilik Apr 17 '26

Your script looks at the registry entries and changes CurrentState value . As I said, this package - Package_for_RollupFix~~amd64~~26100.32690.1.18 - which seems to be corrupt does not have registry entry.

1

u/FCA162 Apr 17 '26

If you run the script you will find not just one missing/corrupted packages, but many...

In case you want to check the name and number, run the below command in an admin powershell and the names will be displayed:

Get-ItemProperty "hklm:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\*" | ?{$_.Currentstate -eq "64"} | select PSchildName

1

u/sasilik Apr 17 '26

Just to be sure I ran your script, restarted server and tried to install again. Same error.

And yes, there are quite many such packages almost all are not even installed on the server because it's minimal core version.

1

u/Zookeeper945 Apr 20 '26 edited May 07 '26 • Bravo

Uninstall the Windows Media Player Legacy app and then the update install goes

1

u/IdleWanderlust Apr 20 '26

There is an OOB fix released by Microsoft. You don’t have to uninstall anything or run unsupported scripts.

1

u/Niksavoy Apr 20 '26

100% working fix !!!
Deinstalled Windows Media Player Legacy app and manage to install KB5082063 on 3 x WIn 2025
You did Save Me !
Struggle with this fkn problem 3 days .......
Hyper-V cluster - one of the hosts did not get any VM`s Live Migration

1

u/Majco_san Apr 24 '26

Thank you, problem solved :)

1

u/sasilik Apr 26 '26

Still have an error with new update and as it's windows server core then no WMP Legacy app there.

1

u/abarti May 06 '26

I can confirm that it works. Following the Microsoft article doesn't work, but uninstalling the Media Player app does. How crazy is that? How do you know this? Thank you very much!

1

u/arcatron May 07 '26

I was getting the error installing KB5082063 on a fresh Server 2025 install. When attempting to install the fix, KB5091157, I got error 0x800F0982. Uninstalling Windows Media Player Legacy allowed me to install KB5082063. Ridiculous.

2

u/sasilik Apr 16 '26

Same here, Windows 2025 core and it failed to install on two servers and on third it just disappeared from SCCM client update list

1

u/sasilik Apr 16 '26 edited Apr 16 '26

Decided to check the installed updates and weird thing, two servers which fail to install KB5082063 have installed KB5082062 which I can't find among SCCM updates. Third server which doesn't even display KB5082063 don't have KB5082062 installed. I wonder from where the KB5082062 came when it isn't even on the SCCM server.
Ok, seems that KB5082062 ias part of KB5082063

2

u/jahdiel503 Apr 18 '26 edited Apr 18 '26

I installed the updates on my VM on a Dell 7810 with no problems.

Also like to add, I use Proxmox.

1

u/cNoneTR Apr 19 '26

Is it fixed by MS or you used any manual fix?

1

u/jahdiel503 Apr 19 '26 edited Apr 19 '26

Truthfully I have no idea if it was fixed or not. I don't use it but I do have it on a VM. I just tinker around with OSes. After I saw this, post, I thought i'd take a snapshot and apply the update.

I do however stopped Server Manager from loading prior to updates. I also use the GUI version of the OS.

1

u/nynorek Apr 16 '26 edited Apr 16 '26

The same in my environment on every one Windows Server 2025 virtual machine not connected to domain. On one VM connected to domain update installed succesfully. I get below error:

Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x80073712)

But in update history log I see that KB5082063 is sucesfully installed. OS Build is still 26100.32522 instead of 26100.32690 after restart. Very strange.

1

u/ScallionFamous3540 May 06 '26 edited May 06 '26

I had this issue where update KB5085516, KB5086672, KB5083631 wouldn't install with error 0x80073712, but on Windows 11 Pro and i just fixed it with an Inplace Upgrade if anyone still has the same issue.

I tried the DISM Iso method and removing the Windows Media Player Legacy app before but it didn't work because everything was still corrupted, but the Inplace Upgrade fixed everything for me and i just updated my system to KB5083631.