The April 14, 2026 security update KB5082063 fails to install on some Windows Server 2025 systems with error code 0x800F0983. Microsoft confirmed the known issue on the Windows release health dashboard as WI1281095 and is currently investigating. A companion failure, 0x80073712, has also been reported on the same build.

If you manage on-prem or hybrid Windows Server 2025 hosts, expect this to show up on domain controllers first. Here is how to get the update to apply while Microsoft works on a permanent fix.

Clear the Update Cache First

Most 0x800F0983 and 0x80073712 failures come from a corrupt Windows Update component store. Reset it from an elevated PowerShell prompt:

Stop-Service -Name wuauserv, cryptSvc, bits, msiserver -Force
Rename-Item -Path "$env:SystemRoot\SoftwareDistribution" -NewName "SoftwareDistribution.old"
Rename-Item -Path "$env:SystemRoot\System32\catroot2" -NewName "catroot2.old"
Start-Service -Name wuauserv, cryptSvc, bits, msiserver

Retry Windows Update after the services restart.

Repair the Component Store

If the update still fails, run DISM and SFC before retrying:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Reboot, then retry the update. DISM repairs the servicing stack that actually applies cumulative updates, which is where 0x800F0983 typically chokes.

Manual Install via Catalog

If Windows Update still refuses, pull the MSU directly from the Microsoft Update Catalog and install from an elevated prompt:

wusa.exe C:\Updates\windows11.0-kb5082063-x64.msu /quiet /norestart

Log the install attempt for diagnostics:

Get-WindowsUpdateLog

The log lands on your desktop as WindowsUpdate.log. Search for 0x800F0983 to see which component is rejecting the package.

Check Release Health Before Redeploying

Microsoft is tracking this under WI1281095 on the Windows release health dashboard. Check that page before re-running any patch ring. If the status changes to resolved, an out-of-band update is likely on the way and will be safer than chasing manual installs on every host.

Verify

Confirm KB5082063 is actually installed:

Get-HotFix -Id KB5082063

Expected output: an entry with HotFixID: KB5082063 and an InstalledOn date.

If Get-HotFix returns nothing, cross-check with the servicing stack:

DISM /Online /Get-Packages | Select-String "5082063"

Need help testing Patch Tuesday in a lab before pushing to production? Contact Rain City Techworks.