KB5079473: 6 Proven Fixes for Install Failures and Issues

Written by: Kymakers Support Team · Reviewed by: Kymakers Technical Team Last updated: July 2026 · Applies to: Windows 11 versions 24H2 and 25H2 (OS Builds 26100.8037 / 26200.8037) Difficulty: Intermediate · Estimated time: 30–90 minutes

KB5079473 is the March 10, 2026 cumulative security update for Windows 11 versions 24H2 and 25H2, taking the OS to build 26100.8037 (24H2) or 26200.8037 (25H2). It’s a mandatory Patch Tuesday release, so skipping it isn’t a real option — the update carries the month’s security fixes.

For most people it installs cleanly. But a significant number of users have reported KB5079473 failing to install with error 0x80073712, and some have reported freezes, crashes, or BSODs after installing it. This guide covers what the update actually changes, six proven fixes for the install failures, and what to do if it destabilizes your PC.

⚠️ Before you start

KB5079473 is a security update — don’t respond to a problem by permanently blocking it and moving on, as that leaves your PC unpatched. Note also that as of the last update to this article, Microsoft’s official page still listed no known issues, while community reports described freezes and failed installs. If your system is stable after installing, leave it alone. Only apply the fixes below if you’re actually experiencing a failure.

Table of Contents

1. What KB5079473 actually changes
2. Fix 1: Run SFC and DISM
3. Fix 2: Install manually from the Update Catalog
4. Fix 3: Reset Windows Update components
5. Fix 4: Free up disk space and retry
6. Fix 5: In-place repair (when 0x80073712 persists)
7. Fix 6: If it causes freezes or BSODs
8. Should you install it?
9. FAQ

What KB5079473 Actually Changes

The update is a combined package — it bundles the latest servicing stack update (SSU) with the cumulative update (LCU), and carries forward the non-security improvements from the previous month’s preview. The main changes:

• Secure Boot — expands the set of devices eligible to automatically receive the new Secure Boot certificates, in a phased rollout. This matters because Secure Boot certificates on most Windows devices begin expiring in June 2026.
• File Explorer — improves search reliability when searching across multiple drives or “This PC.”
• Windows Defender Application Control (WDAC) — fixes COM objects being blocked when the endpoint policy was set higher than the allowlisting policy.
• Windows System Image Manager — adds a warning dialog to confirm catalog files come from a trusted source.
• Performance — faster sign-in, smoother Settings and Taskbar navigation, and more reliable wake-from-sleep.

You can confirm it installed by running winver — build 26100.8037 (24H2) or 26200.8037 (25H2) means it’s applied.

Fix 1: Run SFC and DISM

The most common failure is error 0x80073712, which means the component store is corrupted or missing files. SFC and DISM are built to repair that. From an admin Command Prompt, in order:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Run SFC first, then DISM, rebooting between them, then retry the update through Windows Update.

Worth knowing: several users reported KB5079473 still failing with 0x80073712 even after SFC and DISM came back clean. If that’s you, the store damage is beyond what these tools fix online — move to Fix 2 and, if needed, Fix 5.

Fix 2: Install Manually From the Update Catalog

If Windows Update itself is the broken link, bypass it. The update already includes the required servicing stack update, so you don’t need to hunt down prerequisites.

1. Go to the Microsoft Update Catalog and download the correct package for your version (24H2 or 25H2) and architecture (x64).
2. Install the .msu directly, or use DISM: place the file in a folder like C:\Packages and run:

DISM /Online /Add-Package /PackagePath:C:\Packages\Windows11.0-KB5079473-x64.msu

This installs it offline, outside the Windows Update pipeline, and often works when the automated path fails.

Fix 3: Reset Windows Update Components

A corrupted update cache causes repeated failures until it’s cleared. Resetting the Windows Update components forces Windows to rebuild its update state.

Stop the Windows Update and BITS services, clear the SoftwareDistribution folder, restart the services, and check for updates again. This is safe and reversible, and it resolves a whole category of KB5079473 failures caused by stale cache rather than genuine corruption.

Fix 4: Free Up Disk Space and Retry

A combined SSU + LCU package like this one needs meaningful free space on the system drive to stage and install. Low disk space is a common, overlooked cause of failures — especially the “installs then reverts on reboot” pattern.

Run Disk Cleanup, remove temporary files, and clear any old Windows.old folder. Aim for at least several gigabytes free, then retry the update. On a drive that’s been near-full for months, this alone can fix it.

Fix 5: In-Place Repair (When 0x80073712 Persists)

When SFC and DISM come back clean but the update still fails — a pattern multiple users reported — the reliable fix is an in-place repair, also called “reinstall the current version of Windows.”

Mount an ISO of your exact Windows 11 version, run setup, and choose to keep your files and apps. This replaces system components wholesale while preserving your data, which resolves the deep component-store and metadata issues that block KB5079473 when normal repairs don’t. Back up first as a precaution, then let Windows Update install the patch normally afterward.

Fix 6: If It Causes Freezes or BSODs

Some users reported crashes, hard freezes, repeated restarts, or corrupted apps (including Outlook) after installing it — even while Microsoft’s page listed no known issues.

If your PC became unstable right after this update:

• Roll it back. Settings → Windows Update → Update history → Uninstall updates, and remove KB5079473. This is a temporary measure on a security update — plan to reinstall once stable.
• Update your drivers, especially display and storage drivers, since driver conflicts are a common cause of post-update BSODs.
• If the crashes corrupted system files, an in-place repair (Fix 5) restores stability while keeping the update.

Because Microsoft may not have formally acknowledged the issue, check the Windows release health dashboard for the current status before assuming it’s your hardware.

Should You Install It?

Yes — it’s a mandatory security update, and skipping security patches isn’t a safe long-term choice. But approach it sensibly.

If you have a test machine or a non-critical PC, install it there first and watch for stability over a few days before rolling it out more widely. If a PC is already stable after installing, leave it. If you hit the install failure, work through the fixes above rather than blocking the update permanently.

And keep the June 2026 Secure Boot certificate expiry on your radar — it’s a deadline that affects most Windows devices, and updates like this one are part of how the new certificates roll out.

FAQ About KB5079473

What build does KB5079473 install? OS Build 26100.8037 on Windows 11 24H2, or 26200.8037 on 25H2. Run winver to confirm.

Why does KB5079473 fail with error 0x80073712? That error means the component store is corrupted or missing files. Run SFC and DISM first; if it still fails, install manually from the Update Catalog or do an in-place repair.

Can I uninstall KB5079473 if it causes problems? Yes, temporarily — via Update history → Uninstall updates. But it’s a security update, so treat removal as a short-term fix and reinstall once your system is stable.

Is KB5079473 causing freezes and BSODs? Some users reported crashes and freezes, though Microsoft’s page listed no known issues as of writing. If your PC became unstable right after installing, roll back, update drivers, and check the Windows release health dashboard.

Do I need earlier updates before installing KB5079473? No. It’s a combined package that includes the required servicing stack update, so it installs without a long prerequisite chain.

Does KB5079473 apply to Windows 11 23H2 or older? No. KB5079473 is for 24H2 and 25H2. The 23H2 equivalent that month was KB5078883.

If KB5079473 damage forces an in-place repair or clean reinstall and you need to reactivate, Kymakers supplies genuine Windows 11 Pro and Windows 11 Home keys with instant delivery and activation support. Our guide to downloading, installing, and activating your Microsoft license covers the process, and if the update left the PC unbootable, no operating system installed covers that case.

Run SFC and DISM first. Install manually if Windows Update is stuck. In-place repair when 0x80073712 won’t clear.

Official reference: March 10, 2026—KB5079473 — Microsoft Support