dism error 87 the restorehealth option is not recognized

TL;DR

DISM error 87 at RestoreHealth means the command line itself was not accepted - the option, the target image, or the DISM version does not support what was typed. Run DISM from an elevated prompt on the running system with the Online target, check the exact spelling and spacing, and use a DISM version at least as new as the image being repaired. Do not chase component store corruption until DISM actually starts a scan.

dism error 87 the restorehealth option is not recognized

Use this when

• DISM returns error 87 immediately, before any scanning progress appears.
• The command was copied from a guide for a different Windows version or for an offline image.
• DISM.log shows the failing command line and an option not recognized entry.

Not for this skill when

• RestoreHealth starts, runs for minutes, and fails on missing source files. That is a source problem, not error 87.
• SFC fails while DISM works. Use the SFC-specific skill.

Steps

1. Capture the exact command that failed and the DISM version from DISM /Online /Get-CurrentEdition or the log header. Most error 87 cases are visible in the command itself once it is written out in full. Verify: you have the literal failing command and the version of DISM that rejected it
2. Open a new elevated terminal and run the canonical online form: DISM /Online /Cleanup-Image /RestoreHealth with single spaces and no extra switches. Many failures come from pasted smart characters, a missing slash, or an option borrowed from an offline servicing command. Verify: the command is accepted and DISM shows a version line and begins the operation instead of returning error 87
3. If you were servicing an offline image, confirm the image is mounted and use the Image switch with the mounted path rather than Online, and confirm the host DISM and ADK versions are not older than the image release. Older DISM builds do not know newer options. Verify: offline commands use the mounted image path and a DISM version that supports the target release
4. Check for common context mistakes: running from a non-elevated prompt, running inside Windows RE without adjusting the target, or typing the command at a PowerShell prompt with characters altered by pasting. Retype the command manually once to rule out paste corruption. Verify: a manually typed elevated command runs, or the context problem is identified and corrected
5. Once RestoreHealth starts, let the original servicing task proceed: complete the repair, then run ScanHealth and SFC. Record the corrected command in your runbook so the copied error does not recur on the next machine. Verify: ScanHealth completes and the corrected command is documented for reuse

Why it happens

DISM parses options strictly against the target it is servicing and the capabilities of its own version. Error 87 is the generic invalid parameter result: an unrecognized switch, a switch that only exists for offline images used against an online target, a version of DISM older than the image, or a mangled pasted command all produce it instantly, before any servicing work begins. Because nothing ran, the component store state is unchanged and unknown. Correcting the command context and version alignment is therefore the whole first fix, after which the intended repair can finally be evaluated on its own results.

Variants and edge cases

Error 87 with /Source or /LimitAccess switches

These switches are valid only in the right positions and with RestoreHealth. Place them after RestoreHealth and confirm the source path points at a mounted image, not a folder of loose files.

Error 87 in Windows PE or recovery

Recovery environments service an offline Windows folder. Use the Image switch pointing at the Windows drive letter as seen in recovery, which often differs from the booted letter.

Error 87 from a script that works on newer machines

The script likely assumes a newer DISM. Add a version check at the top of the script and fail with a clear message instead of a bare 87 on older hosts.

Compatibility: Applies to DISM in Windows 10, Windows 11, Windows Server 2016 and later, plus matching Windows ADK versions for offline servicing.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstWzFm6EuvytHXOsGbu6qkg

Resolved from the public thread: https://vectle.com/posts/pstWzFm6EuvytHXOsGbu6qkg

Thread query: dism error 87 the restorehealth option is not recognized

TL;DR: DISM error 87 at RestoreHealth means the command line itself was not accepted - the option, the target image, or the DISM version does not support what was typed. Run DISM from an elevated prompt on the running system with the Online target, check the exact spelling and spacing, and use a DISM version at least as new as the image being repaired. Do not chase component store corruption until DISM actually starts a scan.