Patch Tuesday arrives, the cumulative update downloads, installs to some percentage — and fails. Next month, same story. On Windows 11 24H2, recurring cumulative update failures have a set of known causes, from the new checkpoint servicing model to the classic corrupted cache.

The good news about cumulative updates: each month’s package supersedes the last. You are never permanently behind — you just need one successful install to get current. The fixes below move from the fastest resets to manual installation, which succeeds even when Windows Update itself is the problem.

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

Why this happens

  • Corrupted update cache. Damaged download metadata or packages fail integrity verification every attempt.
  • Damaged servicing stack. Corruption in the component store breaks the install engine cumulative updates depend on.
  • Insufficient disk space. Staging and rollback data need 10+ GB of working room.
  • Third-party antivirus interference. Real-time protection can block servicing operations mid-install.
  • Stuck pending operations. A previous update’s unfinished work blocks the new one.
  • Checkpoint update chain broken. 24H2’s checkpoint model needs an intact baseline; a damaged baseline breaks the chain.
  • Corrupted system files. Damaged protected files fail the update’s pre-install checks.

How to fix it

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

Fix 1: Note the error code and check disk space

Open Settings, Windows Update, Update history, and record the exact error code on the failed cumulative update. Then check free space on C: in File Explorer — you want 10 GB minimum, 15+ ideally.

Error 0x80070070 means disk space, full stop — clean up first. Other codes point to servicing or download issues. This two-minute check prevents you from running servicing repairs when the problem is just a full SSD. If space is fine and the code is unclear, proceed — the next fixes cover the common cases regardless.

Fix 2: Run the Windows Update troubleshooter

Go to Settings, System, Troubleshoot, Other troubleshooters, and run the Windows Update troubleshooter. It is specifically good at the cumulative-update failure patterns: corrupted update database, wrong service states, and stuck pending.xml entries.

Apply all suggested fixes and restart. Then retry the update once. The troubleshooter resolves a meaningful share of recurring monthly failures on its own, particularly the “fails at the same point every month” pattern that suggests a stuck servicing operation rather than a bad package. If the download itself never completes, the Windows Update stuck downloading guide for 24H2 covers the delivery side.

Fix 3: Clear the update cache completely

A corrupted package poisons every retry until it is purged:

  1. Open Command Prompt as administrator.
  2. Run: net stop wuauserv
  3. Run: net stop bits
  4. Run: net stop cryptsvc
  5. Delete everything inside C:\Windows\SoftwareDistribution\Download and C:\Windows\System32\catroot2 (contents only, not the folders).
  6. Run: net start cryptsvc, net start bits, net start wuauserv
  7. Check for updates and let the cumulative update download fresh.

Do not pause the download. A clean, complete package eliminates an entire failure class. If the update fails identically on a fresh download, the issue is in the servicing stack, not the bits.

Fix 4: Repair the servicing stack with DISM and SFC

Cumulative updates live and die by the servicing stack. Repair it:

  1. Open Command Prompt as administrator.
  2. Run: DISM /Online /Cleanup-Image /RestoreHealth (10-30 minutes, needs internet).
  3. Run: sfc /scannow.
  4. Restart the laptop.
  5. Retry the cumulative update.

On 24H2 specifically, also consider DISM /Online /Cleanup-Image /StartComponentCleanup to clear superseded components that can confuse the checkpoint chain. When DISM and SFC both complete cleanly, the servicing engine is in a known-good state and the update’s install phase stops tripping over damaged infrastructure. Microsoft documents these tools in their Windows support resources .

Fix 5: Install the update manually from the Microsoft Update Catalog

When Windows Update itself is the failing component, bypass it. Go to the Microsoft Update Catalog , search for the KB number (from Update history), download the x64 package, and double-click the .msu file to install.

The Catalog serves the identical signed package through a manual channel — this is Microsoft’s official fallback, not a hack. Manual installation succeeds in a large share of cases where the automated path fails, because it skips the download-and-staging pipeline where the corruption lived. Restart when prompted and verify in Update history.

Fix 6: Temporarily disable third-party antivirus

Third-party antivirus products can interfere with servicing operations, particularly during the file-replacement phase. Uninstall (not just disable) the third-party antivirus using its removal tool, relying on Windows Security during the update.

Retry the cumulative update — via Windows Update or the manual Catalog package. If it succeeds, the antivirus was the blocker; you can reinstall it afterward, but check for an updated version first since the old one clearly conflicts with 24H2’s servicing. If the failure persists without antivirus, you have eliminated a major variable and the remaining suspects are servicing corruption (Fix 4) or pending operations.

Fix 7: Clear pending operations and consider an in-place repair

Check for stuck servicing work: open Command Prompt as administrator and run dism /online /get-packages — look for packages stuck in “Install Pending.” A pending restart that never completes blocks everything behind it; restart (fully, not fast-startup) and let it finish.

If cumulative updates have failed for months despite everything, do an in-place repair upgrade: mount the Windows 11 24H2 ISO from the official Microsoft download page , run setup.exe, choose “Keep personal files and apps.” This rebuilds the entire servicing stack while preserving your system, and monthly updates install cleanly afterward. For Lenovo-specific cumulative failures, the dedicated cumulative update failure guide for Lenovo laptops adds manufacturer angles.

Closing

Recurring cumulative update failures on 24H2 come down to a short list: corrupted cache, damaged servicing stack, tight disk space, or interfering antivirus. The troubleshooter and cache clear handle the quick wins, DISM/SFC rebuild the engine, and the manual Catalog install bypasses Windows Update entirely when it is the broken part. Remember that cumulative updates supersede each other — one successful install, by any method, puts you fully current.

Frequently asked questions

Can I skip a failed cumulative update and wait for next month?
Yes — cumulative updates are exactly that: cumulative. Next month’s update contains everything the failed one did, plus new fixes. Skipping is safe and often the pragmatic choice. But if updates fail repeatedly for months, the underlying servicing problem needs fixing, because eventually a future update will fail for the same reason.
Why do cumulative updates fail more on 24H2?
24H2 introduced a new servicing stack and checkpoint cumulative updates, which changed how deltas are computed and applied. Early in a Windows version’s life, servicing bugs are more common, and third-party software hasn’t fully adapted. Most of these issues get ironed out through later cumulative updates themselves — once you can install them.
Is it safe to install a cumulative update manually from the Catalog?
Yes, the Microsoft Update Catalog hosts the exact same signed packages Windows Update delivers. Download the update matching your architecture (x64 for most laptops) and install the .msu file by double-clicking it. It’s Microsoft’s official manual distribution channel, not a third-party workaround.
How much free space does a cumulative update need?
Plan for at least 10 GB free on C:, though the update itself is usually 300 MB to 1 GB. The servicing stack needs working room for staging, backup, and rollback data. Updates failing with 0x80070070 or late in the install almost always trace back to tight disk space — clean up before retrying.