Microsoft admits its September Windows 11 update is breaking backups and blocking some PCs from booting

Microsoft has confirmed that its latest mandatory Windows 11 update is causing a cluster of problems ranging from silently failing backups to some laptops refusing to start at all. The admission lands just days after the company had urged Windows users not to delay installing the very same update, an awkward sequence that has left affected users weighing a known-buggy patch against the security risk of skipping it.

KB5124008 arrives as a mandatory September patch

The update in question, cataloged as KB5124008, was released on September 8 as part of Microsoft’s regular monthly patch cycle and was flagged as mandatory rather than optional. Mandatory updates typically install automatically on most consumer machines within a short window of release, which meant the bugs bundled inside KB5124008 reached a large number of devices before Microsoft had fully documented the scope of what was going wrong.

File History backups quietly stop working

One of the most disruptive issues involves File History, the built-in Windows backup tool many users rely on to automatically copy files to an external drive. Since the update went out, numerous users have reported that File History simply stops running, with the File History panel throwing an error even when the external drive remains plugged in and functioning normally. In several reported cases, the “last backup” timestamp shown in the tool freezes on a date from days or weeks earlier, giving no clear on-screen indication that backups had silently stopped rather than continuing as expected, meaning affected users could go a long stretch believing their files were protected when they were not.

Some HP laptops fail to boot after installing the patch

A smaller but more severe set of reports involves systems that cannot start up at all after installing KB5124008. Affected users describe black screens, BitLocker recovery prompts, Secure Boot errors, and boot loops that cycle without ever completing startup. The specific error code 0xc0430001, accompanied by a message reading “Code Integrity failed to initialize,” has come up repeatedly in these reports, and the pattern appears concentrated on certain hardware and firmware configurations, with a disproportionate share of complaints coming from owners of HP laptops. Microsoft has indicated the underlying cause traces back to how the update interacts with Secure Boot on those specific configurations, though the update installs without incident on the large majority of Windows 11 PCs.

Additional reported issues beyond backups and boot failures

Beyond the two headline problems, Microsoft has acknowledged that the update also breaks certain WSL-based applications, which rely on the Windows Subsystem for Linux, and disrupts some Remote Desktop sessions. Separate investigations by users and outlets tracking the rollout have surfaced additional complaints, including Explorer.exe crashes and instability affecting AMD graphics cards on some systems, suggesting the update’s problems extend across a wider range of subsystems than the backup and boot issues alone would indicate.

Why Secure Boot failures are harder to fix than a typical bug

Secure Boot is a firmware-level security feature designed to verify that only trusted, digitally signed software loads while a computer starts up, blocking malware that tries to hijack the boot process before the operating system itself is even running. When an update interacts badly with Secure Boot, as appears to be happening on the affected HP configurations, the failure occurs before Windows has fully loaded, which is why the symptoms include black screens and boot loops rather than an error message a typical software crash would display. That timing also makes the fix more complicated than an ordinary application bug, since some remediation approaches require booting into a recovery environment or reverting firmware-level settings rather than simply uninstalling a piece of software after the system has started normally.

What affected users can do while waiting for an official fix

For systems that still boot normally, Windows keeps a record of recently installed updates that can typically be uninstalled through the Windows Update history settings, a step that can reverse KB5124008’s changes on a machine experiencing the File History bug without requiring a full system reset. Machines already stuck in a boot loop generally need to be repaired through the built-in Windows recovery environment, which can attempt to undo a recent update or roll the system back to a previous restore point, though the exact recovery path varies by manufacturer and by how severely the Secure Boot failure has affected the device. Anyone relying on File History as their only backup method has particular reason to verify recent backups completed successfully using an alternate method, given how quietly the tool has been reported to fail without an on-screen warning.

A patch users were just told not to delay

What makes the timing particularly awkward is that Microsoft had urged Windows 11 users to install updates promptly rather than postponing them, guidance issued only days before the company had to publicly acknowledge the scope of problems inside this specific release. That sequence leaves affected users in an uncomfortable position: skipping or delaying the update avoids the newly discovered bugs but also forgoes whatever security fixes the patch was meant to deliver, while installing it on an unsupported hardware configuration risks a boot failure or a backup tool that stops working without any visible warning. Microsoft has not yet detailed a firm timeline for a follow-up fix, leaving affected users to monitor official guidance for a corrective update addressing the File History and Secure Boot problems specifically.

This article was produced with AI assistance and edited by Morning Overview staff.

More from Morning Overview