TL;DR: Windows error code 0x80070057 means “The parameter is incorrect” (HRESULT -2147024809). It blocks Windows Update, software installs, and backup jobs across Windows 10, Windows 11, and Windows Server. Fix it by running the Windows Update Troubleshooter, then sfc /scannow, then DISM /RestoreHealth. For backup errors, verify your target drive is NTFS-formatted with sufficient space. This guide covers every scenario from quick 2-minute fixes to advanced registry repair.
What is Windows Error Code 0x80070057?
Windows error code 0x80070057 is a Windows API error that translates to “The parameter is incorrect.” Its signed decimal equivalent is HRESULT –2147024809. The error fires when a Windows process or application passes an invalid, missing, or out-of-range parameter to a system function.
Affected systems: Windows 7 · Windows 10 · Windows 11 · Windows Server 2016 / 2019 / 2022
Quick Fix Summary: Top 5 Fastest Solutions
Not sure where to start? Use this table to jump directly to the fix that matches your situation.
| Fix | Best For | Difficulty | Time |
|---|---|---|---|
| Windows Update Troubleshooter | Failed Windows Update | Easy | 2 min |
| Run SFC /scannow | Corrupted system files | Easy | 5–15 min |
| Run DISM /RestoreHealth | Deep Windows image corruption | Easy–Medium | 10–20 min |
| Registry Parameter Correction | Backup / install errors | Advanced | 15 min |
What Causes Error Code 0x80070057?
Error 0x80070057 is a generic Windows API error, which means it can originate from many different subsystems. The most common root causes are:
- Corrupted Windows Update cache: Damaged or incomplete files in the SoftwareDistribution folder cause the update engine to pass invalid parameters
- Invalid or missing registry parameter: The most frequent cause in backup software and enterprise tools. A registry key references a path or value that no longer exists
- Damaged system files (.dll, .sys, .exe): Corrupted Windows system files cause any operation that depends on them to fail with an invalid parameter error
- Third-party software conflict : Antivirus, VPN clients, or storage drivers intercepting system calls and passing incorrect values to the Windows API
- Disk full or insufficient permissions: File copy or backup operations fail when the target location runs out of space or the process lacks write permission
- Unsupported file system (FAT32 target): Windows Backup and most imaging tools require an NTFS-formatted target drive; FAT32 triggers 0x80070057
- Incorrect regional or locale settings: In some Windows versions, misconfigured date/time format settings cause parameter mismatches in certain installers.
Common Scenarios Where Error 0x80070057 Appears
Here are the most common contexts in which you will encounter this error across Windows 7, Windows 10, and Windows 11:
- Windows Update: The error 0x80070057 can occur when Windows Update encounters issues with downloading or installing updates
- File or Folder Operations: It can appear when copying, moving, or deleting files, often pointing to a file system or permissions problem
- Disk Management: When working with disk partitions or storage configurations, it may indicate issues with formatting, resizing, or creating partitions
- Backup and Restore: If performing a system backup or restore, the error often relates to backup settings, target drive format, or insufficient space
- Windows Installation: During a Windows installation or upgrade, it can occur due to issues with installation media, partition style, or hardware compatibility
- Software Installation: Third-party application installers can trigger this error when they encounter invalid registry values or missing system libraries
How to Fix Error Code 0x80070057 – Step by Step
Work through the following fixes in order. Stop as soon as the error is resolved.
Fix 1: Run the Windows Update Troubleshooter
The built-in troubleshooter automatically detects and fixes most Windows Update-related causes of error 0x80070057.
- Press Windows + I to open Settings.
- Go to System → Troubleshoot → Other troubleshooters (Windows 11) or Update & Security → Troubleshoot → Windows Update (Windows 10).
- Click Run next to Windows Update.
- Follow the on-screen prompts and apply any fixes suggested.
- Restart your computer and attempt the update again.
Fix 2: Run SFC /scannow to Repair System Files
System File Checker (SFC) scans and repairs corrupted Windows system files that may be passing invalid parameters.
- Press Windows + S, type cmd, right-click Command Prompt, and select Run as administrator.
- Wait for the scan to complete (5–15 minutes). Do not close the window.
- Review the results. If SFC reports it found and repaired files, restart and test.
Type the following command and press Enter:
sfc /scannow
Fix 3: Run DISM to Restore Windows Image Health
DISM repairs the underlying Windows component store – run this after SFC if the error persists.
- Open Command Prompt as Administrator (same steps as Fix 2).
- Run the following command:
DISM /Online /Cleanup-Image /RestoreHealth - Wait for the process to complete (10–20 minutes). Internet connectivity is required.
- After DISM completes, run sfc /scannow once more, then restart.
Fix 4: Reset Windows Update Components
Clearing the SoftwareDistribution and Catroot2 folders forces Windows Update to rebuild its component cache cleanly.
- Open Command Prompt as Administrator.
- Stop Windows Update services by running these commands one at a time:
net stop wuauservnet stop cryptSvcnet stop bitsnet stop msiserver - Rename the corrupted folders:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.oldren C:\Windows\System32\catroot2 Catroot2.old - Restart the services:
net start wuauservnet start cryptSvcnet start bitsnet start msiserver - Restart your PC and retry Windows Update.
Fix 5: Scan and Repair Disk Errors (CHKDSK)
Run Check Disk to detect and repair bad sectors or file system errors on your storage drive.
- Open Command Prompt as Administrator.
- Run: chkdsk C: /f /r
- If prompted that the disk is in use, type Y to schedule the scan at next restart.
- Restart your computer and allow CHKDSK to complete before Windows loads.
Fix 6: Registry Cleanup (Advanced)
In backup software and enterprise tools, error 0x80070057 often maps to a corrupt or missing registry parameter. Use this fix with caution – back up your registry first.
- Press Windows + R, type regedit, and press Enter.
- Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update
- Look for any entries with invalid data types or empty values – these indicate the corrupted parameter.
- For backup-related errors, check: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS
- If unsure, export the key first (File → Export) before making any changes.
- Correct or delete the invalid value, then restart the related service.
- Note: If you are not comfortable with registry editing, use a trusted IT professional or back up your system before proceeding.
Fix 7: Additional Checks
- Scan for Malware: Run a full system scan using your antivirus software to rule out malware causing invalid API calls.
- Update Device Drivers: Ensure disk controller and storage drivers are up to date, especially after a major Windows update.
- Check Hardware: If you suspect hardware issues, run diagnostics on your hard drive (CrystalDiskInfo) and RAM (Windows Memory Diagnostic).
- Verify Regional Settings: Go to Settings → Time & Language → Region and ensure the format matches your locale – some installers are sensitive to this.
How to Fix Error 0x80070057 During Windows Update
When error 0x80070057 appears specifically during a Windows Update installation, the most effective targeted fix sequence is:
- Run the Windows Update Troubleshooter first (Fix 1 above).
- Reset Windows Update Components by clearing SoftwareDistribution (Fix 4 above).
- After restarting, go to Settings → Windows Update → Check for updates and attempt the update again.
- If a specific cumulative update keeps failing, manually download it from the Microsoft Update Catalog and install via the standalone installer.
- Run DISM /RestoreHealth followed by SFC /scannow if the above steps do not resolve the issue.
Windows Update error 0x80070057 is most common after interrupted update downloads or when the SoftwareDistribution folder has grown corrupt over multiple failed attempts.
How to Fix Error 0x80070057 During Software Installation or Download
When this error appears during a third-party application install or download, it is typically caused by a conflicting registry value, insufficient disk space, or a corrupted installer package.
- Verify disk space: Ensure the target drive has at least 2× the size of the installer as free space. Clear temporary files using cleanmgr if needed.
- Run the installer as Administrator: Right-click the installer and select Run as administrator to ensure it has write access to all required locations.
- Download the installer again: A partially downloaded or corrupt installer file commonly triggers 0x80070057. Re-download from the official source.
- Temporarily disable antivirus: Security software occasionally intercepts installer API calls and causes parameter errors. Disable it briefly during installation and re-enable immediately after.
- Run SFC /scannow: Corrupted system DLLs that the installer depends on will generate this error. Fix 2 above addresses this.
- Check Windows Installer service: Open Services (services.msc), find Windows Installer, and ensure it is set to Manual and is running.
How to Fix Error 0x80070057 in Backup Software
Error 0x80070057 is one of the most common errors in Windows backup tools – including Windows Server Backup, and third-party backup solutions like BDRShield. In backup contexts, it almost always means the backup target has an unsupported file system or an invalid configuration parameter.
- Verify the target drive is NTFS-formatted: FAT32 drives cannot store files larger than 4 GB and will immediately trigger 0x80070057 on any full system image. Format the target to NTFS if needed.
- Check available disk space: Ensure the target drive has more free space than the total size of the data being backed up.
- Validate backup job configuration: Open your backup software settings and verify that all source and destination paths are valid, accessible, and have not been renamed or moved.
- Check VSS (Volume Shadow Copy Service): Open Services (services.msc), find Volume Shadow Copy, and ensure it is set to Manual. Start it manually and retry the backup.
- Review backup software logs: Most enterprise backup tools log the exact registry or API parameter that failed – use this to pinpoint the invalid value.
Using a purpose-built backup solution that validates parameters before running jobs prevents this error class entirely. BDRShield’s free Windows Workstation Backup includes pre-flight configuration validation to catch these issues before they cause a backup failure.
How to Fix Error Code 0x80070057 on Windows 10
On Windows 10, error 0x80070057 is most commonly triggered by Windows Update (particularly cumulative updates) and by system image backups. Follow this Windows 10-specific sequence:
- Go to Settings → Update & Security → Troubleshoot → Windows Update → Run the troubleshooter.
- If the error persists, open an elevated Command Prompt and run:
net stop wuauserv && ren C:\Windows\SoftwareDistribution SoftwareDistribution.old && net start wuauserv - Run sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth.
- Check that Windows Update service is set to Automatic in services.msc.
- If the error appears during a Windows 10 backup, ensure the target drive is NTFS and has sufficient free space (at least the size of your OS partition).
- For persistent errors, try the Windows 10 Media Creation Tool to perform an in-place upgrade repair without losing data.
How to Fix Error Code 0x80070057 on Windows 11
On Windows 11, error 0x80070057 appears most frequently during cumulative update installations and when using imaging or backup applications. The Windows 11-specific fix path is:
- Go to Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run.
- If the troubleshooter finds nothing, open an elevated Command Prompt and run:
- Run sfc /scannow after DISM completes.
- Verify that your Windows 11 installation meets TPM 2.0 and Secure Boot requirements – update mismatches sometimes surface as parameter errors.
- For installation errors on Windows 11, check that the target partition is GPT (not MBR). Windows 11 requires UEFI with GPT.
- Clear the Windows Update cache using Fix 4 above and retry.
DISM /Online /Cleanup-Image /StartComponentCleanup followed by:
DISM /Online /Cleanup-Image /RestoreHealth
Understanding HRESULT -2147024809 and “The Parameter Is Incorrect” (0x80070057)
Developers and system administrators frequently see this error in event logs or application output in its decimal form rather than hex. Here is what both values mean:
| Hex Error Code | 0x80070057 |
|---|---|
| HRESULT (Decimal) | -2147024809 |
| Win32 Error | ERROR_INVALID_PARAMETER (87) |
| Error Message | The parameter is incorrect. |
| Affected Systems |
Windows 7, 10, 11, Server 2016 / 2019 / 2022 |
When you see HRESULT -2147024809 in an application log, an event viewer entry, or a developer stack trace, it is the same error as 0x80070057. The Windows API uses this code whenever a function receives a parameter value it cannot process – a null pointer where a value is expected, a file path that exceeds the MAX_PATH limit, a size value that is zero or negative, or a handle that refers to an already-closed resource.
In enterprise backup and replication tools, this most often means a backup job is referencing a volume, path, or service account that has changed since the job was last configured.
Prevent Backup Errors with BDRShield – Free Windows Workstation Backup
The best way to avoid recurring 0x80070057 backup errors is to use backup software that validates job parameters before every run. BDRShield’s free Windows Workstation Backup supports up to 10 workstations at no cost and includes:
- Backup of the entire workstation or selected disks/volumes
- Supports MBR and GPT partitioned disks and drives larger than 2 TB
- Supports both Basic and Dynamic disks on Windows Workstations
- Application-consistent backups with Microsoft application quiescing
- Flexible storage: local disk, NAS, SAN, or cloud (S3, Azure Blob, Google Cloud, Wasabi, MinIO)
- AES 256-bit encryption both in-flight and at rest
- Pre-flight parameter validation to catch configuration errors before they cause job failures
Frequently Asked Questions
1. What does Windows error code 0x80070057 mean?
Windows error code 0x80070057 means “The parameter is incorrect.” Its HRESULT decimal equivalent is -2147024809. It appears when a Windows process or application passes an invalid, missing, or unsupported parameter to a system API function. It is triggered by Windows Update failures, software installation errors, backup job misconfigurations, and file system operations.
2. What causes error 0x80070057 in Windows 10 or Windows 11?
The most common causes are corrupted Windows Update cache files, damaged system DLLs, invalid or missing registry values, FAT32-formatted backup target drives, incorrect disk partition style (MBR vs GPT), and third-party software or antivirus interference. In enterprise environments, changed file paths or service account permissions in backup jobs are frequent triggers.
3. How do I fix error 0x80070057 quickly?
For the fastest resolution: run the Windows Update Troubleshooter (Settings → Troubleshoot → Windows Update), then run sfc /scannow in an elevated Command Prompt, followed by DISM /Online /Cleanup-Image /RestoreHealth. For backup errors, verify the target drive is NTFS-formatted and has sufficient free space.
4. Can Windows Update cause error 0x80070057?
Yes, it is one of the most common sources. Error 0x80070057 occurs when Windows Update files in the SoftwareDistribution folder are incomplete or corrupted, or when update services fail to pass valid parameters to the installer. Resetting Windows Update components (stopping services, renaming SoftwareDistribution, restarting services) typically resolves it.
5. Is error 0x80070057 related to backup failures?
Yes. It is among the most frequently encountered backup errors in Windows. It commonly appears when the backup target uses an unsupported file system (FAT32 cannot hold files above 4 GB), when the target drive lacks space, or when a backup job references a volume or path that has changed. Formatting the target to NTFS and reconfiguring the backup job resolves most cases.
6. What is HRESULT -2147024809?
HRESULT -2147024809 is the signed 32-bit decimal representation of the hexadecimal error code 0x80070057. Both values refer to the same Windows API error: ERROR_INVALID_PARAMETER (Win32 error 87), which means “The parameter is incorrect.” Developers and IT admins see this decimal value in application logs, event viewer entries, and developer stack traces.
7. Does error 0x80070057 affect Windows Server?
Yes. Error 0x80070057 affects Windows Server 2016, 2019, and 2022 particularly in Windows Server Backup jobs, Volume Shadow Copy Service (VSS) operations, and Windows Update for Business deployments. The fix process is identical to the workstation steps: SFC, DISM, and validating backup job configurations and VSS service status.
8. How do I fix 0x80070057 ‘the parameter is incorrect’ in backup software?
In backup software, this error almost always means the target drive is FAT32 (format it to NTFS), the backup target path has changed or become inaccessible, or a registry parameter pointing to the backup destination is invalid. Open your backup software’s job configuration, verify all paths and credentials, check VSS service status, and confirm the target drive has more free space than your backup size.
Download BDRShield for on-premise backup (or) Sign up for BDRShield Cloud Backup.
Follow our Twitter and Facebook feeds for new releases, updates, insightful posts and more.