Fix Windows Update Error 0x800f0982 in 3 Steps

What's Actually Happening Here

Error 0x800f0982 pops up when Windows Update can't finish installing a .NET Framework cumulative update or a language pack. I've seen it most often on Windows 10 version 2004 and 20H2 after a feature update, but it also hits Windows 11 occasionally. The error means the update files are corrupt or a component store entry is broken.

You'll see this in Settings > Update & Security, and the update usually fails at around 20-30%. Don't bother retrying the same update a dozen times — that won't fix the root cause. Work through these steps in order. Stop when the update installs cleanly.

Fix 1: Run the Update Troubleshooter (30 seconds)

Windows has a built-in troubleshooter that catches simple corruption. It's not a deep fix, but it's fast.

Open Settings (Win + I) > Update & Security > Troubleshoot.
Click Additional troubleshooters and select Windows Update.
Click Run the troubleshooter and let it finish.
Restart your PC and try the update again.

If the error still appears after this, move on. The troubleshooter usually just resets some Windows Update service buffers — it won't fix a deeply corrupted component store.

Fix 2: DISM and SFC Scan (5 minutes)

This is the real first step for 0x800f0982. DISM repairs the system image that Windows Update depends on. SFC then fixes individual system files that might be damaged.

Open Command Prompt as administrator. Right-click Start > Command Prompt (Admin) or Windows Terminal (Admin).
Run this command to check and fix the component store:
```
DISM /Online /Cleanup-Image /RestoreHealth
```
Wait for it to finish. It might take a few minutes. Don't close the window.
Then run:
```
SFC /SCANNOW
```
Restart your PC and try the update again.

Why this works: DISM rebuilds the component store from Windows Update sources (or from a local install.wim if you have one). SFC then fixes files like wuaueng.dll or .NET assemblies that got corrupted. I've fixed this error at least 10 times with just these two commands.

Fix 3: Manually Remove the Faulty Update (15+ minutes)

If DISM and SFC didn't help, the update itself is probably half-installed and stuck. You need to remove it manually, then reinstall via the Microsoft Update Catalog.

Write down the KB number from the failed update. It's in Settings > Update & Security > View update history. Look for the one that failed with 0x800f0982.
Open Command Prompt as administrator again.
Check if the update is installed but broken. Run:
```
wmic qfe list brief /format:texttablewsys
```
This shows all installed updates. Find your KB number in the list.
Uninstall it with this command (replace KB1234567 with your number):
```
wusa /uninstall /kb:KB1234567 /quiet /norestart
```
Wait for it to finish — might take 2-5 minutes. Then restart.
Download the same update from the Microsoft Update Catalog. Search for your KB number and pick the version matching your system (x64 or x86).
Run the downloaded .msu file to install it manually.

Why this works: Some updates get registered as installed but the files are incomplete. By removing it via wusa, you clear the bad registration. Then a fresh install from the catalog bypasses the broken Windows Update pipeline. I used this last week on a Windows 11 laptop that refused a .NET 6 update — worked first time.

When to Give Up and Reset

If none of these fix it, the update might be waiting for another update that's also broken. Check your update history for other failures with the same error. If there's a queue of failed updates, consider using the Windows Update Assistant to force a feature update to the latest version. That sometimes clears the backlog.

Last resort: run sfc /scannow again, then dism /online /cleanup-image /restorehealth — yes, again. Sometimes repeated runs fix deeper corruption. I've seen it take three passes to fully repair a .NET store issue.