If DISM shows 0x80070057 while installing or repairing Windows, the code means ERROR_INVALID_PARAMETER—“The parameter is incorrect.” Many searches write the code as 0X800070057, but that version contains an extra zero. Microsoft’s documented code is 0x80070057. Open an elevated Command Prompt, run DISM’s standard health-repair command, and then run System File Checker (SFC). If DISM cannot obtain files through Windows Update, provide a compatible Windows installation source and inspect the CBS logs for the exact missing component.
What 0x80070057 means in a DISM install
Microsoft’s error table defines 0x80070057 as ERROR_INVALID_PARAMETER, with the message “The parameter is incorrect.” The number itself does not identify one universal fault. DISM can return it when a command is mistyped, the shell lacks administrator rights, a repair-source path is wrong or unreadable, required files cannot be downloaded, or Windows has a damaged configuration. Windows Update also associates this code with corrupted files, permission problems, and incorrect system settings.
As an Amazon Associate I earn from qualifying purchases.
The spelling 0X800070057 in the title is therefore a transcription error rather than a separate DISM code. Compare the exact value displayed in the DISM output, Windows Update history, or the event that triggered the repair. A different hexadecimal code can require a different procedure.
Recommended Free Tools
Prepare an elevated Command Prompt
DISM changes protected Windows components, so run it from an administrator Command Prompt rather than an ordinary terminal window.
#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.
- Open the Start menu and type Command Prompt.
- Right-click Command Prompt and choose Run as administrator.
- Accept the User Account Control prompt. The window title should indicate an administrator session.
- Keep this window open until each command reaches 100 percent and returns to the prompt. Closing it midway can leave a repair incomplete.
Check every slash, space, and hyphen in the command. An invalid parameter can be caused by a small syntax change, such as omitting the slash before an option or joining two options together.
Run DISM with the default Windows Update source
Microsoft’s standard repair sequence starts with DISM. In the elevated Command Prompt, enter this command exactly:
DISM.exe /Online /Cleanup-image /Restorehealth- Press Enter and allow the scan to proceed. DISM may take several minutes, and the percentage can appear to pause while components are checked or replaced.
- Wait for a completion message before starting another repair command. The result may indicate that the operation completed successfully or that the component store could not be repaired.
- If DISM reports that source files could not be found, do not repeatedly rerun the same command. Continue to the alternate-source procedure below.
/Online targets the Windows installation currently running. /Cleanup-image tells DISM to service the component store, and /Restorehealth asks it to detect corruption and restore the required files. By default, DISM uses Windows Update as the source for those files, so this method depends on a functioning update client and usable network access.
Run SFC after DISM completes
Microsoft specifically recommends running DISM before System File Checker because DISM supplies the files SFC needs to repair protected system files. In the same elevated window, run:
sfc /scannow- Press Enter and leave the window open while verification advances to 100 percent.
- Read the final SFC message instead of assuming that a completed progress bar means every file was repaired.
SFC normally reports one of these outcomes:
- Windows Resource Protection did not find any integrity violations. No protected-file corruption was detected.
- Windows Resource Protection found corrupt files and successfully repaired them. Restart Windows and retry the operation that originally failed.
- Windows Resource Protection found corrupt files but was unable to fix some of them. Save the details from the CBS log and use them to identify the remaining component before attempting advanced repair.
Use a compatible repair source when Windows Update cannot provide files
If DISM says it cannot find source files, the online client may be damaged, blocked, or unable to supply the required payload. Microsoft provides this source-based pattern:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccessReplace C:RepairSourceWindows with the path to a known-good Windows repair folder. The source can be a running Windows installation, a Windows side-by-side folder on a network share, or removable media such as a Windows DVD. A legitimate Windows installation USB drive can also provide the files when its contents expose a usable Windows folder.
/Source tells DISM where to look, while /LimitAccess prevents it from trying Windows Update. The path must exist, be readable by the administrator account, and contain the files needed by the installed image. Match the source to the installed Windows edition, language, architecture, and build as closely as possible. A source that is incomplete or from a materially different build cannot compensate for a broken update client.
| Repair-source option | When it is appropriate | What to verify |
|---|---|---|
| Windows Update (default) | The computer can reach the update service and the update client is functioning. | Network access, update-service health, and administrator rights. |
| Local Windows folder | The running installation or another known-good installation contains the required side-by-side files. | Correct path, readable permissions, and matching edition, language, architecture, and build. |
| Network share | A trusted Windows side-by-side folder is available on another computer or server. | Share and NTFS permissions, connectivity, and a source that matches the target image. |
| Removable media or Windows DVD | The online client is blocked or damaged and compatible installation media is available. | Authentic, complete media and a Windows folder compatible with the installed image. |
Use the local or removable method when Windows Update connectivity is the failing part. It does not bypass an invalid path, missing payload, denied permission, or mismatched image. If the command still returns 0x80070057, record whether the failure occurs before the percentage counter starts, while accessing the source, or near completion; that timing helps distinguish syntax and access errors from missing component files.
Check the four common causes of “parameter is incorrect”
1. Command syntax
Re-enter the command from the documented form. Ensure DISM.exe is followed by a space, each option begins with /, and the source option has a colon immediately after /Source. Do not add quotation marks unless the actual path contains spaces and your shell requires them. A malformed option can be interpreted as an invalid parameter even when the underlying Windows image is healthy.
2. Missing elevation
An ordinary Command Prompt may be able to display DISM help but fail when it needs to modify protected files. Close it and reopen Command Prompt with Run as administrator. If User Account Control credentials are required, use an account authorized to service the installation.
3. Unavailable or unreadable source
Confirm that the folder in /Source is present, that the drive or network share is connected, and that the administrator account can read it. A disconnected USB drive, an unavailable share, or permissions that allow browsing but not reading the required files can all make a valid-looking path unusable.
Free tools Windows power users keep installed
One-click scans. No signup required.
4. Incorrect Windows configuration or corruption
Microsoft’s Windows Update guidance links 0x80070057 with corrupted files, permission issues, and incorrect system configurations. If the syntax, elevation, and source checks pass, use the logs rather than guessing at a single cause. The code is an indication to investigate the surrounding DISM or update message, not proof of one specific failure.
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]
When the error appears during Windows Update
If the same code is shown in Windows Update rather than directly by DISM, first note the exact update and the date in Settings > Windows Update > Update history. Generic messages such as “undoing changes” or “failure configuring updates” do not identify the repair needed; the numeric code in Update history is more useful.
- Run the built-in Windows Update troubleshooter from the Windows troubleshooting settings.
- Retry Windows Update after the troubleshooter completes.
- Restart when Windows requests it, then check Update history again for a changed code or a successful installation.
- If the error returns, run the DISM and SFC sequence from an elevated Command Prompt and inspect the logs described below.
A troubleshooter can correct update-service conditions, but it cannot make an incompatible repair image valid. If DISM identifies missing payload or manifest files, use a compatible local, network, or removable source instead of repeating the update indefinitely.
Read DISM, CBS, and SFC details
DISM and Component-Based Servicing record detected and repaired issues in the CBS logs. The principal files are:
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match%SYSTEMROOT%LogsCBSCBS.log%SYSTEMROOT%LogsCBSCBS.persist.log
Open them with an editor that can handle large text files, or copy them to another location before searching. Look for entries around the time of the failed command and note references to missing manifests, payload files, package identities, access-denied messages, or source paths. Those details tell you whether to correct permissions, replace the source, or investigate a particular component.
To extract SFC entries into a desktop file, run this command in the elevated prompt:
findstr /c:"[SR]" %windir%LogsCBSCBS.log >"%userprofile%Desktopsfcdetails.txt"Open sfcdetails.txt and match each timestamp to the SFC run. The file can contain entries from earlier scans, so use the dates and times to separate the current result from historical repairs.
What to do when the first repair attempt still fails
DISM fails immediately with 0x80070057
Stop and verify the command text, administrator status, and the exact error code. An immediate failure usually warrants correcting the invocation before changing the Windows image or downloading media.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →DISM reaches a percentage and then cannot find source files
Switch from the default Windows Update source to a known-good path using the source-based command. Confirm that the path contains the Windows files required by the installed edition and build, and that the drive or share remains connected for the entire scan.
SFC cannot repair all files
Keep the CBS log and the extracted SFC details. The names of the unrepaired manifests or payloads provide the next diagnostic target; rerunning SFC without correcting the underlying source generally produces the same result.
Windows Update continues to fail after repairs
Restart, run the Windows Update troubleshooter once more if it reports a fix, and check Update history for the specific code. If the code changes, investigate the new code rather than treating every failure as 0x80070057.
As an optional shortcut after these manual checks, Outbyte PC Repair can address more than 100 common Windows issues, including broken system elements, invalid redirects, shared DLL problems, settings that increase CPU, RAM or disk load, and temporary or cache-file cleanup. It includes vulnerability checks, a real-time boost, file shredder, and app-crash log, runs on Windows 11, 10, 8 and 7, and offers a free trial by category for at least two days before a paid subscription. It complements an antivirus rather than replacing one; results vary, and no tool repairs every crash.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Bottom line
Treat 0x80070057 as an invalid-parameter signal, not a diagnosis by itself. Use an elevated Command Prompt, run DISM.exe /Online /Cleanup-image /Restorehealth, follow it with sfc /scannow, and move to a compatible Windows source when Windows Update cannot supply repair files. Exact syntax, administrator permissions, source compatibility, and the CBS logs determine the correct next step.
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.
