By john Error 0x80073712 indicates that a file needed by Windows Update is either missing or damaged. Windows 11 relies on a component store to assemble updates, and when files in that store become corrupted, the update cannot complete and returns this code.
A blue screen can be alarming, but it is Windows protecting itself by stopping before any deeper damage occurs. The specific stop code is a valuable clue: it narrows down whether the problem lies with a driver, system files, memory, or another component. Noting the exact code, and any file name shown on the Rajatoto88 screen, makes the troubleshooting below far more targeted and effective.
Common Causes
Before applying a fix, it helps to understand why this happens. Identifying the likely cause lets you go straight to the most relevant solution instead of trying everything at random. The most frequent causes are:
- Corrupted files in the Windows component store (WinSxS)
- An interrupted previous update leaving partial files
- Disk errors affecting system files
- Damaged update cache
How to Fix It: Step by Step
Work through these steps in order, starting with the simplest. In most cases one of the earlier steps resolves the problem, so there is no need to continue once it is fixed:
- Open an elevated Command Prompt and run DISM /Online /Cleanup-Image /RestoreHealth to repair the component store.
- Follow with sfc /scannow to verify and restore protected system files.
- Run the Windows Update troubleshooter from Settings > System > Troubleshoot > Other troubleshooters.
- Reset Windows Update components by stopping the BITS, wuauserv, and cryptsvc services, renaming SoftwareDistribution and catroot2, then restarting the services.
- Restart your PC and check for updates again.
If the Problem Persists
Because this error is tied to the component store, the DISM repair is usually the decisive step. If DISM cannot fix the store using Windows Update as a source, you can point it to a mounted Windows 11 ISO with the /Source parameter.
How to Prevent It in the Future
To reduce the chance of this stop error returning, keep your drivers current by checking the websites of your GPU, motherboard, and storage manufacturers periodically rather than relying on Windows Update alone. Avoid running unstable overclocks for everyday use, and monitor component temperatures so heat is never the underlying trigger. Maintaining a recent System Restore point and a separate file backup means that even a sudden blue screen never costs you data, since you can roll the system back to a known-good state and continue working with minimal disruption.
Final Thoughts
Issues like this are common in Windows 11 and rarely mean your PC is failing. Working methodically from the simplest fix to the more involved ones is the fastest way to resolve them while avoiding unnecessary changes to your system. If none of the steps above resolve the issue, it is worth checking Microsoft’s official support pages or community forums, since a recent update may have introduced a known problem that Microsoft is actively working to fix. In that case, waiting for the next patch, or temporarily rolling back the change that caused it, is often the most sensible course of action.