When DISM reports “the cleanup-image option is unknown.”, the command has usually been parsed in the wrong syntax or against the wrong image context. Recheck every slash, space, and dash. Then confirm whether you are servicing the running Windows installation or an offline Windows folder. Do not jump to a reset or reinstall. The message does not prove that Windows is beyond repair.
Read the Command Literally Before Diagnosing Corruption
DISM separates global options, the target image, and servicing options. A valid online health check follows a recognizable pattern:
The forward slash is part of each option. A copied command may contain a typographic dash, a backslash, an invisible character, or a line break from formatted text. PowerShell aliases and third-party shells can also add ambiguity. Type the short command manually in an elevated Windows Terminal or Command Prompt rather than pasting a decorated version.
| Check | Incorrect example | Correct direction |
|---|---|---|
| Option prefix | -Cleanup-Image or \Cleanup-Image | Use /Cleanup-Image |
| Option spelling | /Cleanup Image | Keep the hyphen inside /Cleanup-Image |
| Target selection | Mixing /Online and /Image: | Choose one target context |
| Offline path | Pointing to a drive letter guessed in WinRE | Locate the actual Windows folder first |
| Executable | Running an unrelated or old copy named DISM | Verify the full executable path and version |
Run where dism in a normal Windows session. The expected system copy is normally under the Windows system directories. If a deployment kit or old utility folder appears first in the path, call the current Windows copy explicitly. Do not delete other tools until you know why they are present.
Choose Online Windows or an Offline Image, Not Both
Use Online for the Windows installation currently running
The /Online switch refers to the operating system that launched DISM. It does not mean “use the internet.” For a running Windows 11 or Windows 10 installation, start with:
If DISM recognizes the option, continue with /ScanHealth when a deeper assessment is needed. Microsoft documents /RestoreHealth for repairable images and allows a matching repair source to be specified. The official Repair a Windows Image guidance shows the supported order and syntax.
Use Image for a Windows folder that is not currently running
In Windows Recovery Environment, the visible system may be WinRE rather than the installed Windows copy. In that case, /Online targets WinRE. It may not expose the same servicing features or packages. Locate the offline Windows volume and use an explicit path:
Replace D:\ only after verifying it. The installed system drive often receives a different letter in WinRE. A guessed drive can point to installation media, a recovery partition, or another volume. That mistake may produce an option error, path error, or an irrelevant result.
Map Drive Letters Safely in Windows Recovery Environment
Open Command Prompt from Advanced options. Use diskpart, then list volume, only to view volumes. Exit DiskPart without running clean, format, create, or conversion commands. Those operations write storage metadata and can destroy access to files.
Check likely letters with a read-only directory command such as dir D:\Windows. A genuine installed Windows folder should contain familiar subfolders such as System32. Also verify BitLocker status. An encrypted or locked volume must be unlocked with the correct recovery information before DISM can service it meaningfully.
If the Windows volume is missing, shows RAW, reports the wrong capacity, or produces read errors, stop command repair. These symptoms shift the problem from DISM syntax toward storage access. Protect data before running file-system repair or rebuilding boot structures. The inaccessible boot-device recovery sequence explains that boundary.
Confirm That the DISM Version Supports the Target
Run DISM.exe /? and DISM.exe /Online /? in the relevant environment. Help output shows which options that executable accepts. A servicing tool from an older deployment environment may not understand a newer image. Likewise, a 32-bit process, customized recovery environment, or vendor rescue shell may redirect system paths unexpectedly.
Match the servicing environment to the Windows generation and architecture when practical. If you booted from installation media, use current Microsoft media for the installed release. Do not download a random dism.exe from a file-sharing site. The executable depends on companion servicing components; copying one file rarely creates a trustworthy repair environment.
Separate an unknown option from a missing repair source
An unknown /Cleanup-Image option occurs before DISM evaluates a repair source. Errors about source files, component-store corruption, or error 0x800f081f belong to a later stage. Do not add a long /Source path until the basic /CheckHealth form is accepted. Solving one layer at a time keeps the evidence clear.
Protect Personal Files Before Reset, Reinstall, or Disk Repair
A DISM syntax error alone does not delete documents. Data risk appears when troubleshooting escalates to CHKDSK, registry changes, partition work, Reset this PC, or a clean installation. Check ordinary backups first. If Windows still starts, copy important user folders to an external disk and verify several files. If it does not start, use a safe boot environment or recovery workflow that avoids writing to the source.
Drecov provides a Windows recovery path when local files are missing or inaccessible before that escalation. It can work with PCs, HDDs, SSDs, external disks, USB drives, SD cards, and memory cards. Supported data categories include photos, videos, documents, emails, audio, and archives. Its read-only recovery mode, Quick Scan, Deep Scan, filters, preview, and separate-destination recovery are useful for protecting files before a reset. Lost Partition Recovery can search a stable lost-partition case, while Crashed PC Recovery applies to supported nonbooting scenarios. Neither mode repairs DISM or physical storage damage.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
Step 1: Open Drecov and select the original file location
Run PandaOffice Drecov from a healthy Windows environment. Do not install it on the partition containing missing files. Select the original Windows partition, affected disk, or suitable crashed-PC or lost-partition mode. Confirm the disk capacity and location before scanning.
Step 2: Start Quick Scan and check expected user folders
Run Quick Scan first. Inspect Desktop, Documents, Pictures, project folders, and other known paths. File names and former locations may make the best candidates easier to identify. If the disk disconnects, clicks, changes capacity, or develops severe read errors, stop scanning and seek imaging or professional recovery.
Step 3: Continue with Deep Scan only on stable media
Use Deep Scan when Quick Scan does not locate the necessary files and the source remains stable. The broader read workload is inappropriate for a physically unstable disk. Drecov cannot correct mechanical failure, electrical damage, or fully overwritten data.
Step 4: Filter results and preview representative files
Narrow results by file type, former location, name, size, or date where available. Preview representative documents, images, videos, and archives. Preview confirms only the displayed sample. It cannot guarantee every page, frame, linked asset, or archive member.
Step 5: Recover to another healthy disk and verify
Save selected files to a different healthy device, never to the source partition. Check the Drecov Folder or Recovery Folder if output is not where expected. Open a sample from every important file group and compare sizes. For critical archives, create a verification record using the SHA-256 file-check procedure. Resume DISM, CHKDSK, reset, or reinstall work only after the recovered data is usable.
Retry DISM in a Controlled Order
Return to the shortest valid command. For running Windows, test DISM.exe /Online /Cleanup-Image /CheckHealth. For an offline installation, verify the letter and use /Image:<path>. If the option is now accepted, capture the exact output before progressing to /ScanHealth or /RestoreHealth.
Keep the diagnosis tied to the original symptom. DISM services the Windows component store; it does not repair an application document, media file, or physically failing disk. If Windows starts normally but one personal file will not open, use a file-specific diagnosis instead. These Windows corrupted-file checks help separate an individual damaged file from a system-wide servicing problem.
Specify a repair source only when DISM asks for one or the documented repair path requires it. The source must match the installed Windows edition, architecture, language, and servicing level closely enough for the operation. After DISM completes successfully, run System File Checker if appropriate, restart, and review Windows Update and the original symptom. A successful command is not proof that personal files are intact, so verify those separately.
If the same unknown-option message persists with a verified current executable and correct target, save the DISM log and exact environment details. That evidence is more useful to an administrator than a list of commands already tried. Avoid registry “fixes” that do not explain why the parser rejected the option.
Also note whether the error appears in normal Windows, Safe Mode, WinRE, installation media, or a vendor recovery environment. Record the full command, the prompt path, and the first lines of DISM.exe /?. Those three details usually reveal a context mismatch faster than another repair attempt.
Conclusion
“The cleanup-image option is unknown.” normally calls for syntax and context checks before component-store repair. Type the command manually, distinguish /Online from /Image:, map WinRE drive letters, and verify the DISM executable. Protect files before any reset, reinstall, partition change, or CHKDSK operation. When important local data is already missing or inaccessible, Drecov can scan a stable source, preview recoverable files, and save them to another healthy disk before system repair continues.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
