Windows 11 KB5077181 Update Won't Install — Error 0x800f0983 Fix

What is the KB5077181 installation error 0x800f0983?

The February 2026 cumulative update KB5077181 for Windows 11 25H2 (build 26200.7840) fails to install for many users with error code 0x800f0983. This error means the Windows component store (WinSxS) is damaged or missing required files — specifically, the update cannot locate a matching component directory needed to apply the patch. Windows Update downloads the update, begins installation, then rolls back with the message "We couldn't install this update, but you can try again (0x800f0983)."

This is the most reported KB5077181 issue, distinct from the post-install problems like boot loops or Bluetooth failures covered in our other guides. The root cause is typically a corrupted servicing stack or leftover fragments from previous failed updates.

When does it occur?

• During automatic Windows Update installation of KB5077181
• After retrying the update multiple times through Settings → Windows Update
• On systems that had previous cumulative update failures (KB5074109, KB5067036)
• On Windows 11 25H2 systems with multiple language packs installed
• After interrupted or incomplete prior Windows updates
• On systems with BitLocker enabled where SoftwareDistribution renaming triggers recovery

Common causes

• Corrupted component store (WinSxS) — damaged manifest files prevent the update from finding required components
• Incomplete previous update cleanup — fragments from failed KB5074109 or earlier cumulative updates block the new installation
• Language pack conflicts — multiple installed language packs create component mismatches during servicing
• Corrupted SoftwareDistribution folder — cached update files are inconsistent with the current system state
• BitLocker interference — renaming the SoftwareDistribution folder on BitLocker-encrypted drives can trigger a boot failure and recovery key prompt
• Damaged servicing stack — the Windows Update servicing infrastructure itself is in a broken state

Step-by-step fixes

1. Run DISM and SFC repair — Open Command Prompt as Administrator and run these commands in sequence:

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

Wait for each command to complete fully (DISM can take 15-30 minutes). Restart your PC, then retry Windows Update. This repairs the component store and replaces corrupted system files.

1. Use Windows Update Repair Reinstall — Navigate to Settings → System → Recovery → "Fix problems using Windows Update" → select "Reinstall now." This performs a repair reinstall that resets the servicing stack without losing your files or apps. This is the most effective fix for persistent 0x800f0983 errors.

1. Analyze CBS logs for the blocking component — Open C:\Windows\Logs\CBS\CBS.log in Notepad and search for PSFX_E_MATCHING_COMPONENT_DIRECTORY_MISSING. The line before this error identifies the exact component blocking installation. Search for that component name on Microsoft's support forums for a targeted fix.

1. Reset Windows Update components — Open Command Prompt as Administrator and run:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Warning: On BitLocker-encrypted systems, renaming SoftwareDistribution may trigger a BitLocker recovery screen on reboot. Have your recovery key ready before proceeding.

1. Remove non-essential language packs — Go to Settings → Time & language → Language & region. Remove all language packs except your primary system language. Language pack conflicts are a known cause of 0x800f0983 on multi-language installations. Restart and retry the update.

1. Install manually from Microsoft Update Catalog — Visit the [Microsoft Update Catalog](https://catalog.update.microsoft.com), search for "KB5077181," download the .msu file matching your system architecture (x64 or ARM64), and run it directly. This bypasses the Windows Update client entirely.

1. Run the Windows Update Troubleshooter — Go to Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run. This automatically detects and repairs common Windows Update issues including stuck downloads and corrupted cache files.

1. Perform an in-place repair upgrade — As a last resort, download the Windows 11 ISO from Microsoft's website, mount it, and run setup.exe. Choose "Keep personal files and apps." This performs the cleanest possible servicing stack reset while preserving all your data and applications.

If it still doesn't work

If none of the above resolves the installation failure, consider pausing Windows Update (Settings → Windows Update → Pause for 1 week) until Microsoft releases a corrected version of the update. Microsoft has acknowledged installation issues with KB5077181 on their Q&A forums. You can also check for newer cumulative updates that supersede KB5077181 — later updates typically include fixes for prior installation blockers. For enterprise environments, consult your WSUS or Intune administrator, as group policy or compliance settings may interfere with the update servicing stack. If you successfully installed KB5077181 but are experiencing other issues, see our guides for [KB5077181 boot loop fix](/en/errors/windows-11-kb5077181-boot-loop-fix), [Bluetooth audio issues](/en/errors/windows-11-kb5077181-bluetooth-audio-issues), and [network DHCP failure](/en/errors/windows-11-kb5077181-network-dhcp-failure).