Quick answer: Windows 11 error 0x80073712 means your Windows component store is corrupted. Fix it by opening an elevated Command Prompt and running DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. Once both complete successfully, retry Windows Update or manually install KB5086672 from the Microsoft Update Catalog. This sequence resolves the error in roughly 85% of cases without reinstalling Windows.
If you updated Windows 11 in March 2026 and suddenly found yourself staring at a red error code 0x80073712 every time you try to install further updates, you are not alone. The optional update KB5079391, released mid-March 2026, corrupted the Windows component store on a large number of systems — leaving Windows Update in a broken loop where new patches, including the fix itself, could not be installed. Microsoft responded on March 31, 2026 by releasing KB5086672 as a cumulative update that addresses the underlying issue — but getting it to install on an already-damaged system requires a few repair steps first.
This guide covers every fix from quickest to most thorough. Work through the steps in order. Most readers resolve Windows 11 error 0x80073712 within steps 1 through 4 and never need to go further. Steps 5 through 10 are progressively deeper repairs for persistent cases.
Table of Contents
- Run the Windows Update Troubleshooter
- Run DISM /Online /Cleanup-Image /RestoreHealth
- Run SFC /scannow
- Manually download and install KB5086672
- Reset Windows Update components with net stop commands
- Clear the SoftwareDistribution folder
- Perform a clean boot and retry the update
- Use the Media Creation Tool for an in-place repair upgrade
- Check disk health with CHKDSK
- Reset this PC (keep your files)
What Does Error 0x80073712 Actually Mean?
The hexadecimal code 0x80073712 maps to a specific internal message: "The component store has been corrupted." The Windows component store — also called CBS (Component Based Servicing) — is a repository of all the files, manifests, and metadata that Windows needs to install, update, and service system components. When a file in that store is missing, truncated, or has the wrong hash, Windows Update refuses to proceed and throws this Windows update error.
The component store corruption that causes Windows 11 error 0x80073712 can happen for several reasons:
- An interrupted update (power loss or forced shutdown mid-install)
- A defective update package — as with KB5079391 in March 2026
- Storage drive errors (bad sectors or failing NAND flash on an SSD)
- RAM errors that cause corrupted write operations during system file operations
- Third-party security software that quarantined a CBS manifest file by mistake
Before you start: note your Windows version
Press Win + R, type winver, and press Enter. Write down your build number (e.g., 22H2 Build 22621.xxxx or 24H2 Build 26100.xxxx). This matters for identifying the correct update package to download from the Microsoft Update Catalog in Step 4.
Step 1: Run the Windows Update Troubleshooter
Use the built-in update troubleshooter — it fixes common errors automatically
The Windows Update Troubleshooter can detect and repair a subset of component store issues, reset the Windows Update Agent, and clear stuck update entries. It takes about two minutes and requires no technical knowledge. Always run it first before attempting manual repairs.
Windows 11: Go to Settings → System → Troubleshoot → Other troubleshooters → Windows Update and click Run.
Follow the on-screen prompts. If the troubleshooter reports it has fixed something, restart your computer and try running Windows Update again. If it reports "no changes were made" or the Windows 11 error 0x80073712 persists, proceed to Step 2.
You can also launch the update troubleshooter directly from an elevated Command Prompt:
Step 2: Run DISM /Online /Cleanup-Image /RestoreHealth
Repair the Windows component store using DISM
DISM (Deployment Image Servicing and Management) is the primary tool for fixing a corrupted Windows component store. The /RestoreHealth flag contacts Windows Update servers, identifies corrupted or missing component store files, and replaces them with verified good copies from Microsoft. This is the single most effective fix for Windows 11 error 0x80073712.
Open Command Prompt as administrator: Press Win + S, type cmd, right-click Command Prompt, and select Run as administrator. Then run:
DISM displays a progress percentage. It can appear to freeze at 20%, 40%, or 62% — this is normal. Do not close the window. The full process takes 10–30 minutes on most systems. When it completes, you will see one of these messages:
- "The restore operation completed successfully" — proceed to Step 3
- "The component store corruption was repaired" — excellent, proceed to Step 3
- "The source files could not be found" — DISM cannot reach Windows Update servers; use the offline source method below
DISM with a local source (offline or restricted networks)
If DISM cannot download from Windows Update (error 0x800f081f or "source files could not be found"), you can point it at a local Windows 11 ISO. Mount the ISO, then run:
Replace D: with the drive letter of your mounted ISO. The ISO must match your exact Windows 11 edition and version build.
Step 3: Run SFC /scannow
Use System File Checker to replace corrupted OS files
After DISM has repaired the component store, SFC (System File Checker) can now draw on those repaired files to fix corrupted Windows system files. Always run DISM before SFC — running SFC first on a broken component store means SFC has nothing clean to restore from and will report errors it cannot fix.
In the same elevated Command Prompt, run:
SFC will scan all protected system files. This takes 5–15 minutes. Possible outcomes:
- "Windows Resource Protection did not find any integrity violations" — your system files are clean
- "Windows Resource Protection found corrupt files and successfully repaired them" — restart and retry the update
- "Windows Resource Protection found corrupt files but was unable to fix some of them" — run DISM again, then SFC again, or move to Step 4
After SFC completes, restart your computer and attempt Windows Update again. If the Windows update error 0x80073712 is gone, you are done. If it persists, continue to Step 4.
Stuck on a step? We'll fix it remotely — same day.
Our certified technicians resolve Windows 11 errors including 0x80073712 via secure remote session. No home visit required. Average fix time: under 45 minutes.
Step 4: Manually Download and Install KB5086672 from Microsoft Update Catalog
Bypass Windows Update and install the patch directly
Even after DISM and SFC, the automatic Windows Update channel may still fail with error 0x80073712 due to residual metadata issues in the update database. Installing KB5086672 manually via the Microsoft Update Catalog sidesteps the update pipeline entirely and installs the package directly from a standalone installer. This is the recommended path for systems that were hit by the March 2026 KB5079391 corruption.
How to download and install KB5086672:
- Open your browser and go to catalog.update.microsoft.com
- Search for
KB5086672 - In the results, find the row matching your Windows 11 version and architecture (x64 for most PCs, ARM64 for Surface Pro X and similar devices)
- Click Download, then click the .msu link in the pop-up window that appears
- Once the .msu file downloads, double-click it to launch Windows Update Standalone Installer
- Click Yes when prompted, then wait for installation to complete (5–15 minutes)
- Restart your computer when prompted
After rebooting, open Settings → Windows Update and confirm that KB5086672 appears in your update history as "Successfully installed." Then run Windows Update to pick up any additional patches that were previously blocked.
Was KB5079391 installed on your system?
Open Settings → Windows Update → Update history and scroll through the list. If you see KB5079391 listed as "Successfully installed" from March 2026, your component store corruption almost certainly came from that update. Follow Steps 1–4 carefully. Microsoft's documentation confirms KB5086672 supersedes and replaces KB5079391 entirely.
Step 5: Reset Windows Update Components (net stop Commands)
Stop and restart all Windows Update services to flush corrupted state
Windows Update relies on several interdependent services: wuauserv (Windows Update), bits (Background Intelligent Transfer Service), cryptsvc (Cryptographic Services), and msiserver (Windows Installer). Stopping all of them, clearing their working data, and restarting them gives the update stack a completely clean slate. This resolves a different class of Windows update error compared to component store corruption — specifically issues where the update service itself is stuck.
Open an elevated Command Prompt and run each line in sequence:
After running all commands, restart your computer and try Windows Update again. This reset is particularly effective at breaking the looping failure state that the KB5079391 incident created on affected machines.
Step 6: Clear the SoftwareDistribution Folder
Delete cached update packages to force a fresh download
The C:\Windows\SoftwareDistribution\Download folder stores update packages that Windows has downloaded but not yet installed. If any of those packages are corrupt or only partially downloaded, Windows Update will keep attempting to use them and fail with Windows 11 error 0x80073712. Clearing this folder forces a clean re-download.
If you completed Step 5, you already renamed the SoftwareDistribution folder. If you skipped Step 5 and want to target only the download cache, do the following:
Windows will automatically recreate the folder structure and re-download only the packages it needs. This operation does not remove any previously installed updates — it only clears the temporary download cache used during the installation process.
Step 7: Perform a Clean Boot and Retry the Update
Eliminate third-party software interference
Some third-party antivirus programs, VPNs, endpoint security suites, and driver utilities intercept Windows Update transactions and can corrupt component store writes. A clean boot loads Windows with only Microsoft-signed services and drivers running, removing all third-party software from the equation temporarily.
How to clean boot Windows 11:
- Press Win + R, type
msconfig, press Enter - On the Services tab, check Hide all Microsoft services, then click Disable all
- Go to the Startup tab, click Open Task Manager
- In Task Manager, right-click each startup item and select Disable
- Close Task Manager, click OK in msconfig, then restart your PC
After the clean boot restart, immediately open Settings → Windows Update and attempt to install updates. If the Windows 11 error 0x80073712 no longer appears, one of the disabled services was the culprit — re-enable them in groups to identify which one. After your updates install successfully, reopen msconfig and re-enable all services.
Step 8: Use the Media Creation Tool for an In-Place Repair Upgrade
Reinstall all Windows 11 system files over themselves — without losing data
An in-place upgrade (also called a repair upgrade) uses the Windows 11 Media Creation Tool to reinstall all Windows system files — including the entire component store — while preserving your personal files, installed applications, and settings. Think of it as a targeted rebuild of the operating system layer underneath your data. This approach resolves even the most persistent cases of Windows 11 error 0x80073712 without requiring a full factory wipe.
Steps:
- Download the Windows 11 Media Creation Tool from microsoft.com/software-download/windows11
- Run the tool and select Upgrade this PC now
- Accept the license terms when prompted
- When asked what to keep, select "Keep personal files and apps"
- Click Install and let the process run to completion (30–90 minutes depending on your hardware)
After the in-place upgrade completes and your PC restarts, Windows will be fully rebuilt from Microsoft's verified installation files. Open Windows Update — KB5086672 and all other pending updates should now install without the 0x80073712 error.
In-place upgrade success rate
A repair upgrade resolves error 0x80073712 in virtually all cases where DISM and SFC alone were not sufficient. It is not a destructive operation — your files, desktop shortcuts, and installed programs remain intact. You will need approximately 8 GB of free disk space and a stable internet connection to download the updated Windows image.
Step 9: Check Disk Health with CHKDSK
Rule out physical storage errors that keep re-corrupting the component store
If DISM repairs succeed but the Windows update error 0x80073712 returns after the next reboot, your storage drive may have bad sectors that are silently corrupting files as they are written. CHKDSK scans the drive surface and marks bad sectors so Windows avoids writing to them in the future.
In an elevated Command Prompt, run:
Because the C: drive is in use, Windows will schedule the scan for the next restart. Type Y to confirm, then restart. CHKDSK runs before Windows loads and takes 20–60 minutes on HDDs (SSDs are much faster). Once complete, Windows boots normally — then run DISM and SFC again (Steps 2 and 3) to repair any files that were corrupted by those bad sectors before they were marked.
If CHKDSK reports a large number of bad sectors on an HDD, the drive is physically failing and should be replaced before investing more time in software repairs.
Step 10: Reset This PC (Keep Your Files)
Last resort: fully reset Windows while preserving personal files
If every preceding step has failed to resolve Windows 11 error 0x80073712, a PC reset is the definitive solution. The "Keep my files" option reinstalls Windows from scratch but does not delete documents, photos, or other personal files stored in your user profile folder. It does remove installed applications and custom settings, so you will need to reinstall your software afterward.
Steps:
- Open Settings → System → Recovery
- Under Recovery options, click Reset PC
- Select Keep my files
- Choose Cloud download (recommended — downloads a fresh verified Windows image) or Local reinstall
- Follow the on-screen prompts and allow the reset to complete (45–120 minutes)
After the reset, Windows will be completely clean. Run Windows Update immediately to install all current patches including KB5086672. The Windows 11 error 0x80073712 will not return because the component store has been built from scratch using a verified Microsoft source image.
What Happened in March 2026 — The KB5079391 Story
To understand why so many Windows 11 users encountered error 0x80073712 suddenly in March 2026, it helps to know the background of what happened with KB5079391. Microsoft released this as an optional cumulative preview update in the third week of March 2026. Optional preview updates are offered to users who voluntarily seek out early access to upcoming patches — they are not mandatory and are not pushed automatically via the standard Patch Tuesday cycle.
Shortly after deployment began, Microsoft's telemetry data and community support forums started showing a spike in component store corruption reports, specifically tied to the 0x80073712 error code. The update's installer appeared to improperly modify several CBS manifest files on a subset of system configurations — particularly machines running certain third-party disk encryption tools or specific UEFI firmware versions that had a non-standard component registration layout. The corruption was not always immediately obvious: some users only noticed the error when April 2026 Patch Tuesday updates attempted to install days later and failed.
Microsoft's response was KB5086672, released March 31, 2026. This cumulative update not only included all prior patches but also contained a targeted repair routine for the specific manifest corruption introduced by KB5079391. However — and this is the critical detail — KB5086672 cannot install itself on a system whose component store is already too corrupted to accept any updates. That is precisely why the DISM repair in Step 2 is essential before attempting to install KB5086672 manually in Step 4.
Which Windows 11 versions are affected?
The issue was observed on Windows 11 22H2 (Build 22621), Windows 11 23H2 (Build 22631), and Windows 11 24H2 (Build 26100). Users who had disabled optional preview updates or who had not manually opted in to KB5079391 were generally not affected. Windows 11 Home editions with automatic updates fully enabled were the most commonly impacted group, since they were more likely to have downloaded the optional update automatically during idle periods.
How to Prevent Windows Update Errors in the Future
Once you have resolved Windows 11 error 0x80073712, a few simple habits will significantly reduce the chance of hitting update errors again:
- Pause optional updates for 7 days after release. Go to Settings → Windows Update → Advanced options and set a brief delay on optional updates. This gives the broader community time to surface problems before they reach your machine.
- Keep at least 20 GB free on your C: drive. Windows Update needs substantial working space for package downloads and temporary expansion files. A nearly full system drive is one of the most common causes of corrupted update downloads and failed installs.
- Never interrupt an active update. Never force a shutdown or hard reset while the update progress screen is visible. If you are on a laptop, plug in the power adapter before starting a major update session.
- Run a quick DISM health check monthly. The
CheckHealthflag completes in seconds and tells you immediately whether your component store has any corruption flags:DISM /Online /Cleanup-Image /CheckHealth - Maintain a system image backup. Free tools such as Macrium Reflect can create a full image backup of your Windows drive. If a future update ever catastrophically corrupts your system, restoring from a pre-update image is far faster than any repair procedure described in this guide.
How to Confirm the Fix Worked
After completing whichever steps resolved your issue, verify the fix thoroughly before considering the matter closed:
- Open Settings → Windows Update and click Check for updates. All available updates should download and install without the 0x80073712 error appearing.
- Open an elevated Command Prompt and run
DISM /Online /Cleanup-Image /CheckHealth. The result should say "No component store corruption detected." - In Settings → Windows Update → Update history, confirm that KB5086672 appears with a status of "Successfully installed."
- Run
sfc /scannowone final time. The result should confirm no integrity violations are found.
If all four checks pass cleanly, your Windows component store is fully healthy and the Windows 11 error 0x80073712 is resolved. Your system is now ready to receive ongoing updates normally through the standard update troubleshooter and automatic Windows Update channels.
Frequently Asked Questions
Error 0x80073712 means the Windows component store (CBS — Component Based Servicing) is corrupted. Update files required to install a patch are missing or damaged. The March 2026 optional update KB5079391 was a known trigger that corrupted CBS manifests on many systems. Microsoft released cumulative update KB5086672 on March 31, 2026 to address this, but systems already corrupted still need manual repair using DISM and SFC before the update can install successfully.
KB5086672 is a cumulative update for Windows 11 released by Microsoft on March 31, 2026. It was issued partly in response to problems caused by the optional March 2026 update KB5079391, which left many systems unable to install subsequent updates and triggered error 0x80073712. If you are seeing this Windows update error and had KB5079391 installed, you should install KB5086672 manually from the Microsoft Update Catalog after repairing your component store with DISM.
DISM /Online /Cleanup-Image /RestoreHealth typically takes between 10 and 30 minutes depending on your internet speed and the speed of your storage drive. On a slow HDD or a congested network connection it can take up to 45 minutes. Do not close the Command Prompt window — DISM may appear to stall at certain percentage points (especially around 20% and 62%) but will continue if you leave it running.
Yes, it is completely safe to delete or rename the SoftwareDistribution\Download folder. This folder holds update files that Windows has already downloaded but not yet fully installed. Deleting it does not remove any previously installed updates — it only forces Windows Update to re-download update packages on its next run. You must stop the Windows Update service (wuauserv) and BITS service before deleting the folder, then restart them afterward. Windows will automatically recreate the folder structure.
In the vast majority of cases, yes. Most instances of Windows 11 error 0x80073712 are resolved through the repair sequence: DISM /Online /Cleanup-Image /RestoreHealth, then SFC /scannow, followed by manually installing KB5086672 from the Microsoft Update Catalog. If those steps do not work, a Media Creation Tool in-place upgrade repairs all Windows system files while keeping your personal files, programs, and settings intact — without a full reinstall.
Still seeing error 0x80073712? Let IT Cares fix it for you.
Our technicians have resolved hundreds of Windows 11 update errors including the KB5079391 / KB5086672 issue. Remote session from anywhere in Canada — usually fixed in under an hour. No fix, no charge.