Home › Windows Update › 0x80070057

Windows Update · 0x80070057 · Windows 11 23H2

Windows Update Error 0x80070057 in Windows 11 23H2

Root cause: malformed GUIDs or registry keys; Fix: repair CBS store, remove invalid entries.

Error Details

FactValueSourceNote
Exact error stringFailed to pin deployment [DeploymentInvalid] 0x80070057CBS.log-> CBS operation
Affected build rangeWindows 11 23H2
Registry key involvedHKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\ClientsRegistry Editor-> Malformed GUIDs
Relevant service/endpoint URL
Log line signatureERROR_INVALID_PARAMETER or DeploymentInvalid near 0x80070057CBS.log, WindowsUpdate.log

Log Files to Check

What This Error Actually Means

The error code 0x80070057, also known as ERROR_INVALID_PARAMETER, is raised when the Windows Update Agent passes an invalid or malformed parameter to the Component-Based Servicing (CBS) transaction engine or the Standalone Update Installer (wusa.exe). This specific error occurs in scenarios where a GUID or registry key reference is incorrectly formatted. The CBS.log file will contain entries like "Failed to pin deployment [DeploymentInvalid] 0x80070057," indicating that an internal call from Windows Update Agent to the CBS engine failed due to malformed input data.

Affected Versions and Scope

This error is particularly prevalent in Windows 11, build 23H2. It does not affect earlier versions of Windows 11 or other operating systems such as Windows 10. The issue arises from the interaction between the Windows Update Agent and CBS, which are tightly integrated components in Windows 11.

Where To Look First: Logs and Event IDs

To diagnose this error, start by examining the following logs:

Root Causes

There are several distinct causes that can lead to this error:

Malformed GUIDs in Registry Keys

The registry key HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Clients contains subkeys that should be properly formatted GUIDs. If any of these keys are malformed (e.g., missing braces or wrong byte order), the CBS transaction engine will reject the update installation request, resulting in error 0x80070057.

Incorrect Version String in .msu Metadata

When using wusa.exe to apply a .msu patch and the update package metadata specifies a version string that does not match the CBS transaction format, this can also trigger the error. The mismatch occurs when the metadata is incorrectly formatted or references an invalid component.

Fix Procedure

To resolve the 0x80070057 error, follow these steps:
  1. Generate the CBS-specific update log: Run Get-WindowsUpdateLog in elevated PowerShell to produce a detailed log at C:\Users\\Desktop\WindowsUpdate.log. Open this file and search for '0x80070057', then look 20 lines above for the CBS operation that preceded the error.

  2. Inspect the Clients registry hive: Use Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Clients' to list all subkeys. Look for any subkeys with malformed or non-GUID names, and backup these entries before removing them using reg export.

  3. Repair the CBS component store: Run DISM /Online /Cleanup-Image /CheckHealth to check the health of the component store. If it reports 'repairable', proceed with DISM /Online /Cleanup-Image /RestoreHealth. This command repairs the component store database and clears malformed deployment entries.

  4. Verify Windows Update service dependencies: Use Get-Service wuauserv,bits,cryptsvc | Select-Object Name,Status,StartType to ensure all services are running (or set to Manual/Automatic).

  5. Reset Windows Update components: Stop the necessary services with Stop-Service wuauserv,bits,cryptsvc,msiserver. Rename the SoftwareDistribution and catroot2 folders to their backup versions using Rename-Item C:\Windows\SoftwareDistribution C:\Windows\SoftwareDistribution.old and Rename-Item C:\Windows\System32\catroot2 C:\Windows\System32\catroot2.old. Restart the services with Start-Service wuauserv,bits,cryptsvc,msiserver.
  6. If using wusa.exe to install a specific .msu: Verify that the update is for the correct Windows version. Try installing via PowerShell instead by running Add-WindowsPackage -Online -PackagePath C:\temp\update.msu.

Error Code Variants

CodeDescriptionDistinguishing Feature
0x80070057ERROR_INVALID_PARAMETERMalformed GUID or version string in CBS transaction.
0x80070102ERROR_PATH_NOT_FOUNDFile path does not exist, often due to incorrect paths in update metadata.
0x80070002ERROR_FILE_NOT_FOUNDMissing file required for the update process.

Verification

To verify that the fix has been successful, retry Windows Update and confirm no 0x80070057 errors appear in C:\Windows\Logs\CBS\CBS.log. Use Select-String -Path C:\Windows\Logs\CBS\CBS.log -Pattern '80070057' to check for any remaining occurrences of the error code. If no results are found, the issue has been resolved.

Prevention

To prevent recurrence of this error, ensure that all registry keys under HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Clients are properly formatted as GUIDs. Additionally, regularly audit update metadata and paths to avoid mismatches with the CBS transaction format.
A non-obvious diagnostic shortcut is to use Select-String -Path C:\Windows\Logs\CBS\CBS.log -Pattern 'DeploymentInvalid' to quickly locate instances of this error in the log file.
By following these detailed steps, you can effectively diagnose and resolve the 0x80070057 error on Windows 11 build 23H2.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.