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. This typically occurs during cumulative update installations such as KB5037771, KB5039212, and KB5039302 on Windows 11 versions 22H2 and 23H2.
When this error strikes, the update rolls back completely, and Windows may attempt to install the same update repeatedly — each time failing at the same point. This not only wastes bandwidth and time but also leaves your system exposed to unpatched security vulnerabilities.
This guide provides 12 proven methods to fix error 0x800f0982 on Windows 11, ranging from simple built-in troubleshooters to advanced DISM commands, language pack reinstallation, PowerShell automation scripts, and in-place upgrade repair.
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 is located 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, triggering the PSFX_E_MATCHING_COMPONENT_NOT_FOUND failure.
Symptoms
- Cumulative update fails to install with error 0x800f0982
- Update downloads to 100% but fails during installation
- Windows automatically rolls back changes after failure
- Repeated attempts to install the same update result in the same error
- Event Viewer logs show Event ID 41 or Event ID 20 under Windows Update Client
- Windows Update history displays "Failed to install" with error code 0x800f0982
- System may become slow or unresponsive during rollback operations
Root Cause
The root cause of error 0x800f0982 is a version mismatch between installed language packs and the system build inside the WinSxS component store. This mismatch occurs because:
1. Language packs installed via Microsoft Store: When you install a language pack through the Microsoft Store, it may not register correctly with the component store, leaving the WinSxS store with incomplete or mismatched references.
2. Partial language pack installations: If a language pack installation was interrupted or failed, the components remain in an incomplete state that the update engine cannot process.
3. Manual language pack modifications: IT administrators who manually deployed language packs using DISM or LP Cab files may have deployed a version that does not perfectly match the current Windows build.
4. Corrupted WinSxS store: General component store corruption from failed updates, disk errors, or malicious software can cause the component store to lose track of installed language pack versions.
Troubleshooting Steps
Step 1: Run the Windows Update Troubleshooter
Before attempting advanced repairs, run the built-in Windows Update troubleshooter. This tool 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 your 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 error 0x800f0982. 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 your computer and try updating again.
Step 3: Repair the Component Store with DISM
DISM (Deployment Image Servicing and Management) repairs corruption within the Windows system image and the WinSxS component store. This is the most effective fix for error 0x800f0982.
1. Press Windows key + X and select Terminal (Admin) or Command Prompt (Admin).
2. Run the following command to check the health of the system image:
DISM /Online /Cleanup-Image /CheckHealth
3. If issues are found, run the scan to identify the corruption level:
DISM /Online /Cleanup-Image /ScanHealth
4. Run the restore operation to repair corrupted components:
DISM /Online /Cleanup-Image /RestoreHealth
5. If you have a Windows 11 installation ISO mounted, use this command instead to specify the source:
DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\SxS /LimitAccess
Replace D: with the drive letter of your mounted ISO.
6. Wait for the operation to complete. This may take 15-30 minutes.
7. Restart your computer when finished.
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. Enter the following command: sfc /scannow
3. Allow the scan to complete. This typically takes 10-20 minutes.
4. If corruption is found and repaired, restart your computer.
5. Run the scan again to verify all corruption is resolved.
Run DISM first, then SFC. DISM repairs the component store that SFC depends on, so running DISM before SFC ensures SFC can function correctly.
Step 5: Remove and Reinstall Language Packs
Since error 0x800f0982 is directly related to language pack conflicts, removing and reinstalling non-primary language packs often resolves the issue.
1. Open Settings > Time & language > Language & region.
2. Under Preferred languages, note all languages other than your primary language.
3. For each additional language, click the three dots and select Remove.
4. Restart your 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 your additional languages.
If the above does not work, use PowerShell to remove language packs:
1. Open PowerShell (Admin).
2. List installed language packs: Get-WindowsPackage -Online | Where-Object {$_.PackageName -like "*Language*"} | Format-Table -Property PackageName
3. Remove each non-primary language pack: Remove-WindowsPackage -Online -PackageName "LanguagePack-PackageNameHere"
Step 6: Reset Windows Update Components Using PowerShell
For persistent cases, reset all Windows Update components using an automated PowerShell script.
Run PowerShell (Admin) and execute the following commands in order:
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
This script stops the update services, renames the cache folders (keeping them as backups), and restarts the services with fresh cache directories.
Step 7: Install the Update Manually from Microsoft Update Catalog
If automatic Windows Update continues to fail, download and install the problematic update manually.
1. Open Windows Update, look at the update history, and note the KB number (e.g., 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 your system architecture (x64 or ARM64).
5. Double-click the downloaded .msu file to install.
6. Restart your computer after installation.
Step 8: Run Windows Modules Installer Service
The Windows Modules Installer service 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 your computer.
Step 9: Perform Disk Cleanup
Low disk space can cause update installations to fail. Run Disk Cleanup to free up space, especially in the Windows temporary files area.
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 your computer.
Step 10: Use PowerShell to Remove Problematic Cumulative Updates
If a specific cumulative update is causing the error loop, remove it using PowerShell and block it temporarily. This requires the PSWindowsUpdate module. Install it with: Install-Module PSWindowsUpdate -Force
Step 11: Repair Install Windows 11 (In-Place Upgrade)
An in-place upgrade reinstalls Windows while preserving your files, applications, and settings. This 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. Your computer will restart several times during the upgrade.
Step 12: Use PowerShell to Automate Full Component Repair
For enterprise IT administrators managing multiple machines, use an automated PowerShell script that performs all essential repairs: stopping Windows Update services, renaming cache folders, running DISM RestoreHealth, running SFC scannow, and removing non-primary language packs.
FAQ
### Q1: 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.
### Q2: Can I ignore error 0x800f0982 and skip the update?
Skipping cumulative updates leaves your system vulnerable to unpatched security exploits. You should resolve the error rather than ignore it.
### Q3: Will uninstalling language packs delete my data?
No. Removing a language pack only removes the display language for the Windows interface. Your personal files and applications remain unchanged.
### Q4: How long does DISM /RestoreHealth take?
DISM typically takes 15 to 30 minutes to complete, depending on your system speed and the extent of corruption.
### Q5: What is the difference between DISM CheckHealth, ScanHealth, and RestoreHealth?
CheckHealth reports the current health status. ScanHealth performs a deeper scan and reports corruption. RestoreHealth repairs any corruption found.
### Q6: Does an in-place upgrade delete my files?
No. An in-place upgrade (repair install) preserves your personal files, applications, and settings while replacing Windows system files.
### Q7: Why does error 0x800f0982 keep coming back after I fix it?
The error returns if the underlying WinSxS corruption was not fully repaired, or if a language pack is being reinstalled by Windows Update or the Microsoft Store.
### Q8: Can I fix error 0x800f0982 without admin access?
No. All repairs for this error require administrative privileges. Contact your IT department if you do not have admin access.
### Q9: Does error 0x800f0982 affect Windows 10?
This error primarily affects Windows 11 versions 22H2 and 23H2, but it can occur on Windows 10 in rare cases with similar language pack conflicts.
### Q10: Should I use the Windows Update troubleshooter first?
Yes. The troubleshooter should be your first step before attempting advanced repairs like DISM or language pack removal.
### Q11: What is PSFX_E_MATCHING_COMPONENT_NOT_FOUND?
This is the internal error code for 0x800f0982. It indicates that Windows Update could not find a matching component in the WinSxS store for installed language packs.
### Q12: Can antivirus software cause error 0x800f0982?
Indirectly, yes. Antivirus software can interfere with file operations during update installation, potentially leading to component store corruption.
Related Articles
- How to Fix Windows 11 Update Stuck at Downloading
- Complete Guide to DISM and SFC Commands for Windows Repair
- How to Perform an In-Place Upgrade in Windows 11
- Windows 11 Cumulative Update Installation Guide for IT Admins
- Fix Windows Update Error 0x80073701 Component Store Corruption
Conclusion
Windows 11 update error 0x800f0982 is a component store mismatch issue that prevents cumulative updates from installing. The fix requires repairing the WinSxS store, removing conflicting language packs, and resetting Windows Update components. For most users, the combination of DISM /RestoreHealth, SFC /scannow, and language pack removal will resolve the problem. For persistent cases, an in-place upgrade provides the most comprehensive repair without data loss.
Enterprise IT administrators should deploy the PowerShell automation script provided in Step 12 to efficiently resolve this error across multiple workstations. Regular DISM maintenance and controlled language pack deployment will prevent recurrence.
If none of these methods resolve your issue, visit the BUSINESSROSHIYA troubleshooting section for additional Windows error fixes and IT support resources.