How to Fix Error 0x80070057 When Updating Windows
A frequent failure during Windows updates and the fixes that work best, step by step.
The code 0x80070057 literally means "the parameter is incorrect" — a generic message that Windows uses in several different situations, not only when updating. That is why the fixes vary depending on where it appears.
If it appears in Windows Update
First follow the general steps in our guide on Windows update errors (disk space, automatic troubleshooter, resetting components) — they fix this code in most cases.
If it appears while making a backup
The most common cause specific to this context: the destination drive is formatted in FAT32 instead of NTFS. Windows backup tools require NTFS. Right-click the drive → Format → choose NTFS (this erases the drive's content, so back up whatever was on it first).
If it appears while copying or moving files
It usually points to insufficient space at the destination, or incorrect permissions on the destination folder. Check both before investigating further.
Lesser-known note: if you have a network drive mapped to a specific letter (for example, "B:"), Windows Update sometimes "gets stuck" checking that drive when looking for where to download updates. If you have mapped network drives and nothing else works, try temporarily disconnecting them before checking for updates.
Checking system files
If the error persists after the previous steps, our guide on SFC and DISM covers the next level — damaged system files are a common cause of this specific code.
Frequently asked questions
Does error 0x80070057 always mean the same thing?
Not exactly — it is a generic code ('the parameter is incorrect') that appears in different contexts: Windows Update, backups, or when copying files. The cause and the fix vary depending on where it shows up.
Why does it appear when making a backup but not when updating?
The most common cause in that specific context is that the destination drive is formatted in FAT32 instead of NTFS, which is what Windows backup tools require.
Do I have to reinstall Windows if none of this works?
That is a last resort, not the first. Before reaching that point, exhausting SFC, DISM and resetting the Windows Update components fixes the vast majority of reported cases.