How to Fix Windows Update Error 0x800f0984 (2026)

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

What error 0x800f0984 means

When Windows installs a monthly cumulative update, it does not 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, each component the patch touches must actually be present on disk. Error 0x800f0984, internally known as PSFX_E_MATCHING_BINARY_MISSING, is Windows telling you that the match failed in a specific way: the component directory exists, but the binary file inside it that the patch needs to modify is gone. With nothing to patch, the update stops rather than risk leaving your system in a half-updated state.

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 0x800f0984 next to a failed cumulative update. Clicking "Retry" almost never helps: retrying downloads the same patch and runs into the same missing binary. You have to repair the component store first so the missing file is restored, and then the update installs cleanly. The repair is a standard, well-tested sequence, and it fixes the vast majority of cases without touching your personal files.

Common causes

• Corrupted component store (WinSxS): the WinSxS folder that holds every Windows component has damaged or inconsistent entries, so an update patch cannot find the binary it expects.
• Interrupted update installation: a power cut, forced shutdown, or disk-space problem during a previous update left a component half-written, with its directory present but its binary missing.
• Corrupted Windows Update cache: the SoftwareDistribution or catroot2 folders contain half-downloaded or mismatched update packages from an earlier interrupted update.
• Third-party antivirus or system cleaners: aggressive cleaners and some antivirus tools quarantine or delete system files while an update is staging, removing exactly the binary the next update needs.
• Disk errors or failing storage: bad sectors and file-system corruption can silently eat component files, and the missing binary only surfaces when an update tries to patch it.

How to fix error 0x800f0984 — 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 for stuck services, bad cache entries, and missing registrations. It fixes simple blockers on its own, and even when it does not fully solve the problem, it often clears enough of the mess that the later steps work better. When it finishes, 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 throws away the corrupted download cache and forces Windows to fetch fresh, complete update files.
3. Repair the component store with DISM. In the same admin terminal, run DISM /Online /Cleanup-Image /RestoreHealth. This command compares your component store against the known-good Windows image and replaces anything damaged or missing, including the binary that 0x800f0984 is complaining about. It usually takes 10 to 30 minutes — let it run to the end and look for the message The restore operation completed successfully. If DISM stalls or errors out, try the same command again after a restart, since a stuck update service can block it.
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 a known-good copy and repairs anything still broken. When it finishes, restart your PC and retry Windows Update from Settings. For most people, the cumulative update that kept failing with 0x800f0984 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. 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. A manual install skips the automatic updater entirely, so it can succeed even when the automatic path keeps tripping over the same broken component.
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 is the definitive fix for a component store that DISM could not repair.

Did this fix it? Quick checklist

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

If 0x800f0984 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 eat component files again. Also temporarily uninstall third-party "optimizer" or cleaner tools before retrying, since some of them delete exactly the files you just repaired.