Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | hr=0x80073712 | C:\Windows\Logs\WindowsUpdate.log | -> Event ID 20 |
| Error description | SXS_COMPONENT_STORE_CORRUPT | Event Viewer > Windows Logs > System | |
| Affected build range | Windows 11 23H2 | -> Specific to this OS version | |
| Registry key | HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update | Registry Editor | -> SuspendedSessionId value |
| Log line signature | SXS_COMPONENT_STORE_CORRUPT | C:\Windows\Logs\CBS\CBS.log |
Log Files to Check
C:\Windows\Logs\WindowsUpdate.logC:\Windows\Logs\CBS\CBS.log
What This Error Actually Means
The error code0x80073712, also known as SXS_COMPONENT_STORE_CORRUPT, is raised by the Windows Side-by-Side (WinSxS) component store during a Windows Update operation. This error indicates that the WinSxS folder, which contains critical system files and components necessary for the proper functioning of various applications and services on your Windows 11 system, has been corrupted or compromised in some way. The corruption can be due to missing or tampered manifest files, orphaned update files from a previous failed installation attempt, or even hardware issues such as disk write errors.
Affected Versions and Scope
This error is specific to Windows 11 build23H2. It does not affect earlier builds of Windows 11 or other versions like Windows 10. The issue primarily impacts systems that are actively attempting to install updates through the built-in Windows Update service, although it can also occur during installation of certain applications or services if they rely on components stored in the WinSxS folder.
Where To Look First: Logs and Event IDs
To diagnose this error, you need to inspect several log files and event logs. The primary locations are: -C:\Windows\Logs\CBS\CBS.log: Search for lines containing 'SXS_COMPONENT_STORE_CORRUPT'.
- C:\Windows\Logs\WindowsUpdate.log: Use PowerShell cmdlet Get-WindowsUpdateLog to generate this log, then search for the exact string 'hr=0x80073712'.
- Event Viewer > Windows Logs > System: Look for Event ID 7023 (Service Control Manager) or Event ID 20 (Windows Update Agent), which will contain the error code 0x80073712.
Root Causes
Disk Write Errors During Previous Updates
Disk write errors can corrupt component manifests in the WinSxS folder, leading to this error. To identify if disk errors are the cause, runGet-PhysicalDisk | Get-StorageReliabilityCounter | Select-Object DeviceId,ReadErrorsTotal,WriteErrorsTotal,Temperature. High read/write error counts indicate potential hardware issues.
Orphaned Files from Failed Updates
A previous failed update attempt might leave behind orphaned files in the WinSxS folder. This can be identified by runningDISM /Online /Cleanup-Image /CheckHealth, which will report if there are any corrupted components.
Third-party Security Tools or Backup Agents Interfering with Updates
Security tools and backup agents that lock files in the WinSxS folder during updates can cause this error. Check your security software's logs for activity around update times to identify potential conflicts.Fix Procedure
- Generate Windows Update Log: Run
Get-WindowsUpdateLogin an elevated PowerShell session to generate the log file atC:\Users\. Search for '\Desktop\WindowsUpdate.log hr=0x80073712'. - Run DISM CheckHealth: Execute
DISM /Online /Cleanup-Image /CheckHealth, then proceed to repair if corruption is detected:DISM /Online /Cleanup-Image /ScanHealthfollowed by/RestoreHealth. If the source files are not available, use an ISO mounted on D:\ and run:DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\Sources\install.wim:1 /LimitAccess. - Run SFC: Use Command Prompt with elevated privileges to execute
sfc /scannow. Review the CBS log for specific file repair attempts. - Check Storage Health: Run
Get-PhysicalDisk | Get-StorageReliabilityCounter | Select-Object DeviceId,ReadErrorsTotal,WriteErrorsTotal,Temperatureto check disk health. If errors are present, runchkdsk C: /f /r /x. - Clean Windows Update Cache: Stop the Windows Update service with
Stop-Service wuauserv, remove the download cache folder withRemove-Item -Recurse -Force C:\Windows\SoftwareDistribution\Download\, and restart the service withStart-Service wuauserv. - Repair Windows Image: If severe corruption is detected, mount a Windows 11 ISO on D: and run
Repair-WindowsImage -Online -RestoreHealth -Source 'D:\Sources\SxS'. This step can be risky; proceed with caution.
Running the Repair-WindowsImage command may overwrite important system files, potentially breaking enrolled devices. Ensure backups are in place before proceeding.
Error Code Variants
| Code | Description | Distinguishing Factors |
|---|---|---|
0x800736F1 |
SERVICE_NOT_AVAILABLE | This error occurs when the Windows Update service is not available, often due to network issues or service state. |
0x8024A105 |
NO_SUITABLE_WINDOWS_IMAGE_FOUND | This error occurs when the system cannot find a suitable Windows image to install updates from. |
Verification
After applying the fixes, verify that the issue is resolved by checking for successful update installation in the Windows Update log. Look for entries indicating that the problematic KB article has been installed successfully without any error codes.A quick way to check if the WinSxS folder is healthy after repairs is to run
DISM /Online /Cleanup-Image /ScanHealth and ensure it reports no issues.Prevention
To prevent recurrence of this issue, implement a baseline policy that ensures regular disk health checks using PowerShell cmdlets such asGet-Disk | Get-StorageReliabilityCounter. Additionally, configure third-party security tools to avoid locking WinSxS files during update operations. Use OMA-URI settings like ./Device/Vendor/MSFT/WindowsUpdate/DisableWindowsUpdateAccessControl in Intune to manage access control around updates.
Ensure that all systems are regularly updated with the latest Windows 11 build, and monitor for any signs of disk or storage reliability issues using PowerShell cmdlets. Regularly reviewing Event Viewer logs for Event ID 7023 and 20 can also help catch potential issues early before they escalate into critical errors like SXS_COMPONENT_STORE_CORRUPT.
By following these guidelines, you can maintain a healthy Windows Update environment that minimizes the risk of encountering this specific error code.