How Do I Fix Windows Update Error 0x80070057?

Issue type: Windows Update error — 0x80070057 (ERROR_INVALID_PARAMETER)

SEO focus: If you are looking for windows update error 0x80070057, this guide starts with the fastest diagnosis, then moves to the exact fix that matches the symptom.

Short answer: Error 0x80070057 means Windows passed something invalid to the update system while writing files. The most common cause is a corrupted update cache or a stale WSUS registry entry. Clear the SoftwareDistribution folder, run DISM, then SFC. If the error only appears after a corporate policy removal, clean up the WindowsUpdate registry key.

Windows Update Error 0X80070057: Quick Diagnosis

Error 0x80070057 is a generic Windows error code meaning “invalid parameter” — it’s not exclusive to Windows Update, but when it appears during an update, it almost always means one of three things: the cached update files in SoftwareDistribution are corrupted, the Windows component store has damaged entries, or there’s a leftover WSUS (corporate update server) pointer in the registry pointing to a server that no longer exists. To find which update is failing, open Event Viewer (Win + S, type “Event Viewer”) > Windows Logs > Application and look for entries with the source “Microsoft-Windows-WindowsUpdateClient.” The error message there will usually show the KB number of the failing update and a more specific sub-code.

What to do first

1. Run the Windows Update Troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run. It automatically detects and resets several states that cause this error.
2. Clear the Windows Update cache. Open Command Prompt as Administrator and run:
   net stop wuauserv
net stop bits
ren C:WindowsSoftwareDistribution SoftwareDistribution.old
net start wuauserv
net start bits
   Then go back to Windows Update and try again.
3. Run DISM to repair the component store — do this before SFC:
   DISM /Online /Cleanup-Image /RestoreHealth
   Wait for it to complete fully. It downloads replacement files from Windows Update, so make sure you’re connected to the internet.
4. After DISM completes, run:
   sfc /scannow
   Restart your PC once it finishes.
5. Check for a stale WSUS registry entry. This step is only relevant if your PC was previously on a company domain or had Group Policy applied. Open Registry Editor (Win + R, type regedit). Navigate to:
   HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWindowsUpdate
   If you see values named WUServer or WUStatusServer, right-click the WindowsUpdate key > Export (save a backup), then delete both values. This forces Windows to use Microsoft’s servers instead of the old corporate one.
6. If a specific update keeps failing, note its KB number and download it directly from catalog.update.microsoft.com. Install the .msu file manually by double-clicking it.

Common mistake

Running sfc /scannow before DISM. SFC repairs individual system files, but it depends on the Windows component store being healthy. If the store is corrupted — which is what causes 0x80070057 — SFC may report that it “found corrupt files and could not fix some of them,” and nothing gets resolved. Always run DISM /RestoreHealth first to repair the store, then run SFC to clean up any remaining file issues.

Best next step

If DISM completes but 0x80070057 keeps appearing on the same update, the downloaded update package itself may be the issue. Go to Settings > Windows Update > Update history and note the KB number of the failing update. Delete the SoftwareDistribution folder entirely (using rd /s /q C:WindowsSoftwareDistribution after stopping the wuauserv service), then let Windows re-download it from scratch. If that still fails, download and install it manually from the Microsoft Update Catalog.

Official reference: For official update guidance, check Microsoft’s Windows Update FAQ before using advanced repair steps.

Quick Q&A

Can a third-party antivirus cause error 0x80070057?

Yes. Some antivirus programs intercept Windows Update file writes and block them — especially if the update is writing to a monitored system folder. Temporarily disable real-time protection, try the update again, then re-enable it. If the update succeeds, add C:WindowsSoftwareDistribution to your antivirus exclusion list to prevent it from interfering in future updates.

I see 0x80070057 only on one specific update, not all of them. Does that narrow it down?

Yes — it means the cached download for that specific update is corrupted. Rename the SoftwareDistribution folder as described, go back to Windows Update, and let it re-download that update from scratch. A fresh download almost always resolves it when the error is isolated to one KB.

Is it safe to delete the WUServer registry value?

Yes, if your PC is no longer on a corporate domain and those values are pointing to a server that no longer exists. Deleting them just tells Windows to use Microsoft’s public update servers again. Before deleting anything in the registry, always export the key first (right-click > Export) so you can restore it if needed.