If DISM RestoreHealth returns 0x80070057, Windows is reporting ERROR_INVALID_PARAMETER—“The parameter is incorrect.” The code in this question, 0X080070057, has an extra zero and is not Microsoft’s standard spelling, so first copy the exact code from Command Prompt. Open an elevated Command Prompt, assess the component store, run the standard online repair, and then run System File Checker. If Windows Update cannot supply the repair files, repeat the repair with a known-good source that matches the installed Windows version, edition, architecture and language.
What DISM error 0x80070057 means
Deployment Image Servicing and Management (DISM) is built into Windows and repairs the component store used by the operating system. Its /RestoreHealth operation scans that image for component-store corruption and performs repair operations automatically. Microsoft defines 0x80070057 as ERROR_INVALID_PARAMETER, meaning “The parameter is incorrect.”
As an Amazon Associate I earn from qualifying purchases.
The number alone does not identify one universal cause. It can appear when a command was entered incorrectly, when the command is being run against the wrong image, when required repair content is unavailable, or when the component store has corruption. The correct remedy depends on the command, image and output that produced the error.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteFirst confirm the exact code and operating context
Check the spelling in the command output
Look at the complete DISM result rather than relying on a typed title or screenshot. The standard Microsoft code is 0x80070057. If your output shows another number, use that number when choosing a repair path. Also copy the command that was running when the failure occurred; an online repair, offline servicing operation, Windows Update task, backup, or system-image restore may require different handling.
#1 Best Overall
- Dual USB-A & USB-C Bootable Drive – compatible with nearly all Windows PCs, laptops, and tablets (UEFI & Legacy BIOS). Works with Surface devices and all major brands.
- Fully Customizable USB – easily Add, Replace, or Upgrade any compatible bootable ISO app, installer, or utility (clear step-by-step instructions included).
- Complete Windows Repair Toolkit – includes tools to remove viruses, reset passwords, recover lost files, and fix boot errors like BOOTMGR or NTLDR missing.
- Reinstall or Upgrade Windows – perform a clean reinstall of Windows 7 (32bit and 64bit), 10, or 11 (amd64 + arm64) to restore performance and stability. (Windows license not included.). Includes Full Driver Pack – ensures hardware compatibility after installation. Automatically detects and installs drivers for most PCs.
- Premium Hardware & Reliable Support – built with high-quality flash chips for speed and longevity. TECH STORE ON provides responsive customer support within 24 hours.
Record the useful details
- Your Windows version and build, including whether it is 32-bit or 64-bit.
- The exact DISM command and all text printed after it.
- Whether the operation targeted the running installation (
/Online) or an offline Windows image. - Whether the message mentions missing source files, access or permission problems, or an invalid parameter.
There is no reliable way to name the root cause from 0x80070057 alone. The build, command context and logs are needed to distinguish a syntax problem from component corruption or unavailable source content.
Open an elevated Command Prompt
- Open the Windows search box and type Command Prompt.
- Right-click Command Prompt and choose Run as administrator.
- Approve the User Account Control prompt.
Run the following commands in that administrator window. A non-elevated prompt can fail even when the syntax is correct.
Assess the Windows image before repairing it
Run CheckHealth
Enter:
DISM /Online /Cleanup-Image /CheckHealth
CheckHealth reports whether Windows has already flagged the image as corrupted. It is a quick assessment; it does not perform a full scan or repair.
Run ScanHealth
Enter:
DISM /Online /Cleanup-Image /ScanHealth
ScanHealth performs a deeper examination of the component store. Let it finish and save the resulting message. These checks are optional when you need an immediate repair, but they provide useful evidence if /RestoreHealth fails again.
Run the standard online RestoreHealth repair
For the currently running Windows installation, enter:
DISM.exe /Online /Cleanup-Image /RestoreHealth
The operation can take several minutes. Do not close the administrator window while it is working. The command asks Windows to obtain replacement components through its normal repair source and use them to repair the component store.
When DISM finishes, read the final result. A successful completion means the component-store repair operation completed; it does not by itself confirm that every protected system file is already correct. Continue with System File Checker.
Recommended Free Tools
Run SFC after DISM
In the same elevated Command Prompt, enter:
sfc /scannow
Wait until verification reaches 100 percent. The supported order is DISM first and SFC second: DISM repairs the component store that SFC uses as its source for protected Windows files.
After SFC reports its result, restart Windows if requested, then retry the operation that originally failed. Keep the SFC message because it indicates whether Windows found and repaired integrity violations or could not complete the check.
What to do when RestoreHealth cannot find repair files
A common failure path is that Windows Update cannot provide the content DISM needs. In that situation, give DISM a known-good local or network source from a matching Windows installation and prevent it from falling back to Windows Update.
Use a matching source
The source can be a repair folder, a mounted Windows image, a network share, a USB drive or a DVD. Match these attributes as closely as possible:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Windows version and build.
- Edition, such as the edition installed on the affected PC.
- CPU architecture.
- Display language.
A source from a different release or edition may not contain the component versions required by the target image. If you are unsure whether two installations match, record their version and build before attempting the repair rather than repeatedly trying an arbitrary source.
Run RestoreHealth with the source
For a repair folder at C:RepairSourceWindows, the documented pattern is:
Rank #2
- High-speed USB 3.0 performance of up to 150MB/s(1) [(1) Write to drive up to 15x faster than standard USB 2.0 drives (4MB/s); varies by drive capacity. Up to 150MB/s read speed. USB 3.0 port required. Based on internal testing; performance may be lower depending on host device, usage conditions, and other factors; 1MB=1,000,000 bytes]
- Transfer a full-length movie in less than 30 seconds(2) [(2) Based on 1.2GB MPEG-4 video transfer with USB 3.0 host device. Results may vary based on host device, file attributes and other factors]
- Transfer to drive up to 15 times faster than standard USB 2.0 drives(1)
- Sleek, durable metal casing
- Easy-to-use password protection for your private files(3) [(3)Password protection uses 128-bit AES encryption and is supported by Windows 7, Windows 8, Windows 10, and Mac OS X v10.9 plus; Software download required for Mac, visit the SanDisk SecureAccess support page]
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess
A mounted source can use the same pattern, for example:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsDISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:MountedWindows /LimitAccess
Replace the example path with the actual Windows directory in your source. The /Source option tells DISM where to obtain repair content. /LimitAccess stops DISM from contacting Windows Update, which is useful when Windows Update is unavailable or when you need to ensure that only the specified source is used.
If the source-based command still fails, check the exact path and permissions, verify that the source is complete and readable, and confirm that its version, edition, architecture and language match the target. A source error should not be treated as proof that the target installation is beyond repair.
Choose the repair route that matches your situation
| Situation | Command or route | What it depends on |
|---|---|---|
| Running Windows normally and no source error is shown | DISM.exe /Online /Cleanup-Image /RestoreHealth |
Windows’ normal repair source, commonly Windows Update |
| Windows Update cannot provide required files | /Source: with a known-good repair directory and /LimitAccess |
A readable source matching version, edition, architecture and language |
| Checking whether corruption is already flagged | DISM /Online /Cleanup-Image /CheckHealth |
The state recorded for the online image |
| Performing a deeper corruption assessment | DISM /Online /Cleanup-Image /ScanHealth |
Time for a full scan and the condition of the component store |
| Repair completed and protected files still need verification | sfc /scannow |
A functioning component store and an elevated prompt |
| Servicing an offline installation | Use the offline-image procedure for the exact image path, not /Online |
The image location, servicing context and matching repair source |
The table separates the online Windows image from an offline image. Do not substitute /Online when your original task was servicing a different installation; preserve the original context and inspect its output and logs.
Read DISM and CBS logs when the repair fails
When the command returns another error or repeatedly stops at the same stage, inspect the logs instead of issuing the identical command indefinitely. The relevant locations are:
%windir%LogsCBSCBS.log%windir%LogsDISMdism.log
Search the entries around the time of the failed attempt. They can identify a missing source component, the package or component that could not be repaired, an access problem, or a parameter that DISM rejected. Keep copies of the logs with the exact command and final error code if you need support or recovery assistance.
When the log points to a missing source
Recheck the source path and use a matching Windows image. If the source is on removable media or a network share, make sure it remains connected and readable for the entire operation. Then rerun the source-based command once the mismatch or path problem has been corrected.
When the log points to an invalid parameter
Compare the command character by character with the documented syntax. Check the spelling of /Online, /Cleanup-Image, /RestoreHealth, /Source: and /LimitAccess, and make sure a source path follows /Source: without an accidental extra character. Also confirm that you are using the command for the intended online or offline image.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →When the image is reported as non-repairable
Preserve the CBS and DISM logs and stop repeating the same repair command. Use Microsoft’s Windows recovery or reinstall guidance appropriate to your edition and installation context. Reinstalling or resetting Windows is a larger change than a component-store repair, so first protect important data and verify that the recovery path applies to the affected image.
Common mistakes that produce another 0x80070057 failure
- Using the mistyped number: searching for or troubleshooting
0X080070057instead of confirming the code printed by DISM. The documented code is0x80070057. - Running without elevation: opening Command Prompt normally rather than selecting Run as administrator.
- Skipping the command context: using an online command for an offline image, or diagnosing a Windows Update or backup failure as though it were a component-store repair.
- Stopping the process early: closing the window before DISM or SFC finishes verification.
- Using an incompatible source: pointing
/Sourceat media from another build, edition, architecture or language. - Assuming one successful command repairs everything: DISM and SFC perform different checks, so run SFC after DISM and then retry the original Windows operation.
- Ignoring the logs: repeating a command without checking
CBS.loganddism.logcan hide a source, permission or syntax problem.
A practical decision path
- Confirm that the output really says
0x80070057and note the command context. - Open an administrator Command Prompt.
- Run
CheckHealthandScanHealthif you need to establish whether corruption is flagged and to obtain deeper diagnostic information. - Run
DISM.exe /Online /Cleanup-Image /RestoreHealthfor the running installation. - After DISM finishes, run
sfc /scannowand wait for 100-percent verification. - If DISM reports that source files cannot be obtained, select a matching local, network, USB or DVD source and rerun RestoreHealth with
/Sourceand, when appropriate,/LimitAccess. - If the repair still fails, read both logs, correct the specific source, parameter or permission issue they reveal, and escalate to Windows recovery guidance when the image is non-repairable.
As an optional shortcut after these manual steps, Outbyte PC Repair can address more than 100 common Windows issues where possible, including broken system elements and shared DLL problems, while also offering settings tweaks, cleanup, privacy checks, vulnerability checks, a real-time boost, file shredder and crash log. It runs on Windows 11, 10, 8 and 7; a category-based free trial lasts at least two days before a paid subscription. It complements antivirus software rather than replacing it, results vary, and no tool repairs every crash.
When to stop troubleshooting
Stop and preserve the command output and logs when the image is identified as non-repairable, when the source cannot be matched, or when the operation was actually an offline servicing, backup or system-image task rather than an online repair. Those cases need the recovery procedure for the specific Windows image and operation. A precise diagnosis requires the exact build, command, final code and log entries; the number 0x80070057 by itself is not enough.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →
