# Windows Update Error 0x800f0922, 0x80070002, 0x80073712: Fixes Source: https://srvscripts.com/guides/windows-update-error-0x800f0922/ Updated: 2026-10-06 Publisher: srvScripts (https://srvscripts.com/) Windows Update fails in three broad ways: it cannot find or download what it needs, it downloads but cannot stage the package, or it stages the package and the installation fails during the reboot. The codes 0x80070002, 0x800f0922 and 0x80073712 map neatly onto those stages, which is why they account for such a large share of update tickets. The steps below apply to Windows 10, Windows 11 (25H2 and 26H1) and Windows Server 2019/2022/2025, whether updates come from Microsoft, WSUS or Intune. In short: 0x80070002 means a file the update client expected is missing, so reset the Windows Update components and clear C:\Windows\SoftwareDistribution; 0x800f0922 means the installation could not commit, most often because the EFI system… **Short answer:** 0x80070002 means a file the update client expected is missing, so reset the Windows Update components and clear `C:\Windows\SoftwareDistribution`; 0x800f0922 means the installation could not commit, most often because the EFI system partition is full or a service such as .NET or Secure Boot servicing is blocked, so free space on the EFI partition and check the CBS log; 0x80073712 means the component store is corrupt, so run `DISM /Online /Cleanup-Image /RestoreHealth` followed by `sfc /scannow` and retry. ## Collect the evidence first Before resetting anything, capture the client’s view of the failure: ``` Get-WindowsUpdateLog Get-Content C:\Windows\Logs\CBS\CBS.log -Tail 300 | Select-String "error|failed" ``` `Get-WindowsUpdateLog` decodes the ETW traces into WindowsUpdate.log on the desktop. Search it for the KB number and the “Failed” lines around it; the download URL and the HTTP status tell you whether the source (WSUS, Microsoft Update or an Intune-delivered package) was even reachable. ## 0x80070002: file not found This is ERROR_FILE_NOT_FOUND from the download or staging step. Typical causes are a corrupted download cache, a WSUS server that has not synchronised the package content, or a broken language pack reference. Reset the update components: ``` net stop wuauserv net stop cryptSvc net stop bits net stop msiserver ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old net start msiserver net start bits net start cryptSvc net start wuauserv ``` Then check for updates again. On WSUS clients, also confirm the target group and that the update is approved and downloaded on the server. If the error names a feature update, verify `C:\$WINDOWS.~BT` is not left over from a previous attempt; remove it once services are stopped. ## 0x800f0922: installation could not commit CBS_E_INSTALLERS_FAILED. The two dominant causes: - The EFI system partition (typically 100 MB) has no free space for the new boot files. Check it: ``` mountvol S: /S dir S:\EFI\Microsoft\Boot ``` Delete stale font files or old language folders under S:\EFI\Microsoft\Boot only if you are certain, then `mountvol S: /D`. On machines with a chronically small partition, the durable fix is to extend it during a maintenance window or rebuild with a larger partition. - A servicing step the package depends on is blocked: .NET Framework updates failing behind a proxy that blocks the download, or Secure Boot certificate servicing failing on old firmware. The CBS log names the failing installer; search for “Failed to execute” near the end. If neither applies, disable third-party antivirus temporarily, because filter drivers that block writes to WinSxS cause the same code. ## 0x80073712: component store corrupt ERROR_SXS_COMPONENT_STORE_CORRUPT. The fix is the standard repair sequence, documented in more depth in [Repair Windows 11 with DISM and SFC](/guides/dism-restorehealth-offline-source/): ``` DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow DISM /Online /Cleanup-Image /StartComponentCleanup ``` Reboot, then retry the update. If DISM itself fails with 0x800f081f, supply an offline source from an ISO of the same build. Where the client keeps failing but the store is healthy, download the .msu from the Microsoft Update Catalog and install it directly, which bypasses the scan and download stages: ``` wusa.exe C:\Updates\windows11.0-kb5129195-x64.msu /quiet /norestart DISM /Online /Add-Package /PackagePath:C:\Updates\windows11.0-kb5129195-x64.msu ``` The DISM route gives a more detailed error in dism.log if it also fails. ## Verify After a successful retry, confirm the package is present and the machine is on the expected build: ``` Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5 winver ``` Also check Settings » Windows Update » Update history shows the KB as “Successfully installed” and that no further reboot is pending. ## Common pitfall Running the SoftwareDistribution reset while the Windows Update service restarts itself is the usual reason the rename fails with “access denied”; the services must be stopped in the order shown and the rename issued immediately. On servers managed by Intune or SCCM, the client-side reset is harmless, but do not delete the WSUS server-side content in response to a client error; one misbehaving client is not evidence of a server problem. ## Windows Update error 0x800f0922 at a glance **Official documentation:** [Windows client documentation](https://learn.microsoft.com/en-us/windows/), [Windows Server documentation](https://learn.microsoft.com/en-us/windows-server/). **Related guides:** [Transfer and seize FSMO roles with PowerShell and ntdsutil](https://srvscripts.com/guides/transfer-fsmo-roles-powershell/) · [Fix AD replication errors 8453 and 1722 “The RPC server is unavailable”](https://srvscripts.com/guides/ad-replication-error-1722-8453/) · [A basic RMM monitoring policy for small-business endpoints: disk, patching and antivirus](https://srvscripts.com/guides/rmm-monitoring-policy-endpoints/). ## Frequently asked questions ### Does 0x800f0922 also apply to Windows Server 2022 and 2025? Yes. Servers hit it for the same two reasons, and full EFI partitions are common on servers that were upgraded in place through several versions. The mountvol check and CBS log analysis are identical. ### How long does the Windows Update component reset take? The reset itself completes in under a minute. The first scan afterwards rebuilds the update catalogue and can take 10–20 minutes, and the download of a cumulative update restarts from scratch. ### Can I undo the reset of SoftwareDistribution? Yes, stop the services again and rename SoftwareDistribution.old back, but there is rarely a reason to. The folder is only a cache; the renamed copy can be deleted once updates are working.