Error Code 0x80070057: Every Fix, Every Scenario (Windows 10 & 11)

If you’ve ever been stopped dead in your tracks by error code 0x80070057, you know how frustrating it feels. You’re trying to update Windows, install software, back up your files, or plug in an external drive — and suddenly Windows throws this cryptic message at you: “The parameter is incorrect.”

The good news? This error is fixable. The bad news is that most guides online dump 10+ generic solutions on you without telling you which fix applies to your situation. This guide is different. We’ll diagnose the problem by scenario first, then give you the exact fix you need — without wasting your time.

What Does Error Code 0x80070057 Mean?

At its core, error code 0x80070057 is a Windows API error that translates to “The parameter is incorrect.” In developer terms, it maps to Win32 error 87 (ERROR_INVALID_PARAMETER) and its signed decimal equivalent is HRESULT –2147024809. If you’re an IT admin seeing that decimal value in Event Viewer or application logs, it’s the exact same error.

Windows throws this error whenever a system process or application passes an invalid, missing, or out-of-range parameter to a Windows API function. Think of it like giving the wrong input to a form field — Windows simply can’t process what it received.

The Different Error Messages You Might See

The same underlying error shows up with different text depending on where it occurs:

Context	Message You See
Windows Update	“There were some problems installing updates”
Windows Installation	“Windows could not format a partition on disk 0. Error code: 0x80070057”
Backup & Restore	“The backup did not complete successfully. Error: 0x80070057”
External Drive	“The parameter is incorrect” when opening a USB or SD card
Hyper-V	“One or more arguments are invalid. Error Code: 0x80070057”
WSL 2	“WslRegisterDistribution failed with error: 0x80070057”

Each message points to a different root cause and requires a different fix. That’s exactly why generic guides fail users — they treat all versions of 0x80070057 as the same problem.

What Causes Error Code 0x80070057?

Before jumping into fixes, it helps to understand the most common triggers so you can match your situation to the right solution:

• Corrupted Windows Update cache files — Downloaded update files become damaged before installation completes
• Damaged system DLLs or component store — Core Windows files are missing or corrupted
• Invalid or missing registry values — Registry entries pointing to Windows Update, VSS, or backup destinations contain bad data
• FAT32-formatted backup target — FAT32 drives cannot store files larger than 4 GB, instantly triggering the error during backups
• Incorrect disk partition style — MBR vs. GPT mismatch during Windows installation
• File system corruption on external drives — Caused by improper ejection, bad sectors, or physical connection failures
• Third-party software conflicts — Antivirus or security tools blocking certain Windows operations
• Insufficient disk space — Windows Update and backup operations need a substantial buffer of free space
• VSS (Volume Shadow Copy Service) misconfiguration — Particularly on volumes larger than 64 TB or in enterprise backup setups

Now let’s get to the fixes — organized by the scenario where you actually encountered the error.

Scenario 1: Error 0x80070057 During Windows Update

This is the most common context for this error. Here’s how to confirm it and fix it.

How to Confirm It

Open Event Viewer (search for it in the Start menu), navigate to Windows Logs → Application, and look for entries with the source “Windows Update” or “WUAUCLT” around the time of failure. You’ll see the 0x80070057 code listed alongside the failed component.

Fix 1: Run the Windows Update Troubleshooter

This is the fastest first step and resolves the problem in a large number of cases.

1. Press Win + I to open Settings
2. Go to System → Troubleshoot → Other Troubleshooters (Windows 11) or Update & Security → Troubleshoot (Windows 10)
3. Click Run next to Windows Update
4. Follow the on-screen prompts and restart when prompted

Fix 2: Clear the Software Distribution Folder

The Software Distribution folder is where Windows stores downloaded update files before installing them. When these files become corrupted — due to an interrupted download or unexpected shutdown — they trigger error code 0x80070057. Clearing the folder forces Windows to re-download the update cleanly.

1. Open Command Prompt as Administrator
2. Run the following commands one by one:

net stop wuauserv
net stop bits
net stop cryptsvc

3. Navigate to C:\Windows\SoftwareDistribution and delete all files and folders inside it
4. Restart the services:

net start wuauserv
net start bits
net start cryptsvc

5. Try Windows Update again

Fix 3: Run SFC and DISM

If clearing the cache doesn’t work, corrupted system files are likely the cause.

Open Command Prompt as Administrator and run:

sfc /scannow

Wait for it to complete, then run:

DISM /Online /Cleanup-Image /RestoreHealth

Restart your PC and attempt the update again.

Fix 4: Free Up Disk Space

Windows Update requires substantial free space — not just for the update files, but also because Windows stores a copy of your previous installation in a Windows.old folder. If your C: drive has less than 10 GB free, this is very likely your culprit. Run Disk Cleanup (search for it in Start), check all boxes including system files, and clear space before retrying.

Scenario 2: Error 0x80070057 During Windows Installation

When you see 0x80070057 during a clean install or upgrade, the message usually reads: “Windows could not format a partition on disk 0.” This is almost always a partition or disk configuration issue, not a file problem.

Fix 1: Delete and Recreate the Partition

During Windows Setup, on the partition selection screen:

1. Select the partition where Windows will be installed
2. Click Delete to remove it (your data will be lost — ensure backups are taken first)
3. Select the resulting Unallocated Space
4. Click New to create a fresh partition
5. Click Apply, then proceed with installation

Fix 2: Check MBR vs. GPT Compatibility

UEFI systems require a GPT disk, while older BIOS systems use MBR. A mismatch will trigger this error. To check and convert:

1. Boot from your Windows installation media
2. At the partition screen, press Shift + F10 to open Command Prompt
3. Type diskpart, then list disk
4. Note whether your disk shows an asterisk (*) in the GPT column
5. If conversion is needed, use convert gpt or convert mbr as appropriate (this erases all data on the disk)

Fix 3: Sync Date and Time

An out-of-sync system clock can quietly cause 0x80070057 during installation. Before starting setup, confirm your system date and time are correct in BIOS/UEFI settings.

Scenario 3: Error 0x80070057 in Windows Backup & Restore

Backup-related instances of this error are extremely common in both home and enterprise environments — and almost always come down to one of three specific causes.

Fix 1: Verify the Target Drive Is NTFS Formatted

FAT32 drives cannot store files larger than 4 GB, which means any full system image backup will immediately fail with error code 0x80070057. Right-click your backup destination drive in File Explorer, select Properties, and check the File System. If it says FAT32, you’ll need to format it as NTFS. Be aware that formatting erases all data on the drive.

Fix 2: Check VSS (Volume Shadow Copy Service)

Backup operations depend on VSS to capture a consistent snapshot of your data. If the service isn’t running, backups will fail.

1. Press Win + R, type services.msc, and press Enter
2. Find Volume Shadow Copy in the list
3. Right-click and select Start if it isn’t running
4. Set its Startup type to Manual

Fix 3: Inspect Registry Backup Parameters

For enterprise backup tools, the error frequently maps to an invalid registry entry. In Registry Editor (open with regedit), navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS

Look for entries with empty values or incorrect data types. Always export the key as a backup before making any changes.

Fix 4: Validate Backup Job Configuration

If you’re using third-party backup software, open the job configuration and verify that all source and destination paths still exist and are accessible. Renamed folders, disconnected network drives, or changed service account permissions are frequent culprits in enterprise environments.

Scenario 4: Error 0x80070057 on an External Drive, USB, or SD Card

When 0x80070057 appears the moment you try to open an external drive, the situation is different — and potentially more serious. This usually points to a physical or logical failure in the drive itself, not Windows.

What’s Actually Happening

File system corruption can occur when a drive is unplugged without being safely ejected, damaging the Master File Table (MFT) or NTFS structure. Physical issues like a frayed cable, a failing USB port, or an underpowered USB hub can also prevent Windows from passing correct parameters to the device.

Fix 1: Try a Different USB Port and Cable

Before assuming the drive is at fault, test it on a different USB port (preferably a USB 3.0 port directly on the motherboard, not a hub) and with a different cable if possible.

Fix 2: Run CHKDSK on the Drive

1. Open Command Prompt as Administrator
2. Run: chkdsk X: /f /r (replace X with your drive letter)
3. Allow it to complete — this may take a while for large drives

Fix 3: Consider Data Recovery First

If CHKDSK fails or the drive isn’t recognized at all, treat this as a potential data loss event. Do not continue running fix attempts if the data on the drive is irreplaceable. Contact a professional data recovery service before the situation worsens.

Scenario 5: Error 0x80070057 in Hyper-V

Power users and IT professionals running Hyper-V on Windows 10 or 11 Pro may encounter 0x80070057 when trying to enable Hyper-V through Windows Features or when attempting to start a virtual machine.

Fix 1: Verify System Requirements

Hyper-V won’t run if the system doesn’t meet minimum requirements. Confirm in Task Manager → Performance → CPU that Virtualization is shown as “Enabled.” If not, enable it in your BIOS/UEFI under Virtualization Technology (VT-x or AMD-V).

Fix 2: Re-enable Hyper-V via Command Line

Sometimes the Hyper-V components get partially corrupted. Open PowerShell as Administrator and run:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

Restart when prompted and attempt to launch the VM again.

Fix 3: Run SFC and DISM

As with Windows Update, corrupted system files can block Hyper-V from functioning. Run sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth and restart.

Scenario 6: Error 0x80070057 in WSL 2

Developers installing Linux distributions via WSL 2 (Windows Subsystem for Linux) may hit a WslRegisterDistribution failed with error: 0x80070057 message. This is a growing scenario on Windows 11 that no mainstream guide currently addresses.

Fix 1: Unregister and Reinstall the Distribution

Open PowerShell as Administrator:

wsl --unregister Ubuntu
wsl --install -d Ubuntu

Fix 2: Update WSL

wsl --update
wsl --shutdown

Then reinstall the affected distribution from the Microsoft Store.

Fix 3: Enable Required Windows Features

Ensure both Virtual Machine Platform and Windows Subsystem for Linux are enabled in Turn Windows features on or off (search for it in Start). Restart after enabling.

Scenario 7: Error 0x80070057 in Drive Optimization

Some users encounter 0x80070057 not in a dialog box, but quietly in Event Viewer — logged as “was not optimised because an error was encountered: The parameter is incorrect.” This appears when the scheduled Drive Optimization (defrag) task fails.

Open an Administrator Command Prompt and run:

fsutil behavior set disablelastaccess 0
fsutil behavior set disabledeletionnotify 0

Then retry optimization from Defragment and Optimize Drives in the Start menu.

General Fallback Fixes

If none of the scenario-specific fixes above resolved your issue, work through these general solutions in order — from least to most invasive.

Step 1: Perform a Clean Boot

A clean boot disables all third-party startup programs and services, helping identify whether a conflicting application is causing the error. Press Win + R, type msconfig, go to the Services tab, check Hide all Microsoft services, and click Disable all. Restart and test.

Step 2: Correct Your Date and Time

An out-of-sync clock disrupts several Windows services. Press Win + I, go to Time & Language → Date & Time, and click Sync now.

Step 3: Registry Repair for Windows Update

Navigate in Registry Editor to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update

Look for entries with missing or invalid values. Back up the key before editing anything.

Step 4: System Restore

If the error started recently and you have a restore point from before it began, restoring to that point will undo whatever change introduced the problem. Search for Create a restore point in Start, click System Restore, and follow the wizard.

Step 5: Reset or Reinstall Windows

This is a last resort. Use Settings → System → Recovery → Reset this PC and choose to keep your files if possible. A clean reinstall will resolve any software-based cause of error code 0x80070057 without exception.

Prevention: How to Avoid 0x80070057 in the Future

Scenario	Prevention Tip
Windows Update	Keep at least 15 GB free on your C: drive at all times
Backup & Restore	Always use NTFS-formatted drives for backup targets
External Drives	Always use “Safely Remove Hardware” before unplugging
Hyper-V / VSS	Validate VSS service status before running backup jobs
Enterprise Backup	Use backup software that validates job parameters before every run
WSL 2	Keep WSL updated with wsl --update regularly

Frequently Asked Questions

What does error code 0x80070057 mean?

It means “The parameter is incorrect” — Windows received an invalid, missing, or unsupported value when a system process or app tried to execute a task. It’s Win32 error 87 (HRESULT –2147024809).

Is 0x80070057 a serious error?

In most cases, no — it’s fixable without data loss. The exception is when it appears while accessing an external drive, which may indicate hardware failure requiring professional data recovery.

Which fix works most often for Windows Update?

Clearing the Software Distribution folder (Fix 2 in the Windows Update section) resolves the majority of 0x80070057 update errors, followed by running SFC and DISM.

Does 0x80070057 affect Windows Server?

Yes. The error appears in Windows Server 2016, 2019, and 2022 — particularly in Windows Server Backup jobs, VSS operations, and Windows Update for Business. The fix process mirrors the workstation steps: SFC, DISM, and validating VSS and backup job configurations.

Can antivirus software cause 0x80070057?

Yes. Some security tools — particularly older or overly aggressive ones — can block Windows API calls, resulting in this error. Temporarily disabling your antivirus and performing a clean boot are both valid diagnostic steps.

How long does fixing 0x80070057 take?

Most scenario-specific fixes take between 5 and 30 minutes. DISM repair can take up to an hour. A full reset or reinstall takes 1–2 hours but is rarely necessary.

What is HRESULT –2147024809?

It is the signed 32-bit decimal form of 0x80070057. Developers and IT admins often see this value in application logs and Event Viewer entries. Both values refer to the same underlying Windows error.

Can 0x80070057 cause data loss?

Not directly — the error itself doesn’t delete files. However, if it appears while accessing a failing external drive, the underlying hardware issue could lead to data loss if not addressed carefully.