Windows Update Error 0x800f0984 After a Cumulative Patch

Chang Min 60 Reputation points
2026-10-22T02:49:50.5366667+00:00

Several workstations fail to install a cumulative update with error 0x800f0984. How can I investigate component servicing, package applicability, and CBS logs to determine why the update cannot be applied?

Windows for business | Windows 365 Business
0 comments
Answer accepted by question author
Hoang Le Huy 1,600 Reputation points Independent Advisor
2026-10-22T03:21:31.35+00:00

Hello Chang Min,

Error 0x800f0984 usually indicates that the Windows servicing stack cannot successfully apply the cumulative update because of a component store inconsistency, package state mismatch, or an update applicability problem. The first place to investigate is C:\Windows\Logs\CBS\CBS.log, where you should look for entries containing 0x800f0984, Failed to resolve package, CBS_E_* errors, or messages indicating that a required package is missing, superseded, or in an invalid state.

You should also review C:\Windows\Logs\DISM\dism.log and verify the health of the component store (WinSxS). In many cases, cumulative update failures occur because the servicing stack detects corruption, incomplete pending actions, or inconsistencies between installed package metadata and the actual component store contents. Compare the affected systems against a healthy workstation running the same Windows build to confirm that the target cumulative update is applicable to that exact OS version and servicing level.

Additionally, check whether a previous Servicing Stack Update (SSU) or cumulative update failed and left the machine in a partially serviced state. The CBS log will typically show whether Windows considers the package not applicable, blocked by a prerequisite, or unable to commit due to component corruption. If corruption is identified, repair the component store first and then retry the cumulative update rather than repeatedly attempting the installation. In environments where multiple devices fail with the same error, focus on common factors such as the Windows build level, update source, servicing stack version, and identical CBS errors across the affected machines.

If my answer is useful for you, please hit Accept the answer for me please.

HL.

Was this answer helpful?

1 person found this answer helpful.
0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-10-22T02:50:09.33+00:00

    For 0x800f0984, focus on whether the failure is caused by component store corruption, a missing matching binary, or an update that cannot be applied to the current image state.

    1. Identify what the error means
      • 0x800f0984 is PSFX_E_MATCHING_BINARY_MISSING.
      • On Azure VMs, Microsoft classifies it as delta update corruption and points to component store repair or an in-place upgrade path.
      • Errors in this family are also listed among Windows Update failures that can require an in-place upgrade.
    2. Check package applicability first Use the standard applicability checks before going deeper into servicing:
      • Confirm the update is not already installed.
      • Confirm it has not been superseded by a newer update.
      • Confirm the package matches the OS version.
      • Confirm the package matches the processor architecture.
      • Confirm prerequisite updates are installed.
      These checks help rule out cases where the cumulative update is rejected because it does not apply to the current system state.
    3. Investigate component servicing state Microsoft’s Windows Update troubleshooting guidance ties servicing failures such as component store corruption to DISM and SFC repair steps. In an elevated Command Prompt, run: 
         Dism.exe /Online /Cleanup-Image /Restorehealth
   Sfc.exe /Scannow
      Then restart the device and try the update again. This is the documented mitigation for component store corruption-related update failures such as 0x800f0831, 0x800f081f, and 0x800f0825, and it is the supported component servicing investigation path in the provided guidance.
    4. Review CBS logging to determine the exact blocker For servicing-related failures, inspect the CBS log at: 
         C:\Windows\Logs\CBS
      The troubleshooting guidance for 0x800F0831 specifically recommends examining CBS.log to identify whether:
      • the update was never installed, or
      • the update is installed but some packages were not fully applied to the registry.
      It also points to the servicing packages registry location: 
         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages
      Use this to correlate package state with what CBS reports. Warning: registry changes are risky and can cause further servicing problems; use the key for inspection unless a documented repair action specifically requires modification.
    5. Interpret what to look for in CBS Based on the provided guidance, use CBS to determine whether the failure is due to:
      • missing package payloads or binaries,
      • partially applied packages,
      • package metadata or applicability mismatch,
      • broader component store corruption.
      If CBS shows corruption or missing servicing content that repair steps do not resolve, the documented Azure VM guidance for 0x800f0984 is to move to the in-place upgrade path.
    6. When to escalate to in-place upgrade If all applicability checks are correct, and DISM /RestoreHealth plus SFC /Scannow do not resolve the issue, Microsoft lists 0x800f0984 among errors that often require servicing stack repair or an in-place upgrade.

    A practical investigation flow is:

    1. Verify supersedence, installed state, architecture, OS version, and prerequisites.
    2. Run Dism.exe /Online /Cleanup-Image /Restorehealth.
    3. Run Sfc.exe /Scannow.
    4. Restart and retry the cumulative update.
    5. Inspect C:\Windows\Logs\CBS\CBS.log for missing payload, partially applied package, or corruption evidence.
    6. Inspect HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages to correlate package state.
    7. If corruption persists, use the in-place upgrade path documented for 0x800f0984-class failures.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.