Windows 11 machines that installed KB5124008, the mandatory September 8, 2026 security update, began failing to back up files through File History without ever showing an error that said so plainly. Instead, the feature displayed a false drive-disconnection warning, telling people to reconnect a drive that was plugged in and working, and left backups silently stalled for two weeks before Microsoft said anything about it.
The gap between the break and the acknowledgment is the part worth sitting with: a backup feature is only useful if people can trust its status indicator, and this one was lying to them for two full weeks before Microsoft said a word about it publicly.
What KB5124008 broke in File History
File History, the built-in Windows tool that copies files to an external drive or network location on a schedule, started misbehaving in several specific ways after the update landed. Drives that were connected and functioning normally in File Explorer stopped being recognized by the backup tool itself. The “last backup” timestamp froze or showed stale information instead of updating. Event Viewer logs on affected machines recorded crash events pointing to FileHistory.exe and KERNELBASE.dll, evidence that the process was failing outright rather than merely slowing down.
None of that produced a dialog box telling users their files were unprotected. It produced a warning that looked like a hardware problem — reconnect the drive — on hardware that had never disconnected. Anyone who trusted the message and moved on, rather than digging into Event Viewer, had no way of knowing backups had stopped.
Fourteen days between the bug and Microsoft’s admission
KB5124008 rolled out on September 8. Microsoft did not confirm the File History failure until September 22, according to Windows Latest‘s reporting on the timeline — a two-week window in which affected machines kept running with a backup feature that had quietly stopped working. When the acknowledgment came, Microsoft’s language was direct: “After installing the September 2026 Windows security update KB5124008, some customers using File History, might be unable to create or update backups.” KB5124008 itself advanced Windows 11 25H2 to build 26200.9445 and 24H2 to build 26100.9445, folding File History’s failure in alongside a separate list of issues that update had already introduced, including domain-joined devices losing their trust relationship and USB audio devices failing to start.
Users on Microsoft’s own support forums had already narrowed down the cause well before the official confirmation arrived. In a Microsoft Tech Community thread, one affected user traced the failure specifically to KB5122878 and reported that removing it restored File History, while another confirmed the same result after pulling KB5124008 — only to watch Windows reinstall the update automatically on the next update cycle regardless of their pause settings.
A fix arrived September 24, but not for everyone yet
Microsoft shipped KB5124010 on September 22, an optional preview update Microsoft describes as “the final preview update for Windows 11, version 24H2,” and it carries the File History repair alongside a batch of unrelated changes to File Explorer, emoji support, and Bluetooth reliability. Anyone who wants the fix immediately has to seek out an optional update manually through Windows Update, rather than waiting for it to arrive on its own. Microsoft’s plan for everyone else is to fold the same repair into the automatic October 13 Patch Tuesday release, more than a month after the original bug first appeared.
The gap between the two fixes leaves a stretch where two populations of the same Windows version exist side by side: machines whose owners went looking for KB5124010 and got working backups back, and machines that will keep showing the false drive-disconnection warning until October 13 unless someone intervenes manually in the meantime. Windows 11’s official release-health status page for 25H2, the page Microsoft maintains specifically to document known issues tied to each cumulative update, still does not list File History among the problems attributed to KB5124008, even after the September 22 acknowledgment reported elsewhere — a gap between what Microsoft told reporters and what it posted on its own tracker.
OneDrive as the stopgap, and what silent failure costs
Windows Latest’s reporting recommends switching to OneDrive for active backups in the meantime, since File History’s failure mode gives no reliable signal that it needs attention. A cloud sync tool that shows upload status per file does not share File History’s specific blind spot: a frozen timestamp and a misleading drive-connection error, both of which look like problems a user could dismiss rather than escalate.
The practical risk sits with anyone who assumed File History was doing its job during those two weeks. A drive failure, a ransomware infection, or a simple accidental deletion in that window would have met a backup set that stopped updating on September 8 and never said so, whatever the “last backup” field on screen happened to claim.
This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.
More from Morning Overview
- Older Teslas are wearing out in ways early owners never saw coming
- Early electric-car owners are hitting battery and screen failures no one warned them about
- A magnitude 5.3 quake struck off the Oregon coast this week
- Amazon’s Prime refunds are rising to $200 as millions more customers become eligible
