Error 0x800F0831 is Windows Update telling you it is missing a puzzle piece: the update you want requires another package that is not installed. Most often that missing piece is a servicing stack update — the behind-the-scenes component that installs other updates. Without it, the main update cannot proceed, and you get this code instead of progress.

The repair has two halves: install the missing prerequisite directly, and fix whatever broke the automatic prerequisite chain so it does not happen again. Both are straightforward once you know the sequence.

Every Windows update is part of a chain: it expects certain earlier packages — most often the servicing stack update — to already be installed, and it verifies that expectation before proceeding. Error 0x800F0831 is what happens when a link in that chain is missing. Windows Update is designed to pull prerequisites automatically, so a missing link means something interrupted the design: a corrupted update database that lost track of installed packages, a metered connection that skipped the prerequisite, or a previous install that failed halfway. The repair restores the missing link and fixes the tracking so the chain stays intact.

Why this happens

  • Missing servicing stack update: The SSU that the cumulative update requires was never installed.
  • Skipped prerequisite: A metered connection or paused updates prevented the prerequisite from arriving.
  • Corrupt update database: The data store lost track of which packages are installed, breaking dependency resolution.
  • Failed earlier install: A previous update that partially failed left the servicing state inconsistent.
  • Out-of-order manual installs: Installing updates manually in the wrong sequence breaks the chain.
  • Damaged component store: Corruption prevents the servicing stack from recognizing installed prerequisites.
  • Stale update cache: Corrupt metadata hides available prerequisites from the engine.
  • Language pack dependencies: Missing language-specific prerequisites can trigger the error on some configurations.

How to fix it

Work through these in order — diagnose first, then act.

Order matters in the fixes below in a way it does not for most update errors: install the servicing stack update before the cumulative update, not after. The cumulative package checks for the servicing stack during installation, so reversing the order just reproduces the error. SSU first, cumulative second, every time.

Fix 1: Install the latest servicing stack update

The missing prerequisite is most often the SSU — install it directly.

  1. Identify your Windows 11 version and build with winver.
  2. Search the Microsoft Update Catalog for the latest servicing stack update for your build.
  3. Download and install the SSU .msu package, then restart.
  4. Retry the original failing update afterward.

Fix 2: Install the latest cumulative update manually

The newest cumulative package often resolves the chain in one move.

  1. Find the current month’s cumulative update KB for your Windows 11 version.
  2. Download it from the Microsoft Update Catalog.
  3. Install the .msu and restart when prompted.
  4. Check update history to confirm both the SSU and cumulative update are recorded.

Fix 3: Reset the Windows Update components

Repair the database that lost track of installed packages.

  1. In an admin Command Prompt, stop the services: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
  2. Rename the folders: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old.
  3. Restart the services with net start for each.
  4. Reboot, then check for updates and let the engine rediscover prerequisites.

Fix 4: Repair the component store

Fix the servicing foundation so dependency checks work correctly.

  1. Run DISM /Online /Cleanup-Image /RestoreHealth in an admin Command Prompt.
  2. Follow with sfc /scannow.
  3. Restart after both complete.
  4. Retry the update sequence: SSU first, then cumulative.

Fix 5: Check the CBS log for the exact missing package

When the general approach stalls, the log names the missing piece.

  1. Open C:\Windows\Logs\CBS\CBS.log after a failed attempt.
  2. Search for 0x800f0831 or “failed” near the failure time.
  3. Note the package or KB name mentioned alongside the error.
  4. Download and install that specific package from the Update Catalog.
  5. For deeper component-store issues, our 0x80070490 guide covers the advanced repairs.

Fix 6: Run the Windows Update troubleshooter

The automated tool can repair the metadata behind broken dependency chains.

  1. Open Settings, System, Troubleshoot, Other troubleshooters.
  2. Run the Windows Update troubleshooter and apply its fixes.
  3. Restart and check for updates.

Fix 7: Clear metered connection and pause blocks

Make sure nothing is preventing prerequisites from arriving automatically.

  1. Turn off the metered connection toggle on your active network.
  2. Unpause updates if they are paused in Windows Update settings.
  3. Click Check for updates and allow the engine to pull the full prerequisite chain.
  4. Install offered updates in the order presented.

Fix 8: Perform an in-place upgrade for stubborn cases

When the servicing state is too tangled, rebuild it while keeping everything.

  1. Download the Windows 11 ISO from Microsoft’s software download page.
  2. Mount the ISO and run setup.exe, keeping files and apps.
  3. The in-place upgrade installs the current build with a clean servicing state.
  4. Afterward, Windows Update should process new updates without dependency errors.

To keep the prerequisite chain healthy going forward, avoid interrupting updates mid-install and be cautious with manual installations done out of order — both are classic ways to break the chain. If you install updates manually from the Catalog, always check the KB article’s prerequisite list first; Microsoft documents them clearly, and two minutes of reading prevents exactly this error. A Windows Update database that accurately tracks installed packages is the quiet machinery behind every smooth Patch Tuesday. For installing those prerequisites directly, our manual installation walkthrough covers the Catalog process step by step.

Closing

Error 0x800F0831 is a dependency problem wearing an error code costume. Install the servicing stack update, follow with the cumulative update, repair the database that lost track — and the chain completes itself. Future updates will then pull their prerequisites automatically, as intended.

Frequently asked questions

What does error 0x800F0831 mean?
It means the update you are trying to install depends on another package that is not present on the system — typically a missing servicing stack update or an earlier cumulative update. Windows Update is supposed to pull prerequisites automatically, but when the chain breaks, the install fails with this code. The fix is to identify and install the missing prerequisite manually.
How do I find which update is missing?
Check the CBS log at C:\Windows\Logs\CBS\CBS.log for the package name associated with the failure, or note which KB failed and check Microsoft’s documentation for its prerequisites. Servicing stack updates are the most common missing piece. Installing the latest servicing stack update for your Windows build before retrying resolves many cases.
Can I just install the latest cumulative update to fix it?
Sometimes. Cumulative updates are, as the name suggests, cumulative — the latest one contains everything before it. But the missing piece is often the servicing stack update, which is separate from the cumulative update and must be installed first. Installing the newest SSU and then the newest cumulative update is the reliable sequence.
Why didn't Windows Update install the prerequisite automatically?
Usually because of a corrupted update cache, a broken update database that lost track of installed packages, or a previously failed install that left the servicing state inconsistent. In rarer cases, the prerequisite was offered but skipped due to a metered connection or a paused update window. Repairing the update components restores the automatic chain.