I've been facing a persistent problem on multiple Windows 11 PCs where I encounter Error 80073712, indicating that the component store is corrupted. This has been happening for a few months across various versions: 23H2, 24H2, and 25H2. Currently, at least 20 PCs are affected by this issue.
Interestingly, other Windows updates install without any issues, but the Cumulative Update doesn't work at all. We've been trying to update via SCCM, and even attempted direct installations from Microsoft's site, but nothing seems to resolve the error.
Here's what we've tried so far:
- Running the built-in Windows Update Troubleshooter often reports it has fixed something, but it never resolves this particular issue.
- Deleting the update cache located in SoftwareDistribution\Download and clearing the CCM Cache.
- Flushing BITS and branchcache with commands like bitsadmin.exe /reset /allusers and netsh branchcache flush.
- Running "SFC /scannow" which sometimes detects errors and claims to fix them, but often finds nothing at all.
However, when I try to run "Dism.exe /Online /Cleanup-Image /RestoreHealth", I consistently receive the error: 0x800f0915, which indicates that the repair content cannot be found and suggests checking internet connectivity or specifying a source for the required files. Setting the source to the original WIM file used for imaging doesn't help either.
At this point, I'm considering reimaging the affected PCs, but I would love to hear if anyone has other ideas for resolving this issue.
3 Answers
This might be a bit dated, but here's what I remember: First, you need to remove the pending.xml file, and you should look for corrupt manifest files in the CBS log. Also, grabbing the .cab files of the failing updates and attempting a manual install with DISM offline might help. If you're pressed for time, though, just go for a complete rebuild; it could save you a hassle later on.
Another method that may help: Run a scanhealth followed by a repair using a mapped drive that has the required source files. This usually works if you can access a working server with the proper files on it.
Have you checked the CBS log? It can give you some insight into what might be going wrong if you're able to decipher it. Sometimes those logs point out exactly what's broken.
One option you can try is running an in-place upgrade to a newer version of Windows. This has worked for quite a few folks to solve update issues like yours. Just installing a fresh build may fix the corrupted component store problem without the need for a full reimage.
Just a heads up, some systems may already be on version 25 H2, so this method might not work for everyone.
I totally agree! I had to do this as well when some systems were stuck on updates. It can really do the trick for getting everything back on track.