Error 0x800f0989 is a close cousin of the other 0x800F servicing codes, and on HP laptops it almost always appears the same way: a cumulative update downloads fine, starts installing, then fails partway with this code. The download is innocent — the failure happens when Windows tries to assemble the update payload from its component store and discovers damaged or mismatched pieces.

HP machines add their own servicing load: HP driver packages and firmware updaters register components in the same store Windows servicing uses, so there are simply more transactions that can go wrong. The practical upshot is that this error responds to servicing-stack repair, not network tweaks — resetting your router will not help here.

The sequence below starts with quick automated checks, moves into DISM and SFC repair, and ends with manual installation and in-place upgrade options. Each step tells you how to confirm it worked before moving on.

Why this happens

  • Damaged payload assembly data: The servicing stack could not reconcile the downloaded package with the component store, usually due to manifest corruption.
  • Stale pending transactions: A previous update that never fully committed leaves transaction records that block new payload assembly.
  • HP driver components conflicting: HP-registered driver components in the store can mismatch what a cumulative update expects during assembly.
  • Corrupted update manifest: The XML manifest describing the update’s contents can be damaged in the local cache, derailing assembly.
  • Interrupted earlier servicing: A killed or power-cut servicing operation leaves half-written component data behind.
  • Disk errors under WinSxS: File-system damage in the component store area corrupts the pieces assembly needs.
  • Overaggressive cleanup tools: Third-party cleaners that prune servicing files can remove manifests future updates require.
  • Servicing stack itself outdated: An old servicing stack can fail to assemble payloads built for newer stack versions.

How to fix it

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

Fix 1: Run the Windows Update troubleshooter

The troubleshooter can clear stuck servicing registrations and reset update components automatically — a quick win when the damage is shallow. If the troubleshooter itself misbehaves, see How to fix driver updates failing in windows update step by step for a dedicated walkthrough.

  1. Open Settings, then System, then Troubleshoot, then Other troubleshooters.
  2. Run the Windows Update troubleshooter and apply its recommendations.
  3. Restart the laptop and retry the update.
  4. Continue below if 0x800f0989 persists.

Fix 2: Install the latest servicing stack update first

Payload assembly sometimes fails simply because the servicing stack is too old for the update format. Installing the newest servicing stack update manually can unblock everything downstream.

  1. Check Update history for any failed servicing stack updates.
  2. Search the {OUT3} for the latest servicing stack update for your Windows build.
  3. Download and install the x64 package, then restart.
  4. Retry the cumulative update.

Fix 3: Repair the component store with DISM

DISM restores the component inventory that payload assembly depends on. Run it with a stable connection so it can fetch clean replacement files from Windows Update.

  1. Open Terminal (Admin).
  2. Run: DISM /Online /Cleanup-Image /RestoreHealth
  3. Allow it to reach 100 percent without interruption.
  4. Note whether it reports success or failure — failure changes the plan later.

Fix 4: Run SFC to repair protected system files

With the store restored, SFC replaces damaged protected files that assembly also touches. This catches damage DISM’s store-level scan can miss.

  1. In the elevated Terminal, run: sfc /scannow
  2. Wait for the full scan to complete.
  3. Restart the laptop.
  4. Retry the cumulative update and watch for 0x800f0989.

Fix 5: Clear servicing temp files and reset the update cache

Stale staged payloads and a corrupted download index can both sabotage assembly. Clearing them forces every stage to start clean. Servicing concepts are explained further on Microsoft’s Windows support hub .

  1. Open Terminal (Admin) and run: net stop wuauserv, then net stop bits.
  2. Run: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
  3. Run: net start wuauserv, then net start bits.
  4. Check for updates and let the download complete fresh.

Fix 6: Update HP drivers and firmware before retrying

Outdated HP firmware or chipset drivers occasionally interfere with servicing. Use HP Support Assistant to bring them current, or browse HP’s official support site for your model’s latest packages.

  1. Open HP Support Assistant and install all offered driver and firmware updates.
  2. Restart when prompted — firmware updates require a full restart.
  3. After booting, retry the Windows cumulative update.
  4. Confirm whether the payload now assembles cleanly.

Fix 7: Finish with a manual install or in-place upgrade

If assembly still fails, either bypass the assembler with a standalone installer or replace the whole servicing stack. Choose based on what DISM reported earlier.

  1. If DISM succeeded: install the KB manually from the {OUT3}.
  2. If DISM failed: back up data and run a Windows 11 in-place upgrade, keeping files and apps.
  3. Restart and confirm the update in Update history.
  4. Run a final update check to confirm the queue is healthy.

Fix 8: Keep the servicing stack ahead of the updates it must assemble

Payload assembly failed once because the servicing machinery fell behind or got damaged. Keep it ahead from now on. The servicing stack updates itself through Windows Update, but on a machine with a history of failures it pays to confirm the stack is current before each Patch Tuesday rather than discovering it is stale when a cumulative update fails to assemble. HP Support Assistant timing matters too: let HP’s firmware and driver passes finish before Windows servicing begins its work, so the two never contend for the store.

  1. Before each Patch Tuesday, open Update history and confirm the latest servicing stack update installed.
  2. If a servicing stack update ever fails, install it manually from the Update Catalog before retrying cumulative updates.
  3. Run HP Support Assistant on the first of each month and let all firmware and driver updates complete fully.
  4. Never run HP updates and Windows Update simultaneously — serialize them, HP first, then Windows.
  5. Quarterly, run DISM ScanHealth to confirm the store assembly depends on is still clean.
  6. After every cumulative update, verify success in Update history; a failed assembly caught early is a ten-minute fix, caught late is an hour.

Closing

Once 0x800f0989 is resolved, keep servicing healthy on your HP laptop: install HP firmware updates before Patch Tuesday when possible, never interrupt an installing update, and skip third-party cleaners that touch servicing files. If related errors crop up, see How to fix windows update troubleshooter not working on laptop and How to fix metered connection blocking windows update — payload and store issues share root causes, and the repair discipline is the same.

Frequently asked questions

What does error 0x800f0989 mean?
It means Windows downloaded an update but failed while assembling the installable payload from its component store. The download itself is fine — the damage is in the servicing layer, such as corrupted manifests or a damaged component inventory. Repairs target DISM, SFC, and the servicing cache rather than the network.
How is 0x800f0989 different from 0x800f0988?
Both are servicing-layer failures, but 0x800f0988 points at general component store corruption while 0x800f0989 more specifically indicates payload assembly failure during a cumulative update install. In practice the repair sequence overlaps heavily: DISM, SFC, cache reset, then manual install or in-place upgrade.
Do I really need to update the servicing stack separately?
Usually Windows Update handles it automatically, but when updates are already failing, the stack update may be stuck in the same broken queue. Installing the latest servicing stack update manually from the Update Catalog breaks that deadlock and is a legitimate, Microsoft-supported step.
Can HP Support Assistant fix this error?
Not directly — this is a Windows servicing problem, not a driver problem. But updating HP firmware and chipset drivers first removes one variable, since outdated firmware has been known to interfere with servicing operations on some HP models. Run it before Patch Tuesday so firmware never becomes the variable that breaks assembly.