Every cumulative update. Every month. Fails. Not sometimes — always. The update downloads, attempts, rolls back, and the next month’s does exactly the same thing. If that describes your laptop, you’re dealing with a permanent blocker: a fixed condition on your system that every servicing operation trips over. This guide is the universal, brand-neutral checklist for finding it.

The strategy is elimination in likelihood order: space, cache, services, conflicts, component store, then the definitive repairs. Each step removes one class of permanent blocker. Don’t skip — the steps are quick, and the one you skip is statistically the one that’s broken. For the HP-focused version with brand-specific angles, see our HP every-time guide .

A mindset note before you begin: resist the urge to combine fixes. It’s tempting to clear the cache, uninstall the antivirus, and run DISM all in one session — but if the update then succeeds, you’ll never know which fix mattered, and you won’t know what to watch for next month. Change one thing, test with the update, observe. Slower per step, faster overall, because you build actual knowledge about your machine instead of a lucky streak.

Why this happens

  • Chronic low disk space: The drive is always near-full, so every update fails staging.
  • Permanently poisoned cache: A corrupted SoftwareDistribution never cleared between attempts.
  • Broken update services: wuauserv or BITS in a permanently damaged state.
  • Ever-present software conflict: AV or filter drivers that are always installed, always interfering.
  • Component store corruption: WinSxS damage blocking all servicing.
  • Full system partitions: EFI or recovery partitions with zero free space, failing every update.
  • Failing storage hardware: Bad sectors corrupting servicing operations consistently.

How to fix it

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

Fix 1: Free space decisively

Chronic space shortage is the most common permanent blocker.

  1. Get 20 GB free on C: minimum — not 10, not “some”: 20.
  2. Settings > System > Storage > Temporary files — remove all safe categories including previous Windows installations.
  3. Uninstall unused apps and move personal data off the drive.
  4. Verify free space persists (not immediately eaten by temp files), then continue.

Fix 2: Nuke the update cache completely

Remove the poisoned state between attempts.

  1. Elevated Terminal: net stop wuauserv, net stop bits, net stop cryptsvc, net stop msiserver.
  2. Rename SoftwareDistribution and catroot2 with .old suffixes.
  3. Clear C:\Windows\Temp; run Disk Cleanup → Windows Update Cleanup.
  4. Restart all services and reboot.

Fix 3: Verify the update services are healthy

A permanently broken service fails every update identically.

  1. services.msc — Windows Update and BITS must exist, be set to Automatic/Manual (not Disabled), and stay running when started.
  2. If the service is missing entirely, see our missing-service restoration guide .
  3. If it won’t stay running, work our service-not-running guide before returning here.

Fix 4: Strip the software environment to minimum

Find the always-present conflict.

  1. Uninstall third-party antivirus, VPN clients with filters, disk encryption, and optimizers. Uninstall rather than disable — disabled security software frequently leaves kernel filter drivers loaded, which are the actual conflict source.
  2. Disconnect all USB peripherals; disable vendor update scheduled tasks. Check Task Scheduler for vendor tasks (Dell, HP, Lenovo, ASUS, Acer) that run at logon or on schedules — these are the “always present” part of the conflict.
  3. Retry the update in this minimal state — success here proves a software conflict. Then reinstall what you removed one item at a time, testing the update after each, to identify the specific offender rather than living without protection indefinitely.

Fix 5: Check the hidden partitions

EFI and recovery partitions fail every update when full.

  1. Disk Management → check recovery partition free space; reagentc /info to verify WinRE health.
  2. Mount the EFI partition (mountvol Y: /s) and check its free space.
  3. Address full partitions per Microsoft’s guidance at the Windows update support hub .

Fix 6: Repair the component store with source media

Deep WinSxS damage needs the heavy repair.

  1. Mount a Windows 11 ISO; elevated Terminal: DISM /Online /Cleanup-Image /RestoreHealth /Source:X:\sources\install.wim (X: = mounted ISO).
  2. sfc /scannow; restart; retry the update.

Fix 7: In-place upgrade, then hardware diagnostics

The final software answer, then the hardware check.

  1. ISO → setup.exe → Keep personal files and apps from the Windows 11 download page .
  2. If even the in-place upgrade fails the same way, suspect hardware: run the manufacturer’s SSD diagnostics and Windows Memory Diagnostic before anything else.

Closing

Permanent blockers surrender to systematic elimination — there are only so many constants on a system, and this checklist covers them all. Most people find theirs in the first four steps: space, cache, services, conflicts. Fix it once and the months of failed updates become a single successful Patch Tuesday, and then just… quiet. That’s the goal: updates so boring you forget they happen.

If you worked this entire checklist and updates still fail, don’t despair — you’ve done something valuable: you’ve eliminated every common cause, which means whatever remains is genuinely unusual (failing storage, deep registry damage, exotic policy). That elimination work isn’t wasted; it’s exactly what a professional technician would do before escalating, and it makes any further help — from a repair shop or a forum — dramatically more effective, because you can say precisely what you’ve ruled out. Systematic elimination never fails to produce useful information — even when it doesn’t produce the fix directly, it produces the map that leads to it. That’s never wasted effort. And the next time any update misbehaves — not just cumulative updates — you’ll have a proven diagnostic sequence to reach for instead of starting from zero. Write down what worked this time — that note becomes the first thing you check next time, and the second fix is always faster than the first.

Frequently asked questions

How is this different from the HP-specific every-time guide?
Same problem, brand-neutral approach. The HP guide leads with HP-specific suspects (recovery partition layouts, HP software, Sure Start); this guide works the universal checklist — space, cache, services, component store, conflicts — that applies to Dell, Lenovo, ASUS, Acer, and HP alike. Use this one if your brand’s specific guide doesn’t match your symptoms.
At what point should I stop troubleshooting and reinstall?
After the in-place upgrade step fails — which is rare. The checklist is ordered so the destructive options come last; most every-time blockers are found by step 4. A clean reinstall always works but costs you apps and settings, so it’s the final resort, not the plan.
Can a hardware problem cause every update to fail?
Yes — a failing SSD with bad sectors in system areas can corrupt every servicing operation identically, and bad RAM can corrupt downloads consistently. If software fixes all fail and SFC/DISM report unfixable corruption repeatedly, run your manufacturer’s storage diagnostics and a memory test before reinstalling.
Do I need to fix this urgently for security?
Yes — every missed cumulative update is a missed month of security patches, and the gap compounds. An every-time failure means you’ve likely missed several months already. Work the checklist promptly; each step is safe and the security payoff is real.