Windows Update error 0x800f0988: how to fix it

What 0x800f0988 means

In Windows Update you’ll see Install error – 0x800f0988 next to a cumulative update, often with Updates failed at the top of the page. Microsoft’s error table names the code PSFX_E_INVALID_DELTA_COMBINATION and describes it as possibly related to a specific update branch or delta patch issues.

Cumulative updates don’t ship every file in full. Many files arrive as deltas, the differences between versions, and Windows rebuilds the new file from the copy already in the component store (the WinSxS folder). If that base copy is damaged or isn’t the version the delta was built against, the result is invalid and the install stops with this code. That’s our plain-English reading of Microsoft’s description, not a Microsoft statement, but it explains why repairing the component store is the core of the fix.

One note if you search further: an answer on Microsoft Q&A translates 0x800f0988 as PSFX_E_MATCHING_COMPONENT_NOT_FOUND. That name belongs to a different code, 0x800f0982.

Find the failing file in CBS.log

This step is optional but shows what broke. Open C:\Windows\Logs\CBS\CBS.log in Notepad (copy it to the desktop first if it’s locked) and search for 0x800F0988. The matching line names the update package and the file Windows couldn’t build, which tells you whether the problem is one component or something wider.

Fix 1: Run the Windows Update troubleshooter

On Windows 11, Microsoft now points users to the automated Windows Update troubleshooter in the Get Help app. Open Settings > System > Troubleshoot > Other troubleshooters and select Run next to Windows Update; recent builds hand this over to Get Help. On Windows 10 the path is Settings > Update & Security > Troubleshoot > Additional troubleshooters. Restart and check for updates again.

Fix 2: Reset the update folders

Microsoft’s update troubleshooting page renames the download cache and the catalog folder so Windows builds fresh copies. Open Command Prompt as administrator and run these lines one at a time:

net stop bits
net stop wuauserv
net stop cryptsvc
ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak
ren %systemroot%\System32\catroot2 catroot2.bak
net start cryptsvc
net start wuauserv
net start bits

Microsoft’s own list stops only BITS and Windows Update; we add the Cryptographic service because catroot2 is usually in use until it’s stopped. Restart the PC afterwards. Renaming rather than deleting keeps the old folders, and you can remove the .bak copies once updates work.

Fix 3: Repair the component store

Since the error points at the component store, this is the step most likely to help. In the same admin window, run:

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

DISM checks the component store against Windows Update and replaces damaged files; SFC then repairs protected system files from that store. Let each finish, restart, and try the update again. Our guide to running sfc /scannow explains the result messages. Microsoft’s page also suggests making sure you have enough free disk space (at least 20 GB on 64-bit Windows) before updating.

Fix 4: Clean up superseded components

Old, superseded versions of components can be cleared with Windows’ own cleanup task. Run:

Dism.exe /Online /Cleanup-Image /StartComponentCleanup

This removes old component versions; it doesn’t repair damaged ones, so run it after Fix 3, not instead of it. Some guides add /ResetBase. Microsoft warns that after that switch, the updates already installed can’t be uninstalled, so leave it off unless you’re sure you won’t need to roll one back.

Fix 5: Install the update manually

Note the KB number of the failing update from the Windows Update page, search for it in the Microsoft Update Catalog, and download the package that matches your Windows version and architecture (x64 or Arm64). Double-click the downloaded .msu file to install it. This doesn’t always work: in at least one Microsoft Q&A thread the standalone package failed with the same 0x800f0988, most likely because it patches the same damaged files. If that happens, move on to Fix 6. Our guide to forcing Windows Update covers checking again afterwards.

Fix 6: Reinstall Windows through Windows Update

When the component store is too damaged to patch, reinstalling the current version replaces it. Microsoft’s guidance for this error on Windows Server virtual machines in Azure is blunt: the only reliable resolution is an in-place upgrade.

• Windows 11: open Settings > System > Recovery and, under Fix problems using Windows Update, select Reinstall now. Microsoft says this keeps your apps, files and settings, needs the February 2024 optional update or later, and may be unavailable on work or school PCs.
• Windows 10: download the Media Creation Tool from Microsoft, run it, choose Upgrade this PC now and keep personal files and apps. Windows 10 reached end of support in October 2025, so updates after that need Extended Security Updates.

Back up important files before either option, even though both are designed to keep them.

If it appears when adding a language

Some users on Microsoft Q&A report 0x800f0988 when adding a language, with optional features such as text-to-speech, speech recognition or handwriting failing to install. Fixes 2 and 3 apply here too. Some guides also suggest removing extra language packs before updating; Microsoft doesn’t document that as a fix for this code, so try it only after the steps above. For related missing-source problems, see error 0x800f081f.

Related guides

• Error 0x800f081f: how to fix it in Windows 11 and 10
• 0x800f0922: how to fix this Windows Update error in Windows 11 and 10
• Windows Update error 0x800f0831: how to fix it
• How to run sfc /scannow in Windows 11 and 10 (and read the results)
• How to force Windows Update to check and install updates

Official sources

• Windows Update errors that require in-place upgrades (Microsoft Learn)
• Troubleshoot problems updating Windows (Microsoft Support)
• Fix issues by reinstalling the current version of Windows (Microsoft Support)