Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0x800F0984

0x800F0984 and 0x800F0988: delta patch errors when installing updates

10 min read Updated October 5, 2026 Windows Update & Setup

Fix it now

These are PSFX codes: component hydration and delta failures. 0x800F0984 means the matching component directory exists but the binary is missing; 0x800F0988 means an invalid combination of deltas. Repair the store, then install the update as a full package instead of an express one.

Run these in an elevated Command Prompt, in order, then reboot

DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
  1. Get the KB number of the failing update from Update history, then download the full standalone package for your exact edition, build and architecture from the Microsoft Update Catalog.
  2. Install that .msu directly and reboot. A full package does not have to reconcile against differentials, so it sidesteps the mismatch entirely.
  3. Confirm the build afterwards with winver and check the update reads as installed in Update history rather than failed.
  4. On a managed fleet, turn off express installation files on the update server so clients receive full payload.

Read the codes out of %windir%\Logs\CBS. The PSFX prefix on those log entries is your confirmation that this is a hydration problem rather than a download problem.

If the full package installs, you are done. If it fails as well, the store underneath is damaged and the next section explains how to tell.

Why it happens

An express update does not ship whole files. It ships differentials, and the client works out the smallest set it needs to reach the target version from whatever version the machine currently holds. Both a forward differential, to move to the new binary, and a reverse differential, to get back to a known base, are involved. That is what makes the download small and the client-side work substantial.

The scheme depends on the binaries on disk matching a state Microsoft generated differentials against. It also depends on hydration: the process of reconstituting a full binary from a base component plus deltas. When a file was replaced outside servicing, when a previous update applied partially, or when the store has drifted, the client cannot assemble what it needs and stops.

The four codes here say four different things, and v1 versions of this advice routinely blur them. 0x800F0984 is PSFX_E_MATCHING_BINARY_MISSING: the matching component directory exists but the binary is missing. 0x800F0982 is PSFX_E_MATCHING_COMPONENT_NOT_FOUND: no matching component could be identified for hydration at all. 0x800F0986 is PSFX_E_APPLY_FORWARD_DELTA_FAILED, which is the forward delta genuinely failing to apply.

0x800F0988 is the one most often described wrongly. It is PSFX_E_INVALID_DELTA_COMBINATION: an invalid combination of deltas, not a missing differential. If what you actually have is a failed reverse delta, the code for that is 0x800F0985, PSFX_E_APPLY_REVERSE_DELTA_FAILED, and if it is a failed forward delta it is 0x800F0986. Knowing which one you have is the difference between repairing a store and chasing a download.

The component store has drifted from what the deltas expect

You have this one if DISM /Online /Cleanup-Image /ScanHealth reports corruption, and the full package fails as well as the express one.

  1. Run DISM /Online /Cleanup-Image /RestoreHealth, supplying a source from media patched to at least the machine’s level if it cannot reach Windows Update.
  2. Follow with sfc /scannow.
  3. Reboot and install the full standalone package.
  4. Rescan the store afterwards to confirm the repair held.

A system binary was replaced outside servicing

You have this one if A security product quarantined a Windows file, or a vendor utility replaced one, shortly before the failures started.

  1. Restore the file from quarantine if the product still holds it, then rescan.
  2. Run sfc /scannow to put the file back from the component store.
  3. If sfc cannot repair it, repair the store first and run sfc again.
  4. Add the vendor’s documented exclusions so the same product does not quarantine the file again.

Do not copy system files from another machine. Versions and hashes have to match what the store expects, and a hand-copied file usually makes the next update fail as well.

Express installation files are enabled on the update server

You have this one if Every managed client fails at the same point while a machine going directly to Windows Update installs the same update without trouble.

  1. In your update server’s options, turn off the setting that downloads express installation files.
  2. Resynchronise and let clients pick up full packages on the next cycle.
  3. For clients already stuck, install the full package by hand to unblock them.
  4. Watch the next cycle to confirm the change took effect across the fleet.

A previous update applied only partially

You have this one if There is an outstanding restart, or DISM /Online /Get-Packages shows packages in a pending state.

  1. Restart fully and let servicing complete the pending work.
  2. Recheck the package list and confirm nothing is left pending.
  3. Only then retry the update.
  4. If a package stays pending across restarts, read CBS.log to find what is blocking it.

Repair does not clear it and the codes keep changing

You have this one if Each attempt produces a different PSFX code, and store repair reports success without changing the outcome.

  1. Stop repairing component by component. Microsoft’s documented escalation for this family is an in-place upgrade.
  2. Use media patched to at least the machine’s level, and keep files and applications.
  3. Back up first and confirm you hold any disk encryption recovery keys.
  4. Retest the update afterwards to confirm the store was the problem.

Full reference

Which layer to suspect

What you see Where the fault is
Only clients of an internal update server fail Express installation files are enabled on that server
The full package installs cleanly The store was fine; only the differential could not be matched
The full package fails too Component store corruption underneath the hydration failure
A security product recently quarantined a system file A binary was replaced or removed outside servicing
Different PSFX codes on each attempt Broad store damage; escalate rather than repairing one component at a time

The PSFX family, code by code

Code Published name Reading
0x800F0982 PSFX_E_MATCHING_COMPONENT_NOT_FOUND No matching component could be identified for hydration
0x800F0984 PSFX_E_MATCHING_BINARY_MISSING The matching component directory exists but the binary is missing
0x800F0985 PSFX_E_APPLY_REVERSE_DELTA_FAILED Applying the reverse delta failed
0x800F0986 PSFX_E_APPLY_FORWARD_DELTA_FAILED Applying the forward delta failed
0x800F0988 PSFX_E_INVALID_DELTA_COMBINATION An invalid combination of deltas

0x800F0985 and 0x800F0987 are not in this article’s list, but they sit in the same table on Microsoft’s page and are worth recognising when you meet them: a failed reverse delta and a failed null delta hydration respectively. If the code in your log is one of those, the diagnosis is the same and only the failing stage differs.

Commands for this one

Command Documented behaviour
DISM /Online /Cleanup-Image /ScanHealth Scans the image for component store corruption
DISM /Online /Cleanup-Image /RestoreHealth Scans for corruption and repairs it automatically
DISM /Online /Get-Packages /Format:Table Displays basic information about all packages in the image, including anything stuck pending
sfc /scannow Repairs live system files using the component store as its source

What the CBS log adds that the code does not

The codes are written into %windir%\Logs\CBS\CBS.log, and the PSFX-prefixed entries around the failure name the component that could not be hydrated. That name is what you take to the Microsoft Update Catalog, and it is also what tells you whether the same component is failing every month or whether the damage is spreading. Two failures on the same component point at something replacing that file. Failures on different components each month point at the store.

Where full packages come from

  • The Microsoft Update Catalog carries the standalone package for every published update, and each entry names an exact edition, build and architecture. Match all three; the closest available is not good enough.
  • A full package is only larger, not different. It installs the same update and leaves the machine in the same state.
  • Express delivery exists to save bandwidth on the wire. When it costs you a failed update every month it is not saving anything, and turning it off for the affected group is a reasonable decision.
  • Do not turn express delivery off across a large estate to unblock a handful of machines. Repair the stores on those machines first.

An in-place upgrade rewrites the operating system. Back up first, confirm you hold any encryption recovery keys, and allow for a long reboot cycle during which the machine is unusable.

Every code this article covers

Code What it points at Source
0x800F0984 PSFX_E_MATCHING_BINARY_MISSING: the matching component directory exists but the binary is missing Microsoft Learn
0x800F0988 PSFX_E_INVALID_DELTA_COMBINATION: an invalid combination of deltas. Not a missing differential; that is 0x800F0985 or 0x800F0986 Microsoft Learn
0x800F0982 PSFX_E_MATCHING_COMPONENT_NOT_FOUND: a matching component for hydration could not be identified Microsoft Learn
0x800F0986 PSFX_E_APPLY_FORWARD_DELTA_FAILED: applying the forward delta failed Microsoft Learn

Confirm the fix worked

  1. Confirm the update appears as installed in Update history rather than failed.
  2. Run DISM /Online /Cleanup-Image /ScanHealth and confirm no corruption is reported.
  3. Reboot and confirm winver shows the build the update was meant to deliver.
  4. Search %windir%\Logs\CBS\CBS.log for PSFX entries after the install and confirm there are none.
  5. Confirm the next update cycle completes without manual intervention.

Questions people ask about this

Does this mean my Windows installation is damaged?

Not necessarily. Hydration can fail on a machine whose store is perfectly healthy, simply because a binary is a version the deltas were not generated against. Run a store scan to find out rather than assuming the worst.

Is the full package worse than the express one?

Only in download size. It installs the same update and leaves the machine in the same state. Express delivery exists to save bandwidth, and when it costs you a failed update every month it is not saving anything.

What is the difference between 0x800F0988 and 0x800F0986?

0x800F0988 is an invalid combination of deltas: the pieces the client has do not go together. 0x800F0986 is a forward delta that was found and genuinely failed to apply. The reverse-delta equivalent is 0x800F0985. They look alike in a summary and point at different stages.

Do I need to buy anything?

No. The Microsoft Update Catalog, DISM and sfc are all free, and none of these codes relates to licensing or activation. This costs time, not money.

Should I turn off express updates everywhere?

Not as a reflex. It is a reasonable change when a group of machines consistently fails this way, and a poor one if you are dropping express delivery across a large estate to fix a handful of clients. Fix the stores on the affected machines first.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix 0x80D01001: Delivery Optimization cannot provide the download service Free Fix 0x800703F1 and 0x80070091: a corrupt registry hive or a folder that will not empty Free Fix 0x80072EE2 and 0x80072EFD: Windows Update times out reaching Microsoft License Error 0x80073712 and 0x800F081F: component store corruption blocking updates
โ† Back to Knowledge Base