Microsoft has officially acknowledged an issue affecting the built-in File History feature following the release of its September 2026 security updates. The bug prevents users from creating new system backups or updating existing archives on external drives and network locations.
According to advisory documentation published by the company, affected systems frequently display incorrect error prompts and experience silent background application crashes. Microsoft confirmed that its engineering teams are investigating the root cause and preparing a permanent resolution for an upcoming cumulative patch.
windows 11 file history backup bug september update
The windows 11 file history backup bug september update stem from mandatory security updates deployed during the September Patch Tuesday cycle, most notably KB5124008. After applying these updates, users who rely on File History through the classic Control Panel interface reported that the system refused to execute scheduled or manual backup cycles. Rather than saving file modifications, the utility either halts entirely or reports that the designated target drive is disconnected.
Although the primary impact is felt on modern Windows 11 builds, the underlying regression extends to older operating system versions that retain the File History infrastructure. The flaw affects Windows 11 version 24H2, version 25H2, and version 26H1, alongside supported releases of Windows 10. While users can still access existing backup files manually through File Explorer, automated background versioning remains non-functional for those experiencing the issue.
Microsoft Acknowledges File History Failures in September 2026 Update
Microsoft formally added the backup malfunction to its list of known issues after receiving influxes of reports across official support forums and community channels. Tech community MVP Susan Bradley and independent administrative groups highlighted the problem after users noticed their secondary drives were failing to log daily changes. The advisory notes that systems running affected security builds may encounter unexpected application failures when attempting to execute background background tasks.
The issue occurs alongside other recent platform regressions, including documented cases where emergency updates left USB audio bugs unfixed across select desktop hardware configurations. In its public notice regarding the backup tool, Microsoft stated: "After installing the September 2026 Windows security update, some customers using File History might be unable to create or update backups." The software giant emphasized that the underlying data on backup drives remains intact and uncorrupted, even though the service cannot currently write new incremental snapshots.
Affected Builds and Key Symptoms
The backup regression impacts multiple client operating system updates released throughout the month. Systems running the following cumulative updates are susceptible to the glitch:
- Windows 11 Version 26H1: KB5124012
- Windows 11 Version 25H2 & 24H2: KB5124008
- Windows 11 Version 23H2: KB5122880
- Windows 10 Version 22H2 & 21H2: KB5122878
- Windows 10 Enterprise LTSC Releases: KB5122876 and KB5123099
Systems affected by the flaw typically display a persistent "Reconnect your drive" banner within the File History applet, even when external USB drives, local secondary disks, or Network Attached Storage (NAS) units are fully connected and accessible. Furthermore, the "Last Backup" timestamp inside Control Panel remains frozen on the date prior to update installation. Right-clicking a local file to view the Previous Versions tab may also incorrectly state that no prior versions are available. In the background, the Windows Event Viewer logs application crashes tied to FileHistory.exe referencing the system module KERNELBASE.dll.
Impact on System Backups and File Recovery
For home users and small business administrators who rely on localized continuous data protection, the bug leaves personal documents, pictures, and project directories unbacked up without explicit failure notifications. Because File History runs quietly in the background, many users only realize the service has stalled when attempting to restore a previous document revision or check drive status.
The problem is exacerbated by the fact that recent out-of-band patches released earlier in the month did not resolve the issue. For instance, emergency updates distributed to fix Remote Desktop Services regressions left the File History crash unaddressed. While Microsoft continues to work on modernizing legacy interfaces, such as recent efforts where tooling accelerates legacy dialog modernization, classic components like File History remain crucial for local snapshot redundancy.
System administrators who maintain automated file discovery settings, such as environments where Windows 11 Search automatically indexes user directories, report that file indexing functions normally while the actual copy process fails at the system kernel level.
Workarounds and Upcoming Resolution Details
Microsoft has confirmed that a official fix is currently in development and will be delivered in an upcoming cumulative update. In the interim, tech support representatives advise against attempting destructive troubleshooting methods, such as reformatting external storage drives or manually deleting local configuration files, as these actions will not bypass the application binary crash and may result in the loss of older snapshot histories.
Users requiring immediate, uninterrupted backup functionality are advised to consider temporary alternatives until Microsoft releases an official patch. Options include manually copying vital folders to external media, using cloud-based sync services like OneDrive, or deploying third-party image and file backup software. Systems where system recovery tools are required can also utilize native tools like Cloud Rebuild, especially as Cloud Rebuild now includes drive sanitization workflows for full system recovery scenarios.
Uninstalling the September security updates restores File History functionality, but security experts caution against removing monthly quality patches due to the critical vulnerabilities they address. IT administrators are advised to monitor the Windows Release Health dashboard for the upcoming release of a standalone or cumulative hotfix.
Microsoft has urged affected users to avoid deleting their current File History databases while awaiting the forthcoming software update, which will restore normal scheduled backup operations automatically once installed.
