0x80070057 Error Code

Question

0x80070057 Error Code

Ruscov Vladmir 40

error occurred in Windows Server 2022 when an incorrect parameter invalid value during a system operation, installation, update

0 comments

Answer accepted by question author

Ronald Sabiiti 1,505 Independent Advisor

Hello @Ruscov Vladmir

The error 0x80070057 “The parameter is incorrect” can occur for different reasons. Please try the following steps first:

Restart your computer and try the operation again.

Check that your drive has enough free space.

If the error occurs during Windows Update, go to Settings → System → Troubleshoot → Other troubleshooters → Windows Update, then select Run.

If the issue continues, open Command Prompt as an administrator and run the following commands one at a time:

DISM /Online /Cleanup-Image /RestoreHealth

Once it finishes, run:

sfc /scannow

Restart your computer and check whether the issue is resolved.

For additional guidance, please refer to Microsoft's documentation:

Troubleshoot Windows Update problems

Fix Windows upgrade and installation errors

If the error still appears, please let us know what you were doing when it occurred. This will help us narrow down the cause and recommend the right solution.

Best regards.

0 comments

1 additional answer

Your answer

Answer 1

Error 0x80070057 only means “The parameter is incorrect”; for a Windows Server 2022 installation or upgrade, run SetupDiag and inspect the Setup logs to identify the specific parameter or setup phase that failed before changing the system.

If this is an in-place upgrade

Do not repeatedly rerun Setup yet. Preserve the existing setup logs under:
- C:\Windows\Panther
- C:\$Windows.~BT\Sources\Panther
Open Command Prompt as Administrator and check whether Setup already generated this result:
```
   notepad C:\Windows\Logs\SetupDiag\SetupDiagResults.xml
```
Windows Setup includes SetupDiag and runs it automatically after an upgrade failure. Its result is normally stored at C:\Windows\Logs\SetupDiag\SetupDiagResults.xml. If it reports multiple failures, the last failure is typically the fatal one.^1^
If that file is absent or inconclusive, download the latest SetupDiag from the Microsoft page and run it from an elevated Command Prompt:
```
   mkdir C:\SetupDiag
   cd /d C:\SetupDiag
   SetupDiag.exe /Output:C:\SetupDiag\Results.log /Verbose
   notepad C:\SetupDiag\Results.log
```
Look for the matched rule, failing phase, operation, driver, application, or compatibility block—not just 0x80070057.^1^

Also examine the newest entries in:

   C:\Windows\Panther\setupact.log
   C:\Windows\Panther\setuperr.log
   C:\$Windows.~BT\Sources\Panther\setupact.log
   C:\$Windows.~BT\Sources\Panther\setuperr.log

Microsoft’s Windows Server upgrade procedure specifically directs failed upgrades to the Panther logs and SetupDiag.^2^

Before retrying, verify the upgrade prerequisites:
- The source-to-target version is a supported upgrade path.
- The target edition matches the intended licensing and media.
- The server is nonclustered when using the standard in-place procedure.
- There is a tested full backup and a maintenance window.
- The server meets target hardware requirements.
- Installed roles and applications support the target release.
- No VMs are running on the server during upgrade.
For non-Azure servers, mount the correct target ISO, run setup.exe, select the correct edition, and choose Keep files, settings, and apps.^2^

If Keep files, settings, and apps is unavailable, do not continue as a clean installation until the media edition, language, architecture, and supported upgrade path have been checked.

If this is a clean installation

If the error occurs specifically while selecting, creating, or formatting the destination disk:

Confirm that firmware/BIOS detects the disk.
Obtain the correct storage-controller driver from the hardware or VM vendor.
On Windows Setup’s disk-selection page, select Load Driver and provide that driver.
Check the disk for faults. From Setup, press Shift+F10, then run:
```
   chkdsk C: /f
```

Microsoft documents storage-controller drivers, firmware detection, and disk errors as relevant checks when Windows Setup cannot select or format a destination disk.^3^

Only for a clean installation, and only after backing up all required data, the destination disk can be erased with DiskPart. This permanently deletes every partition and all data on the selected disk.

diskpart
list disk
select disk <number>
detail disk
clean all
exit

Close Command Prompt, select Refresh on the disk-selection page, and rerun Setup. Do not use this procedure for an in-place upgrade.^3^

If SetupDiag does not identify the cause

Provide these items for further diagnosis or a Microsoft support case:

Source and target Windows Server versions and editions
Whether this is physical, Hyper-V, VMware, or Azure
SetupDiagResults.log or SetupDiagResults.xml
setupact.log and setuperr.log
The setup phase and percentage where failure occurs
Whether Setup rolls back or stops at disk selection

For Azure VMs, use the Azure-specific in-place-upgrade procedure rather than the standard installation-media method; Microsoft also provides Azure VM assessment and servicing-stack diagnostic tools.^4^

References