Windows 11 users on versions 22H2 and 23H2 often see error 0x800f0982 when installing cumulative update KB5037771. This error stops the update from finishing and usually rolls back the installation after it hits a certain percentage.

The error message usually looks like this:

0x800f0982. PSFX_E_MATCHING_COMPONENT_NOT_FOUND

Use these steps to fix the component mismatch and get the update installed. For general troubleshooting, view our other Windows fixes.

Why Error 0x800f0982 Occurs

The PSFX_E_MATCHING_COMPONENT_NOT_FOUND error is a failure within the Windows Side-by-Side (WinSxS) store. When KB5037771 updates system files, it checks for base components for every installed language.

The conflict happens when there is a mismatch between a Language Pack or Local Experience Pack (LXP) and the current build. If a language pack was partially installed, changed manually, or installed through the Microsoft Store without the right system components, the update engine cannot find the files it needs. This causes the installation to fail.

Step 1: Repair the Component Store with DISM

First, repair the WinSxS store. The DISM tool identifies and fixes corruption within the system image.

  1. Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin).
  2. Type the following command and press Enter:

dism /online /cleanup-image /restorehealth

Wait for it to reach 100 percent. If the tool reports that it fixed corruption, restart the computer and try the update again.

Step 2: Reinstall Affected Language Packs

If DISM does not work, the conflict is likely in a specific language pack. Removing and re-adding non-English languages forces Windows to sync component versions.

  1. Go to Settings > Time & language > Language & region.
  2. Check the list of installed languages.
  3. For any language other than your primary one, click the three dots and select Remove.
  4. Restart your computer.
  5. Run Windows Update again.
  6. Once KB5037771 installs, go back to settings and re-add your languages.

Step 3: Verify System Integrity

Run System File Checker (SFC) with DISM to make sure core system files are correct. You can find similar command-line solutions in our guide for PowerShell scripts.

  1. Open Terminal (Admin).
  2. Run this command:

sfc /scannow

If SFC finds corruption but cannot fix it, run the DISM command from Step 1 again while connected to the internet.

Step 4: Clear the Windows Update Cache

Corrupted update files in the cache can trigger 0x800f0982. Clearing these files forces a fresh check.

  1. Open Terminal (Admin).
  2. Stop the update services:
    net stop wuauserv
    net stop bits
  3. Open File Explorer and go to C:\Windows\SoftwareDistribution.
  4. Delete all files and folders inside.
  5. Restart the services:
    net start wuauserv
    net start bits

Step 5: Manual Installation of KB5039212

Microsoft released later updates that bypass the logic failure in KB5037771. Installing the June 2024 cumulative update (KB5039212) or a newer version manually can fix the loop.

  1. Visit the Microsoft Update Catalog.
  2. Search for KB5039212.
  3. Download the version for your system architecture (x64 or ARM64).
  4. Run the .msu file to install it.

If you have issues with other parts of the system after these repairs, check our guide to fix Outlook error 0xc0000409 since system mismatches can hit Office apps too.

Need help? Contact our team.

Related reading: