How to Fix Windows Error 0x80070057 (‘The Parameter Is Incorrect’)

Quick Fix

Start with the free disk space and Windows Update Troubleshooter - these fix the vast majority of cases in under a minute.

1. Check free space. Make sure your system drive (usually C:) has at least several GB free. Low space is the single most common cause.
2. Run the Windows Update Troubleshooter. Press Win + I, then go to System > Troubleshoot > Other troubleshooters (Windows 11) or Update & Security > Troubleshoot (Windows 10), and click Run next to Windows Update.
3. Restart and retry whatever action triggered the error (update, backup, install, or file copy).

Step-by-Step Guide

What this error means

Windows error code 0x80070057 is a Windows API error that translates to "The parameter is incorrect." Its signed decimal equivalent is HRESULT -2147024809. It is a generic Windows API error, which means it can originate from many different subsystems.

Common contexts include Windows Update failing to download or install updates, file or folder operations like copying, moving, or deleting, disk partition or formatting operations, and backup or restore jobs. The most common causes are a corrupted Windows Update cache, corrupted system files, a damaged Windows image, registry corruption, file system corruption, partition or GPT/MBR conflicts, and insufficient disk space.

Because the message is so generic, the right fix depends heavily on what you were doing when it appeared. Work through the causes below in order.

Cause 1: Windows Update is failing (most common)

This is the classic scenario - updates fail to download or install with 0x80070057.

1. Free up disk space. Error 0x80070057 often shows up along with Windows Update since update files can be large. Run Disk Cleanup (type it into the search bar, select your drive, and include Windows Update Cleanup files).
2. Run the Windows Update Troubleshooter. 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.
3. Reset the Windows Update cache manually. Open Command Prompt as administrator and run: net stop wuauserv, then net stop bits. Then navigate to C:WindowsSoftwareDistribution in File Explorer and delete all files and folders in the SoftwareDistribution folder (or simply rename it to SoftwareDistribution.bak). Also rename the Catroot2 folder the same way. Finally restart the services with net start wuauserv, then net start bits.
4. Check date and time. Check the date and time of your machine, and if possible sync it properly. Mismatched clocks can cause certificate and parameter validation errors during updates.
5. Check for a mapped/virtual drive conflict. Some users found the error was caused by a mapped network or virtual drive (e.g. a cloud-backed drive letter) confusing Windows Update; deleting that drive mapping allowed Windows Update to complete without issue, and one user traced it back to virtual drives mapped to a cloud storage bucket via third-party software.

Cause 2: Corrupted system files or Windows image

1. Run System File Checker. Open an elevated Command Prompt and run sfc /scannow. Wait for the scan to complete (5-15 minutes), do not close the window, review the results, and if SFC reports it found and repaired files, restart and test.
2. Run DISM if SFC alone does not fix it. In the same elevated prompt, run these in order: DISM /Online /Cleanup-Image /ScanHealth, DISM /Online /Cleanup-Image /CheckHealth, then DISM /Online /Cleanup-Image /RestoreHealth, followed by sfc /scannow again. Note these commands may need to be repeated 5-6 times to ensure the completeness of the scan.
3. Restart and retry the action that originally failed.

Cause 3: Backup or System Restore fails with this error

1. Check the target drive's file system. For backup errors, verify your target drive is NTFS-formatted with sufficient space - Windows Backup will not write to a FAT32-formatted drive.
2. Free up space on both source and destination drives. Failed Windows Backup or System Restore can happen because Microsoft's services detect an invalid file path or target drive and end the process.
3. Check the registry size limit (older Windows versions). The error message "An internal error has occurred: The parameter is incorrect: (0x80070057)" can appear because the registry is at its size limit — a batch of registry keys created in HKLMSoftwareMicrosoftdasetup during installation can hold many entries, and if the registry reaches its size limit, large entries won't be written. This requires a registry edit; back up the registry first or get help from Microsoft support if you are not comfortable editing it.

Cause 4: Installing Windows or formatting a partition fails

1. Recreate or reformat the target partition. Error code 0x80070057 when installing Windows 10 or 11 usually comes down to the target disk's partition layout rather than corrupted files, and the common fixes are recreating or formatting the target partition with DiskPart and resolving a GPT/MBR mismatch.
2. Do not convert MBR to GPT on a running system. Converting MBR to GPT is only relevant during installation, so do not apply it to an already running system.
3. Try a different USB port or re-create your installation media if the error appears very early in setup, since damaged install media can also trigger it.

Cause 5: Copying, deleting, or accessing files/folders

1. Check permissions. The error code 0x80070057 is often associated with permission issues, and can appear in different instances, such as when opening a folder or installing an application. Make sure you are signed in as (or running as) an administrator.
2. Run CHKDSK. Open an elevated Command Prompt and run chkdsk /r /f on the affected drive, then restart when prompted so it can scan on next boot.
3. Rule out third-party software. Antivirus, VPN clients, or storage drivers can intercept system calls and pass incorrect values to the Windows API. Temporarily disable third-party antivirus or try a clean boot to see if the error stops.

Cause 6: A failing or unstable hard drive/SSD

1. Watch for warning signs. Error code 0x80070057 can be a sign of a failing drive, especially when it repeats across many files or appears alongside clicking sounds, SMART warnings, CRC errors, or extremely slow transfers.
2. Test the drive in another machine if possible. A drive with bad sectors will often still show up in the BIOS yet prevent the operating system from booting, so testing the drive in another machine is the cleanest way to separate a logical fault from a mechanical one.
3. Stop running repair commands and back up data first if you suspect hardware failure. If the error is accompanied by clicking sounds, SMART warnings, or repeated failures across multiple files, the drive may be failing, and contacting professional hard drive data recovery services is far safer than running repair commands that can overwrite recoverable data. This is when you need help beyond normal troubleshooting - a data recovery specialist or hardware replacement, not more software fixes.

Cause 7: Group Policy or Outlook-specific instances

1. Check Group Policy settings. On Windows 10/11 Pro or Enterprise, a misconfigured Group Policy (for example disabling Windows Update-related services) can also throw this error - open gpedit.msc and review Windows Update policies under Computer Configuration > Administrative Templates.
2. Recreate your Outlook profile. Error 0x80070057 sometimes occurs because Outlook cannot communicate with the system to access data, and Outlook profiles can become corrupted due to improper shutdowns, hardware failure, software issues, or malware infections. Create a new Outlook profile via Control Panel > Mail if this is where you see the error.

When to get more help: If you have freed up space, run the troubleshooter, SFC, and DISM, and the error still recurs on every large update, or you notice physical drive symptoms (clicking, extreme slowness, SMART warnings), stop attempting more software fixes. Contact Microsoft Support for update-specific issues, or a professional data recovery service if hardware failure is suspected.