Windows 11’s March Update Is Crashing Some PCs — Here’s What We Actually Know

Microsoft’s KB5079473 shipped on Patch Tuesday with fixes for dozens of vulnerabilities. Days later, a wave of user complaints about blue screens and freezes surfaced — but the full picture is more nuanced than viral posts suggest.

Microsoft rolled out KB5079473 on March 10, 2026, the company’s monthly Patch Tuesday cumulative update targeting Windows 11 versions 24H2 and 25H2. The release advanced both branches to new OS builds — 26100.8037 for 24H2 and 26200.8037 for 25H2 — and was billed primarily as a security-focused maintenance release bundled with a handful of quality-of-life improvements.

The security payload is substantial: roughly 79 vulnerabilities were addressed, including two zero-days described by Microsoft as under limited active exploitation. For most users, that alone is a compelling reason to install the update.

The Complaints: What Users Are Reporting

Within 24 to 72 hours of the update’s initial rollout, a wave of complaints appeared across Microsoft’s Q&A forums, Reddit, and independent community boards. The problems are real, though their precise scope remains unclear.

A Microsoft Q&A post published on March 12 described a PC that “fully crashed 3 times” after installing KB5079473, with each crash wiping unsaved work. Follow-up comments in the same thread reported complete screen freezes requiring hard restarts, and crashes that occurred repeatedly during Zoom screen-sharing sessions.

“My system began restarting every 10 to 20 minutes after the update, and I documented a BSOD with the stop code ATTEMPTED_WRITE_TO_READONLY_MEMORY.” — User post, Microsoft Q&A forum, March 2026

A separate forum thread catalogued a broader range of failures. Here is a summary of the issues users have documented:

• BSOD System crashes with stop code ATTEMPTED_WRITE_TO_READONLY_MEMORY (0xBE); also reported: DRIVER_IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, KMODE_EXCEPTION_NOT_HANDLED, PAGE_FAULT_IN_NONPAGED_AREA.
• Freeze Complete screen freezes requiring hard restarts; unexpected reboots cycling every 10–20 minutes; blank or black screen loops post-update.
• Apps Microsoft Office and Outlook failing to initialize; Command Prompt unresponsive; Print Screen shortcut broken; error code 0x800704b3 when launching system executables.
• Install Update failing to complete, stalling at 96–100% with errors 0x80070306 and 0x800f081f; repeated “Installation failed” prompts.
• Samsung C: drive reported inaccessible and storage partitions unreadable — primarily on Samsung Galaxy Book models. (See below for the full story on this.)

GPU-heavy workloads — gaming in particular — also appear to be a fault line. Titles using DirectX 12 and anti-cheat systems have been cited frequently, with crashes correlating to interactions between the updated OS kernel components and existing NVIDIA or AMD graphics drivers. Dell Precision workstations and high-end gaming configurations appear in community posts with elevated frequency.

The Samsung C: Drive Bug Is Not Windows’ Fault

This matters because a significant portion of the social-media outrage around KB5079473 conflated the Samsung app bug with Windows Update issues. Microsoft’s investigation cleared the update of responsibility for the drive-access failures, which were resolved by updating or removing the Galaxy Connect application.

Microsoft’s Official Stance: “No Known Issues”

Despite the volume of user complaints, Microsoft’s official support page for KB5079473 continued to list the “Known issues in this update” section as empty as of the time of publication. The company has not issued a formal advisory, a Known Issue Rollback (KIR), or any public acknowledgement that the update is the root cause of the stability problems being reported.

The most technically plausible root causes, based on the patterns in user reports, involve driver compatibility: specifically, interactions between kernel-level changes in KB5079473 and older NVIDIA or AMD graphics drivers, gaming anti-cheat software operating at kernel level, and in some cases, BIOS/firmware that cannot handle the updated Secure Boot Key Exchange Key certificates now being deployed by the update. Users with older motherboard firmware who have not updated their BIOS may encounter boot-path errors after installation.

What To Do If Your PC Is Affected

If your system is currently unstable

1. Pause further updates. Open Settings → Windows Update and pause updates to prevent the patch from reinstalling after a rollback.
2. Uninstall KB5079473. Go to Settings → Windows Update → Update history → Uninstall updates, locate the March 2026 quality update, and remove it. Most users who have done this report that their system returns to a stable state.
3. If the Settings UI fails, open an elevated Command Prompt and use the Windows Update Standalone Installer to uninstall the package manually.
4. If the system will not boot normally, enter Safe Mode or the Windows Recovery Environment (WinRE) and uninstall from there. Use a System Restore point dated before March 10 as a fallback.

Before reinstalling the update

1. Update your graphics drivers (NVIDIA, AMD, or Intel) to the latest version from the manufacturer’s website.
2. Update your motherboard BIOS/UEFI firmware to ensure compatibility with the new Secure Boot certificates.
3. If you use gaming anti-cheat software (Easy Anti-Cheat, Vanguard, etc.), check whether compatible updates are available from game developers.
4. Create a System Restore point before attempting to reinstall the cumulative update.

For enterprise and IT administrators: consider pausing the KB5079473 rollout via WSUS or Intune, testing on a representative subset of hardware configurations, and staging deployment until driver vendors have published compatible updates. — Recommended practice, Windows Forum

The Security Trade-Off

Delaying or uninstalling KB5079473 carries its own risks. Two of the vulnerabilities patched in this release are documented as actively exploited in targeted attacks. Skipping the update entirely is not advisable for extended periods, particularly on internet-facing machines or devices handling sensitive data.

The practical guidance for most users: if your system is currently stable after installation, leave the update in place. If you are experiencing crashes or instability, uninstall the update, address driver and firmware currency, and monitor Microsoft’s support documentation for a refreshed cumulative update or Known Issue Rollback that addresses the compatibility problems.

The Bottom Line

KB5079473 is a legitimate security update that patched approximately 79 vulnerabilities in Windows 11 24H2 and 25H2. A real — but apparently hardware-specific — subset of users encountered stability problems including blue screens, freezes, reboot loops, and application failures after installation, with the most commonly documented stop code being ATTEMPTED_WRITE_TO_READONLY_MEMORY (0xBE). The Samsung C: drive bug, though widely attributed to the update, was separately caused by the Galaxy Connect app.

Microsoft has not formally acknowledged the stability reports. Uninstalling the update resolves the instability for most affected users. The situation continues to develop; check Microsoft’s official support documentation for KB5079473 for any new Known Issue disclosures.