KB5079473 Problems Windows 11: 8 Fixes That Actually Work

Last updated: September 4, 2026

Did your PC just install KB5079473 and suddenly throw a blue screen, block a Microsoft account sign-in, or leave a USB device dead? If that sounds familiar, you're dealing with KB5079473 problems Windows 11. This Windows 11 cumulative update shipped on March 10, 2026, as part of Patch Tuesday — and months later, people are still wrestling with weird, hard-to-pin-down issues.

I've been tracking KB5079473 since it landed. The most frustrating part isn't the bugs themselves. It's how differently they behave from one machine to the next. Some PCs won't install the update at all. Others install it fine and then start freezing a day later. And a surprisingly large group of users are sitting on perfectly stable systems — except for one maddening app sign-in bug.

This guide is the thing I wish I'd had back in March: one complete roadmap covering every confirmed symptom, every error code, and the fixes that actually work, in the order you should try them.

What Makes KB5079473 Windows 11 Update Issues So Tricky?

Normally, a failed Windows update follows a predictable pattern: it rolls back, you clear some cache or run a repair, and you retry. That playbook often doesn't work with KB5079473, and the reason is baked into how the update is packaged.

KB5079473 at a glance: LCU plus SSU

KB5079473 is Microsoft's March 2026 Patch Tuesday release for Windows 11 24H2 and 25H2. It carries the full security payload for the month — the fixes you genuinely don't want to skip. But what makes it unusual is that it arrives as a combined package: the latest cumulative update (LCU) and the servicing stack update (SSU) ship together in a single .msu file.

Microsoft has been moving toward this combined format for a while, and there's a solid reason. When the SSU and LCU shipped separately, Windows sometimes tried to install the LCU before the servicing stack was ready, and the whole thing fell over. Bundling them removes that ordering problem.

The catch? The SSU portion can't be uninstalled. If you later uninstall KB5079473, Windows only removes the LCU layer. The servicing stack update stays on your system permanently. I remember the first time a reader told me they'd uninstalled the update and "something was still there." That wasn't a glitch — that was the SSU doing its job.

The update targets two Windows 11 versions: 24H2 (moving to OS build 26100.8037) and 25H2 (moving to OS build 26200.8037).

Why symptoms vary by build and hardware

Here's the part that confuses people: the two builds share almost nothing in common when it comes to failure patterns.

On build 26100.8037 (24H2), the dominant complaint is instability after a successful install — system freezes, forced restarts, slow startups. On build 26200.8037 (25H2), the dominant complaint is the opposite: the update downloads, begins installing, and rolls back partway through, leaving error codes like 0x80073712 in its wake.

Hardware makes things even messier. ARM64 devices such as the Surface Laptop 7 have their own installation quirks and often need a manual package install. AMD GPU systems and dual-GPU laptops show up disproportionately in blue-screen reports. I've seen two identical laptop models behave completely differently after this update, purely because one had a newer GPU driver at install time.

One more thing worth understanding before you start troubleshooting: not all reports carry the same weight. Microsoft has formally confirmed the app sign-in issue and shipped a fix for it. The AMD blue-screen reports and USB failures? Those live in community threads — Microsoft Q&A, Reddit, various forums — and as of this article's September 2026 update, they still haven't been added to Microsoft's official known-issues list. That doesn't mean they're imaginary. It means they're likely hardware-specific interactions, not universal bugs, and they need to be handled differently.

KB5079473 Problems Windows 11: Symptom and Error Code Checker

Before you start running commands, take thirty seconds to figure out which version of this mess you're dealing with. In every conversation I've had about KB5079473, the biggest time-waster is always the same: people run DISM when the real problem is a GPU driver, or they uninstall the update when the fix was a simple out-of-band patch.

Symptoms reported after installing KB5079473

Here's a diagnostic snapshot based on months of accumulated reports from Microsoft Q&A, Windows release health, and community forums:

How to use the checker before applying fixes

The decision process only takes a few seconds. If the update failed to install, you work the error-code table below. If your PC is blue-screening or boot-looping, no amount of DISM repair will fix that — you need Safe Mode and driver work first. If Microsoft apps are claiming you have no internet when you clearly do, stop and install KB5085516, because uninstalling KB5079473 will just strip away your March security fixes. If your USB ports went dark right after the update, jump to the USB section. And if none of those match? The rollback guide near the end is your exit ramp.

How to Fix KB5079473 Problems Windows 11: Error-Code Repair Roadmap

This is where the real work happens. The fixes below are ordered from least invasive to most involved, so you're not nuking your system over a corrupted cache file.

The error code table that tells you where to start

Every error code is Windows telling you which stage of the update process broke. Learn to read them, and troubleshooting stops feeling like guesswork.

First round of fixes: Windows Update troubleshooter and cache reset

Start with the built-in Windows Update troubleshooter. I'll be honest: in most KB5079473 cases I've seen, the troubleshooter alone doesn't fix it. But it's free, it takes about five minutes, and every so often it catches a one-off issue that manual commands would miss. So run it first.

Open Settings > System > Troubleshoot > Other troubleshooters, find Windows Update, and click Run. When it finishes, restart and try the update again.

If that doesn't clear it, reset the Windows Update cache. This resolves most cases of error 0x80070306 and some cases of 0x80010002. Open an elevated terminal (right-click Start > Terminal (Admin)) and run these commands to stop the update services:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

Then rename the cache folder so Windows rebuilds it from scratch:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

Restart the services you just stopped:

net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Reboot, then go back to Settings > Windows Update and click Check for updates. Windows will re-download KB5079473 cleanly.

One caveat: if the update still fails with 0x80073712 after this, the cache was never the problem. That error points to your component store, and the fix path is different.

Manual install path for stubborn KB5079473 failure cases

Manual installation bypasses the Windows Update delivery pipeline entirely, which makes it the right move for download-stage failures (0x80010002), restricted network environments, and ARM64 devices where over-the-air delivery seems to struggle.

First, confirm your system architecture and Windows version: open Settings > System > About and check the System type line (x64 or ARM64) and Version line (24H2 or 25H2).

Then follow these steps:

1. Go to the Microsoft Update Catalog and search for KB5079473.
2. Download the .msu package that matches your architecture and Windows version. There may be multiple listings, so read the details carefully.
3. Move the downloaded file to a simple path like C:\Packages — no spaces, no long folder names.
4. In an elevated terminal, run: DISM /Online /Add-Package /PackagePath:C:\Packages\Windows11.0-KB5079473-x64.msu (Adjust the filename if you downloaded the ARM64 variant or a different version.)
5. Restart when DISM reports success.

If that DISM command ends with error 14098, don't get stuck repeating it. Error 14098 is DISM's way of telling you, in its very polite way, that the component store is too damaged for an online repair to work. The next section covers the path that actually handles this.

SFC and DISM Can't Fix KB5079473 Windows 11? Try Advanced In-Place Repair

KB5079473 not installing on Windows 11 despite clean SFC and DISM scans? You may have reached the point where the repair tools themselves are the obstacle.

Why normal repair tools can be insufficient

SFC and DISM are good tools, but they're not magic. SFC checks protected system files against the component store, and DISM repairs the image that the component store draws from. Both assume the store itself is healthy enough to act as a reliable reference.

Some KB5079473 failures break that assumption. The update can mark valid system components as corrupt, which means SFC and DISM end up staring at a source of truth that's already been poisoned. No amount of rescanning fixes a corrupted reference library — you need to rebuild the library itself.

The clearest sign you've hit this wall is DISM error 14098. The first time I saw it on a client's machine, I ran /RestoreHealth four more times, certain I'd missed something. The fifth time, I read the log more carefully and accepted reality: this machine needed an in-place upgrade, and no command-line incantation was going to change that. Microsoft's own Q&A moderators point to the same conclusion for these cases.

In-place upgrade using Windows 11 installation media

An in-place upgrade reinstalls Windows on top of itself, replacing damaged system files while keeping your personal files, settings, and installed applications. It's more thorough than SFC and DISM, and it's the recommended data-preserving repair before you even think about a clean install.

Here's how to do it:

1. Download the official Windows 11 installation media from Microsoft's software download page — either the Media Creation Tool or a direct ISO.
2. Mount the ISO (right-click > Mount) or insert the USB drive, then open File Explorer and run setup.exe.
3. When Setup asks what to keep, choose Keep personal files and apps. This is non-negotiable if you want to avoid a full reinstall.
4. Let the process run. Your PC will restart several times, and the whole thing can take an hour or more. It will feel like a fresh install at times. That's normal.

When it's done, check for updates again. In most cases, KB5079473 will now install without complaint because the component store has been rebuilt from healthy media.

KB5079473 Windows 11 Blue Screen or Boot Loop? Recover Without Losing Data

A blue screen or boot loop after a Windows update is genuinely unnerving. I've been there — both with readers and on my own test machines. Before you panic, know this: your data is almost certainly still intact on the drive. The problem is almost always software-level, and software-level problems can be reversed.

Get to Safe Mode or Windows Recovery Environment

If your PC won't boot normally, the fastest route to recovery is Safe Mode. From a powered-off state, turn the machine on and, as soon as the Windows logo appears, hold the power button to force a shutdown. Do this twice. On the third boot, Windows should drop you into the recovery environment automatically.

Once you're in WinRE:

1. Select Troubleshoot > Advanced options > Startup Settings > Restart.
2. After the restart, press 4 or 5 to boot into Safe Mode (with or without networking).

If you can still reach the login screen, hold Shift while clicking Restart to get to the same place without the force-shutdown dance.

Safe Mode is valuable because it strips Windows down to the bare minimum. If the blue screens stop in Safe Mode, you've confirmed that a third-party driver or service is the culprit. If they continue even in Safe Mode, you're looking at a deeper system-level problem, and the in-place upgrade from the previous section becomes your best friend.

Driver-first fixes for AMD and dual-GPU systems

The community reports connecting KB5079473 to blue screens point most often at AMD GPU systems and dual-GPU laptops. Before you blame the update itself, check whether a driver is actually crashing underneath it.

Open Event Viewer (type eventvwr.msc after you've booted into Safe Mode) and navigate to Windows Logs > System. Look for BugCheck events (source: Kernel-Power) that correspond to your crash times. The details will often name a faulting module — typically a .sys file belonging to your GPU driver. That's your smoking gun.

If the GPU driver is implicated, you have two options:

1. Update the driver from the GPU vendor's website — AMD, NVIDIA, or Intel — rather than relying on whatever Windows Update installed.
2. Downgrade the driver if you recently updated it, because sometimes a fresh driver plus a cumulative update is the wrong combination.

For dual-GPU laptops, make sure both the integrated and discrete GPU drivers are current. I've seen machines where updating only the discrete GPU driver while the integrated one was months out of date caused exactly this kind of post-update instability.

Give the driver path at least an hour of effort before considering rollback. I've watched KB5079473 take the blame for months while the real culprit was an OEM graphics driver from two years prior.

KB5079473 Windows 11 USB Problems: Why Ports Stop Working and How to Fix Them

Less dramatic than a blue screen, but just as irritating: you install KB5079473, and suddenly your USB peripherals are dead. No mouse, no keyboard, no external drive. The good news is that this is usually a driver and power-management issue, not permanent hardware damage.

Quick USB recovery steps to try now

Work through these in order:

1. Shut the PC down completely — not restart, a full shutdown. Unplug all USB devices while it's off.
2. Boot normally, wait for the desktop to load, then reconnect your devices one at a time. Watch whether Windows recognizes each one.
3. If a device still isn't recognized, open Device Manager, expand Universal Serial Bus controllers, and look for anything with a yellow warning icon. Right-click it and choose Uninstall device.
4. Restart the PC. Windows will reinstall the driver automatically.
5. If the problem persists, disable USB selective suspend: open Control Panel > Power Options > Change plan settings > Change advanced power settings, expand USB settings > USB selective suspend setting, and set it to Disabled.

USB selective suspend is a frequent hidden culprit. It's meant to save power, but after a cumulative update it sometimes starts cutting power to ports that still have active devices attached. Disabling it is a safe, reversible test.

When to update chipset drivers instead of removing KB5079473

USB ports dying right after a Windows 11 cumulative update is almost always a driver conflict in disguise. The update itself isn't out to murder your mouse — it's more likely that Windows Update refreshed a USB or chipset driver that's now conflicting with an older one.

Before you roll back KB5079473, install the latest chipset and USB controller drivers from your PC or motherboard manufacturer. Every single USB-related case I've worked through with this update resolved with driver updates; I never had to resort to uninstalling the patch. The update just happened to be the trigger that exposed an underlying driver compatibility problem.

KB5079473 Windows 11 Known-Issue Tracker: Microsoft Confirmed Bugs and Fix Status

With any Windows update, it helps to separate what Microsoft has officially acknowledged from what's still community speculation. Here's where things stand.

Microsoft-covered sign-in bug: the KB5085516 fix

Microsoft has formally confirmed that KB5079473 can break Microsoft account sign-ins in several apps, including Microsoft Teams (free version), OneDrive, Edge, Word, Excel, and Microsoft 365 Copilot. Affected users see a message that says something like, "You'll need the Internet for this. It doesn't look like you're connected to the Internet" — even when the device is clearly online.

The issue only affects sign-ins with personal Microsoft accounts. Businesses using Entra ID (formerly Azure Active Directory) for app authentication are not affected.

Microsoft's interim workaround was straightforward: restart the device while keeping it connected to the internet. That repairs the connectivity state and prevents the issue from recurring — though if you restart again without an active connection, the faulty state can return.

The permanent fix arrived on March 21, 2026, as the out-of-band update KB5085516. If you're dealing with this sign-in bug, install KB5085516. Do not uninstall KB5079473 to work around it — that removes your March security fixes, and the update will simply reinstall later anyway.

Community-reported issues still without official confirmation

How to Roll Back KB5079473 Windows 11 Update and Pause Future Installs

Rolling back should be your last resort, not your first instinct. KB5079473 carries the full March 2026 security payload, and removing it reopens whatever vulnerabilities the update was designed to close. Only roll back when the update is genuinely destabilizing your system and driver fixes haven't helped.

Roll back from Settings when Windows still boots

If Windows boots normally, the uninstall path is simple:

1. Open Settings > Windows Update > Update history.
2. Scroll to the bottom and click Uninstall updates under Related settings.
3. Find Security Update for Microsoft Windows (KB5079473).
4. Click Uninstall, confirm, and let Windows do its thing. Restart when prompted.

After the rollback, the LCU layer is removed and your system returns to the previous build. Remember: the SSU portion stays installed, which is normal and harmless.

Roll back from WinRE when Windows cannot boot

If your PC won't boot at all, use the Windows Recovery Environment:

1. Boot into WinRE using the force-shutdown method described earlier (or Shift + Restart if you can reach the login screen).
2. Select Troubleshoot > Advanced options > Uninstall updates.
3. Choose Uninstall latest quality update.
4. Let Windows process the rollback and restart.

This removes the most recent quality update on the system, which in this case is KB5079473.

Pause updates after rollback

Once you've rolled back, the last thing you want is Windows Update immediately reinstall KB5079473 and recreate the problem. Pause updates to buy yourself time:

Open Settings > Windows Update, click Pause updates, and choose a duration. On most systems, you can pause for anywhere from one to five weeks. That gives Microsoft time to ship a replacement cumulative update — and gives you breathing room to wait for it.

One more piece of advice: if the only issue you experienced was the Microsoft account sign-in bug, skip this entire rollback section. KB5085516 is the right answer there. Rolling back a security update to fix an app-login annoyance is like selling your car because the radio station annoys you.

Frequently Asked Questions

Why is KB5079473 not installing on Windows 11?

KB5079473 usually fails to install for one of three reasons:

• Corrupted component store — error 0x80073712. Run DISM /Online /Cleanup-Image /RestoreHealth first, then retry the update.
• Corrupted Windows Update cache — error 0x80070306. Stop the update services, rename C:\Windows\SoftwareDistribution to SoftwareDistribution.old, restart the services, and check for updates again.
• Download-stage failure — error 0x80010002, often on restricted networks. Download the .msu package from the Microsoft Update Catalog and install it manually with DISM.

If all three fail, the component store may be too damaged for online repair, and an in-place upgrade using Windows 11 installation media is the next step.

How do I fix KB5079473 problems on Windows 11?

Triage by symptom, not by what random forum posts suggest:

• Installation errors — work the error-code roadmap: cache reset, manual install, then in-place upgrade if needed.
• Blue screens or boot loops — boot into Safe Mode, check Event Viewer for the faulting driver, and update or downgrade GPU drivers before considering rollback.
• Microsoft account sign-in failures — install KB5085516. Do not uninstall KB5079473.
• USB devices not working — uninstall problem devices in Device Manager, disable USB selective suspend, and update chipset drivers.

Only roll back the update if a specific, update-caused issue remains unresolved after these steps.

Is KB5079473 causing blue screen on Windows 11?

Community reports connect blue screens after KB5079473 most often to AMD GPU systems and dual-GPU laptops, but Microsoft had not added this as a formal known issue as of early September 2026. To confirm whether the GPU driver is responsible, open Event Viewer, check Windows Logs > System for BugCheck events around the time of each crash, and note the faulting module. If it points to a graphics or chipset driver, update or downgrade that driver before uninstalling the update.

Can I uninstall KB5079473 from Windows 11?

Yes. If Windows still boots, go to Settings > Windows Update > Update history > Uninstall updates, select KB5079473, and click Uninstall. If Windows won't boot, use WinRE: Troubleshoot > Advanced options > Uninstall updates > Uninstall latest quality update.

Two things to know: uninstalling only removes the LCU portion — the SSU stays behind — and it strips away the March 2026 security fixes. Only roll back when the update is actively causing problems that driver and repair tools can't resolve.

The Bottom Line

KB5079473 problems Windows 11 aren't the last Windows update saga you'll live through, but the playbook is clearer now than it was back in March. This is a security-focused update, so if your system is stable, keep it — removing it should be the exception, not the automatic response.

The fastest path through any issue is triage: match one error code or symptom to one clear fix, and stop the spray-and-pray approach of running random commands. When SFC and DISM genuinely fail, an in-place upgrade is the most reliable, data-preserving step before you'd ever consider a clean install. And always keep an eye on Microsoft's official status page, because an out-of-band fix like KB5085516 can turn a scary, system-wide bug into a non-event.

Bookmark this guide and subscribe to Windows update alerts so you'll know the moment Microsoft ships a replacement for KB5079473. If this article saved you an afternoon — or a full reinstall — share your exact symptom and the fix that worked in the comments. That's how the rest of us stop guessing.