Fix Windows 11 Update Error 0x800f0982 (2026 Guide)

Introduction

Windows 11 error 0x800f0982 is one of the most frustrating update failures because it appears without warning, often after the update has already downloaded and begun installing. The error translates to PSFX_E_MATCHING_COMPONENT_NOT_FOUND, which means the Windows Update engine could not find a matching base component for every language pack installed on your system. It most often appears during cumulative update installations such as KB5037771, KB5039212 and KB5039302 on Windows 11 22H2 and 23H2.

When this error strikes, the update rolls back completely, and Windows may attempt to install the same update repeatedly, failing at the same point every time. That wastes bandwidth and time, and it leaves the system exposed to unpatched security vulnerabilities.

This guide works through twelve fixes in the order an IT support technician would try them, starting with the least disruptive. It includes copy-ready commands, expected output, a root-cause table, a before-and-after check, and answers to the questions that come up most often.

Problem Description

Error 0x800f0982 occurs during the installation phase of Windows cumulative updates. The update downloads successfully, reaches a specific percentage during installation (often between 20% and 60%), and then fails with the message "Something went wrong. We will undo the changes made to your computer." After the rollback completes, Windows Update displays error code 0x800f0982.

The underlying problem lives in the Windows Side-by-Side (WinSxS) store. When a cumulative update attempts to update system files, it checks for base components corresponding to every language pack installed on the system. If a language pack version does not match the current build, because it was partially installed, updated through the Microsoft Store independently, or manually modified, the update engine cannot find the files it needs. That triggers the PSFX_E_MATCHING_COMPONENT_NOT_FOUND failure.

Symptoms

  • The cumulative update fails to install with error 0x800f0982.
  • The update downloads to 100% but fails during installation.
  • Windows automatically rolls back changes after the failure.
  • Repeated attempts to install the same update produce the same error.
  • Event Viewer shows Event ID 41 or Event ID 20 under Windows Update Client.
  • Windows Update history displays "Failed to install" with error code 0x800f0982.
  • The system may become slow or unresponsive during rollback operations.

Root Causes

Root causeTypical clueFirst check
Language pack installed from the Microsoft StoreError started after adding a display languageSettings > Language & region
Partial or interrupted language pack installOnly some UI text is translatedGet-WindowsPackage -Online
Manually deployed LP CAB from a different buildError follows a DISM language deploymentCompare LP version to OS build
Corrupted WinSxS component storeDISM reports repairable corruptionDISM /Online /Cleanup-Image /ScanHealth
Damaged update cacheFailure repeats at the same percentageClear SoftwareDistribution
Insufficient free disk spaceLow-space warnings before the updateGet-PSDrive C
Windows Modules Installer stoppedUpdates fail immediatelyGet-Service TrustedInstaller
Pending reboot from an earlier updateUpdate never leaves "Pending install"Restart, then retry

Before You Start

Open Terminal (Admin): right-click Start and choose Terminal (Admin). Confirm the window title says Administrator. Then record the current build and the KB number that is failing, so you can verify the fix later.

PowerShell
Get-ComputerInfo | Select-Object WindowsProductName, OsBuildNumber, OsVersion
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5 HotFixID, InstalledOn

Expected output (build and KB numbers vary):

Output
WindowsProductName OsBuildNumber OsVersion
------------------ ------------- ---------
Windows 11 Pro     22631         10.0.22631

Step 1: Run the Windows Update Troubleshooter

Before attempting advanced repairs, run the built-in Windows Update troubleshooter. It can automatically detect and resolve common update issues.

  1. Press Windows key + I to open Settings.
  2. Navigate to System > Troubleshoot > Other troubleshooters.
  3. Scroll down and click Run next to Windows Update.
  4. Follow the on-screen instructions.
  5. Restart the computer and check for updates again.

While this step alone rarely resolves error 0x800f0982, it clears the path for more advanced fixes by resetting update-related services and files.

Step 2: Clear the Windows Update Cache

Corrupted update cache files can trigger the error. Clearing the SoftwareDistribution folder forces Windows Update to download fresh copies of all required files.

  1. Press Windows key + R, type services.msc and press Enter.
  2. Right-click Windows Update and select Stop.
  3. Right-click Background Intelligent Transfer Service (BITS) and select Stop.
  4. Open File Explorer and navigate to C:\Windows\SoftwareDistribution.
  5. Select all files and folders inside and press Delete.
  6. Navigate to C:\Windows\System32\catroot2 and delete all contents.
  7. Return to services.msc, right-click Windows Update and select Start.
  8. Right-click BITS and select Start.
  9. Restart the computer and try updating again.

The same reset can be scripted from an elevated terminal:

PowerShell
net stop wuauserv
net stop bits
Remove-Item C:\Windows\SoftwareDistribution\* -Recurse -Force -ErrorAction SilentlyContinue
Remove-Item C:\Windows\System32\catroot2\* -Recurse -Force -ErrorAction SilentlyContinue
net start wuauserv
net start bits

Step 3: Repair the Component Store with DISM

DISM (Deployment Image Servicing and Management) repairs corruption inside the Windows system image and the WinSxS component store. This is the most effective single fix for error 0x800f0982.

  1. Press Windows key + X and select Terminal (Admin).
  2. Check the health of the system image.
  3. If issues are reported, scan for corruption.
  4. Repair the corrupted components.
PowerShell
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

If a Windows 11 installation ISO is mounted, point DISM at it so the repair does not depend on Windows Update:

PowerShell
DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\SxS /LimitAccess

Replace D: with the drive letter of the mounted ISO. RestoreHealth usually takes 15 to 30 minutes; do not close the window while the progress bar is between 20% and 100%.

Expected output when the store is healthy:

Output
The restore operation completed successfully.
The operation completed successfully.

Step 4: Run System File Checker (SFC)

SFC scans and repairs corrupted system files that may contribute to the component store mismatch.

  1. Open Terminal (Admin).
  2. Run the scan.
  3. Allow it to complete. This typically takes 10 to 20 minutes.
  4. If corruption is found and repaired, restart the computer.
  5. Run the scan again to verify that no corruption remains.
PowerShell
sfc /scannow

Typical results:

OutputMeaningNext action
"did not find any integrity violations"No file corruptionContinue to Step 5
"successfully repaired them"Corruption repairedRestart, then retry the update
"found corrupt files but was unable to fix some"Repair needs a sourceRepeat Step 3, then run SFC again
"could not perform the requested operation"SFC cannot runBoot to Safe Mode and retry

Step 5: Remove and Reinstall Language Packs

Because error 0x800f0982 is directly related to language pack conflicts, removing and reinstalling non-primary language packs often resolves it.

  1. Open Settings > Time & language > Language & region.
  2. Under Preferred languages, note all languages other than the primary one.
  3. For each additional language, click the three dots and select Remove.
  4. Restart the computer.
  5. Run Windows Update and attempt to install the failing update.
  6. After the update installs successfully, return to Language & region settings.
  7. Click Add a language and reinstall the additional languages.

If the Settings path does not work, use PowerShell. List the installed language packages first:

PowerShell
Get-WindowsPackage -Online |
  Where-Object { $_.PackageName -like "*Language*" } |
  Select-Object PackageName, PackageState |
  Format-Table -AutoSize

Remove each non-primary language pack by name:

PowerShell
Remove-WindowsPackage -Online -PackageName "Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-GB~10.0.22621.1"

Step 6: Reset Windows Update Components

For persistent cases, reset every Windows Update component. This stops the services, renames the cache folders (keeping them as backups) and restarts the services with fresh directories.

PowerShell
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

Run these commands in order from Terminal (Admin). If a ren command reports "The system cannot find the file specified", the folder was already renamed by an earlier attempt and you can continue.

Step 7: Install the Update Manually from the Microsoft Update Catalog

If automatic Windows Update continues to fail, download and install the problematic update by hand.

  1. Open Windows Update, look at the update history and note the KB number (for example KB5037771).
  2. Visit the Microsoft Update Catalog at https://www.catalog.update.microsoft.com.
  3. Search for the KB number.
  4. Download the version matching the system architecture (x64 or ARM64).
  5. Double-click the downloaded .msu file to install it.
  6. Restart the computer after installation.

Check the installed result with:

PowerShell
Get-HotFix -Id KB5037771

Step 8: Start the Windows Modules Installer Service

The Windows Modules Installer service (TrustedInstaller) must be running for updates to install correctly.

  1. Press Windows key + R, type services.msc and press Enter.
  2. Scroll down to Windows Modules Installer.
  3. If the service is not running, right-click and select Start.
  4. Right-click again and select Properties.
  5. Set Startup type to Automatic and click Apply.
  6. Restart the computer.
PowerShell
Get-Service TrustedInstaller | Select-Object Name, Status, StartType

Step 9: Free Up Disk Space

Low disk space can cause update installations to fail. Windows needs room for the download, the extracted payload and the rollback copy.

  1. Press Windows key + S and type Disk Cleanup.
  2. Select the C: drive and click OK.
  3. Click Clean up system files.
  4. Select Windows Update Cleanup, Delivery Optimization Files and Temporary files.
  5. Click OK and confirm deletion.
  6. Restart the computer.
PowerShell
Get-PSDrive C | Select-Object Name, @{n='FreeGB';e={[math]::Round($_.Free/1GB,2)}}

Step 10: Remove the Problematic Cumulative Update

If a specific cumulative update causes the error loop, remove it and block it temporarily until a fixed build is available. This requires the PSWindowsUpdate module.

PowerShell
Install-Module PSWindowsUpdate -Force
Get-WindowsUpdate -KBArticleID KB5037771
Remove-WindowsUpdate -KBArticleID KB5037771 -Confirm:$false

Then pause updates for up to five weeks from Settings > Windows Update > Pause updates, so the same package does not immediately reinstall.

Step 11: Repair Install Windows 11 (In-Place Upgrade)

An in-place upgrade reinstalls Windows while preserving files, applications and settings. It is the most comprehensive fix and resolves nearly all component store issues.

  1. Download the Windows 11 Media Creation Tool from Microsoft.
  2. Run the tool and select Download ISO file.
  3. Mount the ISO by double-clicking it.
  4. Run setup.exe from the mounted ISO.
  5. Select Download updates, drivers and optional features (recommended).
  6. Choose Keep personal files and apps.
  7. Click Install and allow the process to complete.
  8. The computer restarts several times during the upgrade.

Step 12: Automate the Repair Across Multiple PCs

For IT administrators managing several workstations, wrap the safe steps in one script so each machine gets the same treatment.

PowerShell
# Run as Administrator. Does not remove language packs automatically.
$ErrorActionPreference = 'Continue'

net stop wuauserv; net stop bits; net stop cryptSvc
Rename-Item C:\Windows\SoftwareDistribution SoftwareDistribution.old -ErrorAction SilentlyContinue
Rename-Item C:\Windows\System32\catroot2 catroot2.old -ErrorAction SilentlyContinue
net start cryptSvc; net start bits; net start wuauserv

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

Get-WindowsPackage -Online |
  Where-Object { $_.PackageName -like '*Language*' } |
  Select-Object PackageName, PackageState |
  Export-Csv C:\Temp\language-packs.csv -NoTypeInformation

Review language-packs.csv before removing anything, so the primary language is never touched. Log the DISM and SFC output to a file with Start-Transcript when you need an audit trail.

Verify the Fix

After any of the steps above, confirm that the update is installed and that the error has stopped recurring.

CheckBefore (broken)After (fixed)
Windows Update history"Failed to install" 0x800f0982"Successfully installed"
Get-HotFix -Id KB5037771No resultReturns the hotfix entry
DISM /Online /Cleanup-Image /CheckHealth"The component store is repairable""No component store corruption detected"
Event Viewer > Windows Update ClientRepeated Event ID 20No new failure events
RebootUpdate rolls backUpdate stays applied

Frequently Asked Questions

What causes Windows 11 update error 0x800f0982?

The error is caused by a language pack version mismatch in the WinSxS component store. When a cumulative update cannot find matching base components for installed language packs, the installation fails with PSFX_E_MATCHING_COMPONENT_NOT_FOUND.

Can I ignore error 0x800f0982 and skip the update?

Skipping cumulative updates leaves the system vulnerable to unpatched security exploits. Resolve the error instead of ignoring it, or pause updates only until a fixed build is available.

Will uninstalling language packs delete my data?

No. Removing a language pack only removes the display language for the Windows interface. Personal files and applications remain unchanged.

How long does DISM /RestoreHealth take?

DISM typically takes 15 to 30 minutes, depending on system speed and the extent of corruption. Slower mechanical drives and heavy corruption can push it past an hour.

What is the difference between DISM CheckHealth, ScanHealth and RestoreHealth?

CheckHealth reports the current health status quickly. ScanHealth performs a deeper scan and reports corruption. RestoreHealth repairs the corruption that the scan found.

Does an in-place upgrade delete my files?

No. An in-place upgrade preserves personal files, applications and settings while replacing Windows system files, provided the ISO edition and language match.

Why does error 0x800f0982 keep coming back after I fix it?

It returns when the underlying WinSxS corruption was not fully repaired, or when Windows Update or the Microsoft Store reinstalls the conflicting language pack. Re-check the language packages after each repair.

Can I fix error 0x800f0982 without admin access?

No. Every repair for this error requires administrative privileges. Contact the IT department if the account is not an administrator.

Does error 0x800f0982 affect Windows 10?

It primarily affects Windows 11 22H2 and 23H2, but the same language pack conflict can occur on Windows 10 and the same DISM and SFC steps apply.

What is PSFX_E_MATCHING_COMPONENT_NOT_FOUND?

It is the internal error name behind 0x800f0982. It means Windows Update could not find a matching component in the WinSxS store for the installed language packs.

Can antivirus software cause error 0x800f0982?

Indirectly, yes. Security software can interfere with file operations during installation and contribute to component store corruption. Temporarily disabling real-time protection during the repair is a reasonable last diagnostic step.

Should I use the Windows Update troubleshooter first?

Yes. Run the troubleshooter before advanced repairs such as DISM or language pack removal. It resets update services and clears the path for the later steps.

Conclusion

Error 0x800f0982 is a component store mismatch that prevents cumulative updates from installing. The fix order matters: run the troubleshooter and clear the update cache, repair the store with DISM, then SFC, then remove conflicting language packs. For most users, the combination of DISM /RestoreHealth, sfc /scannow and language pack removal resolves the problem. For persistent cases, an in-place upgrade provides the most comprehensive repair without data loss.

Enterprise administrators should standardise the Step 12 script, log its output, and review installed language packs after every failed deployment. Regular DISM maintenance and controlled language pack rollout prevent the error from returning.

If none of these methods resolve the issue, browse the IT Troubleshooting Center for more Windows error fixes and support resources.

We Value Your Privacy

We use cookies to improve your browsing experience, analyze traffic, and display relevant advertisements.