How to Fix Windows Update Error 0x800F0983 (2026)

By ErrorFix · Updated October 21, 2026 · 9 min read

What error 0x800F0983 means

When Windows installs a monthly cumulative update, it doesn't download every file fresh. Instead it applies small delta patches to the components already on your PC — a technique Microsoft calls PSFX (Package Servicing for Files). For that to work, the components on your PC must be exactly what the patch expects. Error 0x800F0983, internally known as PSFX_E_MATCHING_COMPONENT_NOT_FOUND, is Windows telling you that the match failed: the update found a component that doesn't look like what the patch was written for, so it refused to install rather than risk breaking your system.

This error shows up on the Windows Update screen in Settings — usually with a message like "There were some problems installing updates" and the code 0x800F0983 next to a failed cumulative update. It is frustrating because clicking "Retry" almost never helps: retrying downloads the same patch and runs into the same damaged component. You have to repair the underlying components first, and then the update installs cleanly. The good news is that the repair is a standard, well-tested sequence that works for the vast majority of cases.

Common causes

• Corrupted component store (WinSxS): the WinSxS folder that holds every Windows component has damaged or inconsistent files, so updates can't match against it.
• Corrupted Windows Update cache: the SoftwareDistribution or catroot2 folders contain half-downloaded or mismatched update packages from an earlier interrupted update.
• Language pack or feature mismatch: a partially installed language pack or an optional feature left in a broken state makes components differ from what the cumulative update expects.
• Interrupted update installation: a power cut, forced shutdown, or disk-space problem during a previous update left the component store in an inconsistent state.
• Third-party antivirus or system optimizers: aggressive cleaners and some antivirus tools lock or modify system files while an update is staging, corrupting the result.

How to fix error 0x800F0983 — step by step

Work through these fixes in order. Steps 2 through 4 are the core repair; most people are fixed by step 4.

1. Run the Windows Update troubleshooter. Open Settings, go to System, then Troubleshoot, then Other troubleshooters. Click Run next to Windows Update and let the tool scan and repair common blockers. This occasionally fixes simple cases on its own, and it never hurts as a first move. When it's done, retry the update from Settings, then Windows Update, then Check for updates.
2. Reset the Windows Update components. Right-click Start and choose Terminal (Admin) or Command Prompt (Admin). Stop the four update-related services by running each command: net stop wuauserv, net stop cryptSvc, net stop bits, and net stop msiserver. Then rename the cache folders so Windows rebuilds them from scratch: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 Catroot2.old. Finally, start the services again: net start wuauserv, net start cryptSvc, net start bits, and net start msiserver. This clears the corrupted download cache without touching your files or installed updates.
3. Repair the component store with DISM. In the same admin terminal, run DISM /Online /Cleanup-Image /RestoreHealth. This command scans the component store for damage and replaces bad components with clean copies downloaded from Windows Update. It typically takes 10 to 30 minutes — let it run to the end and look for the message "The restore operation completed successfully." If DISM itself fails, see the linked DISM source-files guide on this site.
4. Verify system files with SFC. Once DISM reports success, run sfc /scannow in the admin terminal. This checks every protected Windows system file against known-good copies and repairs anything still broken. When it finishes, restart your PC and retry Windows Update from Settings. For most people, the previously failing cumulative update now installs normally.
5. Install the update manually from the Microsoft Update Catalog. If the automatic route still fails, go to Settings, then Windows Update, then Update history, and find the KB number of the failed update (for example KB5034765). Visit catalog.update.microsoft.com, search for that KB number, and download the package matching your system architecture — x64 for most Intel and AMD PCs, ARM64 for Snapdragon machines. Double-click the downloaded .msu file to install it directly. Manual installs bypass the automatic updater entirely and often succeed where the normal path got stuck.
6. Do an in-place repair install of Windows. If nothing else works, download a Windows ISO matching your edition with the Media Creation Tool on the same PC, double-click the ISO to mount it, and run setup.exe. Choose the option to keep personal files and apps. This reinstalls Windows over itself, rebuilding the entire component store while keeping your files, programs, and settings exactly as they are. It's the definitive fix for a component store that DISM couldn't repair.

Did this fix it? Quick checklist

• The cumulative update installs from Windows Update without 0x800F0983
• DISM reports "The restore operation completed successfully"
• sfc /scannow reports no integrity violations
• The failed KB number shows as installed under Update history

If 0x800F0983 keeps coming back after all of this, check your disk for errors with chkdsk C: /f /r (run it in an admin terminal, approve the restart prompt, and let it scan on reboot) — failing storage can silently corrupt the component store again. Also temporarily uninstall third-party "optimizer" or cleaner tools before retrying, since some of them re-break the exact files you just repaired.