When a cumulative update fails once, it’s an incident. When it fails every single time — month after month, every KB, identical behavior — it’s a condition. Something on your HP laptop is permanently incompatible with the update process, and every update trips over it the same way. The good news hidden in this frustration: permanent blockers are findable. Transient glitches are the hard ones; constants leave evidence.

This guide is built for the every-time pattern specifically: how to identify the constant, the HP-specific usual suspects, and the order of operations that ends the loop. If your failures are intermittent rather than constant, our standard cumulative-update guide is the better fit.

Start building your evidence file now: for the last three failed updates, record the KB number, the date, the exact error code, and how far the install got before failing (download phase, install percentage, or rollback). Patterns in this data are diagnostic gold — same code every time means one broken subsystem; failures always at the same percentage mean a specific file or driver; failures getting progressively earlier suggest compounding damage. Bring this log to every fix below and you’ll stop guessing.

Why this happens

  • Permanently full recovery partition: Every cumulative update needs WinRE staging space; a full partition fails every one.
  • Broken update service state: A corrupted service registration or cache that never got cleared poisons every attempt.
  • Conflicting HP software: HP Support Assistant or HP drivers in a permanently conflicting state.
  • Ancient BIOS/firmware: Firmware predating the servicing requirements every update checks.
  • Third-party disk filter stuck installed: Encryption or AV filter drivers that every servicing operation chokes on.
  • Component store corruption: WinSxS damage that no cumulative update can install over.
  • Policy enforcement: A managed-device policy permanently blocking the servicing path.

How to fix it

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

Fix 1: Establish the pattern from Update history

Confirm the constant and capture the code.

  1. Settings > Windows Update > Update history — list the last 3+ failed updates with their codes.
  2. Same code every time (e.g., always 0x800f0922) points at one specific subsystem — 0x800f0922 means servicing prerequisites; 0x80070070 means space; 0x80070422 means the service.
  3. Different codes each time suggests compounding issues — still fixable, but work the full list below.

Fix 2: Fix the HP recovery partition problem

The most common permanent blocker on HP laptops.

  1. Open Disk Management and inspect the recovery partition — size and free space. HP’s factory layout often leaves the recovery partition nearly full from day one, which is why this blocker is so consistent on HP hardware specifically.
  2. In elevated Terminal, reagentc /info — if it reports disabled or errors, the WinRE setup is broken, which blocks cumulative servicing. A broken WinRE is itself worth fixing regardless of updates, since it’s your recovery lifeline.
  3. Free space or repair the WinRE configuration per Microsoft’s guidance at the Windows update support hub — do not delete the partition. Deleting it “fixes” the update block by destroying your recovery environment, which is a terrible trade.
  4. Retry the next update; recovery-partition blocks produce the most consistent every-time pattern, so one successful install here is strong confirmation you’ve found your constant.

Fix 3: Deep-clean the permanently poisoned cache

An every-time failure often means a cache that has never been truly cleared.

  1. Elevated Terminal: net stop wuauserv, net stop bits, net stop cryptsvc, net stop msiserver.
  2. Rename C:\Windows\SoftwareDistribution → SoftwareDistribution.old, catroot2 → catroot2.old.
  3. Also delete C:\Windows\Temp contents and run Disk Cleanup’s Windows Update Cleanup.
  4. Restart services, reboot, check for updates.

Fix 4: Update HP BIOS and drivers wholesale

Bring the firmware and driver stack into the supported era.

  1. From HP Support , install the latest BIOS, chipset, storage, and firmware for your exact model.
  2. Apply BIOS updates with the charger connected and never interrupt the flash.
  3. Restart and retry — outdated firmware is a classic every-time blocker because every update validates it.

Fix 5: Remove the permanent software conflict

Find what’s always in the way.

  1. Temporarily uninstall third-party antivirus, disk encryption, and system optimizers — not disable, uninstall.
  2. Disable HP Support Assistant’s scheduled tasks during update attempts.
  3. Retry the cumulative update with the minimum software footprint.

Fix 6: Repair the component store thoroughly

Every-time failures with servicing codes mean WinSxS damage.

  1. Elevated Terminal: DISM /Online /Cleanup-Image /RestoreHealth — if it fails, retry with a Windows 11 ISO mounted as /Source.
  2. sfc /scannow, restart, retry the update.

Fix 7: In-place upgrade to break the loop definitively

When the blocker hides from all diagnostics.

  1. Download the Windows 11 ISO from the Windows 11 download page .
  2. Mount, run setup.exe, Keep personal files and apps.
  3. The upgrade reinstalls the servicing stack wholesale — permanent blockers don’t survive it.

Closing

“Fails every time” is actually the most solvable update problem because the cause is a constant, and constants can be found. On HP laptops the usual constants are the recovery partition, old firmware, and HP software conflicts — clear those and Patch Tuesday becomes boring again. One clean install is all the proof you need that the loop is over.

After the breakthrough, protect it: note which fix worked (write it down — future you will thank present you), keep the recovery partition healthy, and update HP firmware proactively rather than reactively. Every-time failures don’t recur spontaneously; they recur when the same constant rebuilds itself — a refilled partition, a reinstalled conflicting utility, a firmware update you skipped. Stay ahead of your constant and the loop stays closed for good. Months from now, when Patch Tuesday comes and goes without incident, you’ll barely notice — and that quiet, boring success is the entire reward for the detective work you did today. If any failed attempt along the way left the machine stuck “undoing changes,” our undoing-changes recovery guide resolves that loop so you can get back to the real fix.

Frequently asked questions

What does 'fails every time' tell me that one failure doesn't?
It tells you the blocker is permanent, not transient. A one-off failure can be a glitch; an every-time failure means a fixed condition — a full partition, a conflicting driver, a broken service, a policy — that every update trips over identically. That actually makes it easier to fix: find the constant, remove it, and all updates start working.
Could my HP laptop just be too old for new updates?
Unlikely to be the whole story. If the laptop runs Windows 11, it meets the servicing requirements — age alone doesn’t block cumulative updates. What does block them on older HPs: outdated BIOS/firmware, ancient storage drivers, and small SSDs with no free space. Those are fixable, not fatal.
Will resetting Windows fix an every-time failure?
A reset usually does fix it, because it wipes the persistent blocker along with everything else — but it’s the nuclear option. The steps below find and remove the blocker surgically, which preserves your apps and settings. Reserve reset for when the blocker proves unfindable.
How do I know the blocker is really gone?
The next cumulative update installs cleanly on the first attempt. There’s no partial credit with every-time failures — either the constant is gone and updates work, or it isn’t and they don’t. One successful Patch Tuesday is your confirmation, and two in a row means the fix is durable rather than lucky.