Windows Update error 0x80070057, explained and fixed

0x80070057 is ERROR_INVALID_PARAMETER: something handed the update process a value it cannot accept, which in update practice usually means corrupt data in the update cache or its supporting registry values. It most often appears when the update check or download begins, and it is also seen in related tools (backup and restore share the code’s heritage).

The fix, in order

  1. Check the date, time, and region. Wrong system time invalidates certificates and makes update parameters unacceptable in ways that surface as this code. Settings → Time and language: set time and time zone automatically, then Sync now.
  2. Run the Windows Update troubleshooter. Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run. It catches stopped services, cache problems, and registration faults automatically.
  3. Reset the Windows Update components. In an admin Command Prompt, stop the services: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver. Rename C:\Windows\SoftwareDistribution to SoftwareDistribution.old and C:\Windows\System32\catroot2 to catroot2.old, then restart the four services with net start. This rebuilds the download cache and the update database from scratch.
  4. Repair the component store and system files. From an admin Command Prompt: DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. Restart afterwards; a repaired store often lets the same update sail through on the next attempt.
  5. Install the failing update manually. Note its KB number from Settings → Windows Update → Update history, find it in the Microsoft Update Catalog, download the package matching your Windows version and architecture, and run it. This bypasses the download machinery and reports clearer errors if it still fails.

If it still happens

If the code appears in a feature update driven by an ISO or the Installation Assistant, re-download the media; a corrupt image is itself an invalid parameter source. If it appears everywhere (updates, backup, app installs), the repair install becomes the efficient answer, since it replaces the servicing configuration as a whole.

Common questions

Why is the advice for such a vague code mostly ‘reset things’? Because the code reports bad input, not where the bad input lives. The update cache and the servicing registry are the two places bad values hide, and the reset rebuilds both. The fixes look generic because the diagnosis honestly is elimination.

Can a nearly full drive cause 0x80070057? Indirectly, yes: failed writes leave truncated cache data, and truncated data is invalid data. Keeping comfortable free space on the system drive prevents a family of these servicing errors, this one included.

Related errors

Windows Update error 0x8007000d · Windows Update error 0x80004005 · Windows Update error 0x80070002