Microsoft has released an out-of-band update, KB5086672, to address a critical installation failure that prevented many Windows 11 users from installing the March 2026 non-security preview update. The fix, which landed on March 31, 2026, pushes Windows 11 versions 24H2 and 25H2 to OS builds 26100.8117 and 26200.8117, respectively, and resolves error 0x80073712—a showstopper that left devices stuck on earlier builds.

The March 2026 preview update (the optional “C” or “D” week release) was meant to deliver non-security fixes and improvements ahead of the April Patch Tuesday. But for a subset of users, the installation process ground to a halt with the dreaded 0x80073712 error. That hexadecimal code points to a corruption in the component store—the servicing stack’s database of every system file and component. When this store becomes inconsistent, the update installer cannot validate or apply changes, leading to a rollback and a failed update.

KB5086672 is an out-of-band (OOB) release, meaning it arrived outside the normally scheduled update rhythm. Microsoft typically reserves OOB updates for urgent issues—security flaws with active exploits, or widespread bugs that break core functionality. The rapid release of KB5086672 underscores the severity of the problem: without it, affected PCs could not receive the preview update at all, leaving users without its fixes and tests until the next month’s cumulative update.

The error at a glance

Error 0x80073712 is shorthand for ERROR_SXS_COMPONENT_STORE_CORRUPT. It occurs when the Windows Update service, or the underlying Component-Based Servicing (CBS) engine, finds that the component store—a collection of manifests, catalogs, and replacement files stored in C:\\Windows\\WinSxS—is missing entries, contains invalid data, or has mismatched checksums. In the context of the March 2026 preview, the corruption was triggered by the preview update’s own payload. Early reports suggest the preview’s installer made erroneous updates to the store, creating a paradox that later install attempts could not reconcile.

Before KB5086672, the standard remediation was to run the Deployment Image Servicing and Management (DISM) tool with the /RestoreHealth switch, or to manually reset the Windows Update components. However, those methods are time-consuming and often fail if the corruption is deep-seated. KB5086672 sidesteps those manual steps by delivering a targeted repair package that overwrites the corrupted metadata and brings the component store back to a consistent state.

Build numbers and versioning

The out-of-band update carries the KB number 5086672. After applying it, devices on Windows 11 version 24H2 will show OS build 26100.8117, while version 25H2 systems will advance to 26200.8117. These builds are higher than the problematic preview’s build numbers, ensuring that the fix supersedes the flawed installer logic and can be applied directly to the affected installation media.

Because the preview update was optional and only delivered to systems that “opted in” by manually checking for updates, the error hit a relatively narrow audience: mostly IT pros, enthusiasts, and early adopters who choose to run preview patches. Enterprise customers using Windows Update for Business with deferral policies likely avoided the issue, as the preview was not offered to those devices.

How to obtain KB5086672

KB5086672 is available through all standard Windows Update channels. Most affected users will see it appear automatically if their PC is configured to receive updates for other Microsoft products, or if they manually trigger a check for updates. For systems that cannot connect to Windows Update—perhaps because the failed preview left the update client in a broken state—the update can be downloaded from the Microsoft Update Catalog as a standalone .msu file. Installation via DISM or the wusa.exe command line is also supported for advanced deployment scenarios.

IT administrators can import KB5086672 into Windows Server Update Services (WSUS) or deploy it via Microsoft Intune, although the OOB status means it is classified as a “Critical Update” rather than a standard “Security Update.” Group Policy and mobile device management (MDM) settings that auto-approve critical updates will pull it in immediately.

What was in the March 2026 preview?

The preview update that triggered the error was a typical end-of-month quality release, delivering a handful of non-security improvements. While Microsoft’s official changelog for that release was never fully published—the rollout was halted before all users received it—leaked patch notes suggest it contained fixes for Task Manager freezes on multi‑monitor setups, a handful of Bluetooth audio enhancements, and updated Daylight Saving Time rules for several regions. The preview was not, by any stretch, a feature update; its ephemeral nature makes the resulting OOB fix all the more noteworthy.

Because the preview never reached broad distribution, the exact list of fixes remains somewhat speculative. Microsoft has said it will fold the preview’s contents into the April 2026 “Patch Tuesday” cumulative update—this time with the component store corruption fix baked in. For those who successfully installed the faulty preview, Microsoft has confirmed that no additional action is required; the component store error only manifested during installation, not after.

Preventing future component store corruption

Corruption of the Winsxs store is an old foe for Windows administrators. Since the days of Windows Vista, the servicing stack has relied on a meticulously indexed database of files. Any interruption during an update—a power loss, a sudden reboot, or a software conflict—can leave that database in an inconsistent state. The March 2026 episode highlights how even a pristine system can fall victim when the update’s own logic is flawed.

Microsoft has not detailed the root cause in its KB article, but notes that the problem was limited to “a known issue in the March 2026 non‑security update that leads to component store corruption during installation.” The OOB fix includes an integrity checker that reconciles the store before proceeding with the installation—a belt‑and‑suspenders approach that may benefit future previews.

User impact and reactions

On community forums and social media, affected users initially reported long installation times followed by a rollback and the error code. Many turned to manual DISM repairs, some successfully, others not. The rapid OOB response—five days after the preview first went live—drew a mix of relief and frustration. “I wasted three hours on DISM and SFC only to have the fix drop a day later,” wrote one user on Reddit’s r/Windows11. Others praised Microsoft for the swift turnaround, calling KB5086672 “the fastest OOB I’ve seen for a non‑security issue.”

The episode also reignited debate over the wisdom of offering optional preview updates to consumers. While Microsoft positions them as a convenience for “seekers” who want early access, the inherent risk of untested patches has led some to urge a return to the model of keeping previews for Insider channels only. Microsoft has shown no inclination to change course; the company still publishes preview updates each month for all supported Windows versions.

What to do now

If you attempted to install the March 2026 preview and encountered error 0x80073712, KB5086672 should get you back on track. First, make sure your system clock and regional settings are correct—component store repairs are sensitive to certificates and timestamps. Then, check for updates in Windows Update; the OOB should appear as “KB5086672 (Out‑of‑band).” Install it and reboot. No further action is needed. The April cumulative update will include all the fixes originally planned for the March preview, so there is no need to hunt for that now‑dead revision.

For admins managing multiple devices, consider pushing KB5086672 to any pilot group that may have manually installed the preview. Even if the error didn’t show up immediately, a latent store inconsistency could cause problems with future cumulative updates. Running dism /online /cleanup-image /scanhealth after deployment is a good sanity check.

Looking ahead

The March 2026 preview debacle and subsequent OOB fix mirror similar incidents from Windows 10’s past, such as the KB4524244 debacle of 2020. In each case, Microsoft eventually tightened its internal testing procedures, only for a new edge case to surface later. For Windows 11, the company now relies heavily on automated validation pipelines and the Windows Insider fleet, but the sheer diversity of hardware configurations means some bugs slip through.

KB5086672 is a symptom of a broader challenge: as Windows becomes more modular and update packages more interdependent, the servicing stack itself grows more complex. Error 0x80073712 is likely to appear again—perhaps in a different guise. Microsoft’s ability to ship a targeted OOB in under a week demonstrates a mature incident‑response muscle. But the episode also serves as a reminder: even optional updates, applied with the best intentions, can upend a system. Backup regularly, and if you seek out previews, do so knowing that an OOB savior might be just around the corner.