PC Error Codes Look up a code
One safety rule: if a message shows a phone number to call, it is a scam: Microsoft never does that. Check any warning in 5 questions.

Home › Windows Error Codes › Error 0x80070057: The Parameter Is Incorrect

Error 0x80070057: The Parameter Is Incorrect

By Editorial Team · · 9 min read

0x80070057

“The parameter is incorrect”

In plain English: Error 0x80070057, 'The parameter is incorrect,' means Windows was handed a setting or value it could not accept. Windows stopped the task instead of guessing.

First safe step: Restart the computer properly. Select Start > Power > Restart, not Sleep, and do not just close the laptop lid.

Error 0x80070057, 'The parameter is incorrect,' means Windows was handed a setting or value it could not accept. Windows stopped the task instead of guessing. It does not mean your files are lost, and it does not mean your whole computer is broken.

That same code points to different problems. During Windows Update, it usually points to a corrupted or invalid update download. During a backup, restore, or copy to a drive, it is more likely the destination drive or a backup setting. The fix for one will not fix the other.

So do not start with a long list of repairs. The next step below asks where you saw the error, in an update, a backup, or an install, and sends you to only that section. Follow that one path, and skip the rest.

Start Here: Did 0x80070057 Appear During Update, Backup or Install?

Before you try any fix, take a minute to remember exactly where you saw the message. That one detail points to the likely cause and to the right fix, and it keeps you from changing settings that have nothing to do with your problem. The same code can mean a bad update download in one case and a problem with a backup drive or setting in another.

Was it in Windows Update, perhaps after you clicked Check for updates or while an update was installing? Was it in Windows Backup, File History, or while you were making a system image? Or did it show on a Windows setup screen or while you were installing a program? Pick the one that matches.

Write down what you can, exactly as you saw it. If a KB number appeared next to a failed update, copy that number. If you were backing up, note the destination drive, its name or letter, and whether it is external. Also note what you clicked, or what Windows was doing, just before the error appeared. Keep that note in front of you as you read on.

Then use the repeat pattern as your guide. If the error comes back only when a particular update tries to install, follow the Windows Update section below. If it appears only when that external backup drive is connected, follow the backup section. If it happened during an install, use the install section. Follow only that section.

Three Quick Checks That Apply in Every Case

Before you split into the update or backup fix, try these three checks first. They take a few minutes and they rule out causes that can trigger 0x80070057 in either case.

  1. Restart the computer properly. Select Start > Power > Restart, not Sleep, and do not just close the laptop lid. Plug a laptop into power, wait until Windows loads fully, then try the same update or backup once more.
  2. Check the clock. Open Settings > Time & language > Date & time and confirm the date, time, and time zone are correct. A wrong clock can make a valid update or backup look invalid to Windows.
  3. Check space and connections. Open File Explorer > This PC and confirm the Windows drive, usually C:, has space free. For a backup, check the destination drive too. Then unplug extra USB drives, memory cards, and other devices, leaving only the drive your task needs. If the error returns, go to only the section that matches your task.

Fix It When It Happens During Windows Update

Stay on this path if 0x80070057 appeared in Windows Update. Leave backup settings alone for now, because the cause here is the downloaded update itself. Open Settings > Windows Update > Update History, find the failed update, and write down its KB number exactly as shown.

Go back to Settings > Windows Update and select Retry once, after you have done the restart, clock and free space checks. If the same KB number fails again with 0x80070057, stop retrying it. Repeated tries will use the same damaged download.

Next, run the built-in Windows Update troubleshooter and let it finish. On Windows 11, go to Settings > System > Troubleshoot > Other troubleshooters, then select Run next to Windows Update. On Windows 10, go to Settings > Update & Security > Troubleshoot > Additional troubleshooters, then select Windows Update. Do not change anything by hand until it ends. Try the update again afterwards.

If the error returns, clear the downloaded update so Windows has to fetch a clean copy. The steps below rename the download folder instead of deleting it. Your documents and backup settings stay as they are.

  1. Open the Services app. Find Windows Update and Background Intelligent Transfer Service, select each one, and select Stop.
  2. Open File Explorer and go to C:\Windows. Rename the SoftwareDistribution folder to SoftwareDistribution.old.
  3. Return to Services and start Windows Update and Background Intelligent Transfer Service again. Then restart the PC from Start > Power > Restart.
  4. After the restart, open Settings > Windows Update and select Check for updates. Windows will create a new SoftwareDistribution folder and download a fresh copy of the update.

If one KB number now fails again and again while other updates install, treat that single update as the problem. Keep the KB number with your notes and stop forcing it. You do not need a cleaner, a driver updater, or a paid tool that promises to fix this code.

Windows Update History screen showing a failed update with its KB number and error 0x80070057, with the Retry option nearby. | PC Error Codes
Fix It When It Happens During Windows Update | PC Error Codes

Fix It When It Happens During Backup, Restore or Copying to a Drive

Fix It When It Happens During Backup, Restore or Copying to a Drive

If 0x80070057 appears only when you back up, restore, or copy files to a drive, start with that drive. Windows is usually objecting to the destination or to a backup setting, so update fixes will not help here.

  1. Reconnect the drive with a different cable and a different USB port, plugged directly into the computer, not through a hub. Watch it in File Explorer as you work. If it vanishes and reappears, the connection or the drive itself is likely the problem.
  2. Right-click the drive in File Explorer, select Properties, then Tools. Under Error checking, select Check and let it finish. Then try the backup once more.

To find out whether the drive is at fault, back up one small folder to a different location, such as another drive. Use only a few ordinary files for this test.

If the small backup works, the original drive is likely the cause, so use the new location or replace that drive. If it fails with the same code, a file or a setting on the PC is more likely.

Check a setting that often triggers this code during backup. Open Control Panel, select Region, then Additional settings, and look at Decimal symbol. It must be '.' (a period). If it is a comma, change it to a period, select OK, and retry the backup.

For a system image, open the destination drive's Properties and check its file system and free space. The drive must use NTFS and have room for the image. Do not format it to change the format, because formatting erases it. Use another NTFS drive instead.

Finally, type Services in Windows search and open the app. Find Volume Shadow Copy and read its Startup type. If it says Disabled, open it, change the Startup type to Manual, and select OK. None of these checks needs a registry edit.

An external backup drive connected directly to a laptop by USB, with the drive Properties window open to the Tools tab and Error checking | PC Error Codes
Fix It When It Happens During Backup, Restore or Copying to a Drive | PC Error Codes

Fix It When It Happens While Installing Windows or a Program

Fix it when it happens while installing Windows or a program

If a program or app fails, delete the installer you downloaded. Get a fresh copy from Microsoft or from the program maker only, and check that it matches your version of Windows. A damaged or wrong installer is a common reason setup rejects a value and stops.

If Windows setup itself fails, re-create the installation media using the tools on Microsoft's site. Remove all non-essential USB drives before you retry, leaving only the installation media connected. Do not use an old USB stick you are unsure about if a fresh copy is an option.

Do not do this

Stop before you delete or format a partition on an install screen. That is not a safe first fix for this code, and it can erase Windows and your files. Try the fresh media first.

If the failed item has a KB number, check Settings, then Windows Update, then Update History. That is an update failure, not a program install. Go back to the Windows Update fixes above and follow that path instead.

If 0x80070057 Keeps Coming Back: Safe Next Steps

If 0x80070057 keeps coming back, look at the pattern. Failure only during backup points to the destination drive. Failure only when one update installs points to that damaged update. A fault in one place does not mean the whole PC is damaged.

Before any deeper repair, copy important files to a separate safe place, such as another drive, and open a few copies to check they work. Keep any KB number, the backup drive name, and a clear photo of the error together in one record.

If the error still returns, the last resort is an in-place repair install. It is a larger repair, so follow the separate guide for it instead of starting it here. That guide sets out the preparation in full.

Do not do this

Skip registry cleaners, driver updaters, and paid 'fix this code' tools. None are needed for 0x80070057. Some charge for changes Windows can make in its own settings, so close any site that asks you to pay to remove this error.

Conclusion

Error 0x80070057 looks like one problem, but where you saw it is the clue that matters. The same code during Windows Update points one way. The same code during a backup points another way. Staying on the path that matches your case is what turns a vague code into a fix you can test.

If the task finishes now, stop there and leave the working settings alone. If the code comes back in the same place only, that narrow pattern is your next lead. Keep the notes you made at the start, and do not pay for a program that promises to fix the code for you.