File History Backup Bug KB5124008: Fix, Status, and Mitigation

On September 22, 2026, Microsoft released KB5124010 and KB5124006 to address issues affecting Windows 11 File History. Both updates are optional previews. The trouble began on September 8 with the release of the security update KB5124008 for Windows 11 24H2 and 25H2. This update left File History displaying a “Reconnect your drive” message while it quietly stopped backing up files. Microsoft lists the same known issue on its September update pages for other Windows versions, and as of September 26, it remains listed as unresolved on Windows 11 23H2 as well as Windows 10 versions 21H2/22H2, 1809, and 1607.

Microsoft’s documentation establishes a clear timeline of events. Every date provided comes directly from Microsoft support pages or from ghacks.net’s September 25 report.

Documented Symptoms and Mechanism

Microsoft documented three primary symptoms on affected personal computers. Behind the scenes, Event Viewer logged crashes tied to FileHistory.exe and KERNELBASE.dll, which serves as a key detail for help desk readers. The backup engine itself was crashing, alongside the status display.

File History runs in the background. Most users configure the tool once and never open it again. Consequently, a failure that lacks a loud onscreen error is a failure nobody notices.

The “Reconnect your drive” message compounded the problem. If a backup drive remained plugged in, the notification appeared to be a minor glitch that users could safely ignore. Meanwhile, new and modified files were not being copied. Based on Microsoft’s dates, certain computers could have operated for roughly two weeks without a functional backup, spanning from September 8 to September 22. Users would remain unaware until attempting to restore a file and encountering a “No previous version available” prompt.

Data Impact and Security Implications

If you do not use File History at all, this bug does not touch your files. It only matters if File History backs up to an external hard drive or network share.

Microsoft’s documentation does not indicate that existing backup data was deleted. The documented symptoms consist of backups that ceased updating and a restore interface that could not display earlier versions. The safest interpretation is that new backups stopped executing. Whether older versions remained readable during the bug’s active window is not specified.

Regardless, users should avoid formatting, wiping, or repurposing their backup drive while troubleshooting the issue. A two-week window from bug introduction to fix deployment is relatively quick for the newest Windows 11 branches. The actual gap persists on older versions, which are precisely the machines that home offices and family computers tend to retain.

Built-In Backup Options Comparison

Microsoft has not instructed users to stop utilizing File History and has deployed a fix. The built-in options compare as follows, based strictly on supported research:

Nothing in Microsoft’s documentation argues for abandoning File History entirely. A secondary backup layer, such as OneDrive folder backup or a file copy directed to a separate portable SSD, would have successfully captured this gap.

Industry Coverage and Discrepancies

Coverage of the File History backup bug has been largely informational. Windows Latest reported on September 23 that the false “Reconnect your drive” alert appeared on drives functioning properly elsewhere, noting that File History worked again after installing KB5124010 but was not fully patched for everyone due to a reader’s manual Run command failing to update the Last Backup timestamp. PCWorld emphasized on September 23 that the fix is optional and will not install automatically, noting otherwise that it arrives with October’s Patch Tuesday, while also suggesting the uninstallation of the September security update as a temporary stopgap. BleepingComputer covered both the system breakage and the subsequent remediation.

This “it is fixed” framing contributes to confusion. Microsoft’s own support pages continue to list Windows 11 23H2 and Windows 10 versions 21H2/22H2, 1809, and 1607 as unresolved. Skimming headlines could lead a user to assume their Windows 10 computer is secure when it is not. This quiet reaction matches a quiet bug, as users rarely express anger over backups they did not realize had failed.

Verdict: Install the Fix Now

Users should install the fix immediately without pausing updates or rolling back KB5124008.

For systems running Windows 11 24H2, 25H2, or 26H1, the fix is available and documented by Microsoft. Because it is distributed as an optional preview update, Windows will not install it automatically, requiring manual installation. Pausing system updates leaves computers on the broken build for an extended period. Rolling back KB5124008 is not a remedy listed by Microsoft and would strip out that month’s security patches. Microsoft also does not describe any manual workaround. Because the issue is resolved in Windows updates released on and after September 22, 2026, subsequent monthly updates for these versions will incorporate the fix. The September 22 preview simply provides immediate access rather than waiting.

Assessing Your Risk Level

Users should remain moderately worried, but only for a specific timeframe. The primary risk is not lost historical backups, as Microsoft’s documentation contains no indication that past data was erased. Instead, the risk is that files created or modified between September 8 and the application of the fix may never have been backed up. If a drive failed or a file was overwritten during that interval, File History may lack a recovery copy.

Users operating Windows 10 across any version or Windows 11 23H2 should exercise greater caution. Treat File History as unreliable until Microsoft designates a fixing KB for your exact build.

Step-by-Step Guidance for Affected Systems

On Windows 11 24H2, 25H2, or 26H1, install the fix and subsequently verify that File History executes correctly. For Windows 10 or Windows 11 23H2 users where no fix exists yet, proceed directly to the manual mitigation notes.

Verification of the installed update can be performed via PowerShell using the command `Get-HotFix -Id KB5124010`, substituting KB5124006 for version 26H1. If installed successfully, PowerShell outputs the corresponding KB identifier. If the command generates an error, check the build number via `winver` to match the build number published by Microsoft for the fix. For deeper troubleshooting, open `eventvwr.msc`, navigate to Windows Logs, select Application, and search for application errors referencing FileHistory.exe alongside KERNELBASE.dll. If these crashes persist following installation of the update, inspect the physical backup drive, keeping in mind reports that the patch may not be complete for all users.

Users on Windows 10 or Windows 11 23H2 should continue installing standard updates as they arrive, but avoid relying solely on File History. Manually copy essential folders to a secondary external drive or enable OneDrive folder backup for Desktop, Documents, and Pictures. Keep in mind that OneDrive synchronizes those directories to the cloud rather than maintaining versioned local backups, making it a secondary copy rather than a direct File History replacement. Monitor your specific version’s Microsoft Support page to identify the designated fixing KB.

Ultimately, the File History backup bug did not delete existing backups according to Microsoft’s documentation. Instead, it operated covertly by making the tool appear configured while failing to perform background backups. Across any operating system version, inspecting the Last Backup date remains the essential action to take.