Microsoft fixes Windows 11 File History bug in optional update
Manual installation required for immediate fix ahead of October Patch Tuesday
1Critical backup failure
A September 2026 Windows security update broke File History functionality across all current Windows 10/11 versions. The feature stopped creating new backups and incorrectly displayed 'Reconnect your drive' errors despite functional drives. Event logs showed crashes in FileHistory.exe and KERNELBASE.dll, leaving users unable to recover deleted files through historical versions that should have been automatically saved to external drives or network locations.
2Update rollout strategy
Microsoft released two optional KB updates (KB5124010 for 25H2/24H2 and KB5124006 for 26H1) containing the fix. These require manual installation through Windows Update's Optional Updates section. Without proactive installation, affected systems must wait until October's Patch Tuesday for automatic deployment. This staggered approach balances urgent fixes with enterprise update management protocols while maintaining the optional nature of non-security updates.
3Technical root cause
The bug manifested when the system incorrectly validated drive connections during backup operations. Despite proper hardware functionality, the software falsely triggered reconnection prompts and failed to update 'Last Backup' timestamps. The issue particularly impacted default backup locations including Documents, Music, Pictures, Videos and Desktop folders stored on USB drives or NAS devices, breaking the core promise of version recovery.
4User impact assessment
For professional users relying on File History for document versioning, the bug created significant business continuity risks. The temporary workaround required uninstalling the problematic security update, which itself carried security tradeoffs. Microsoft's three-week gap between bug discovery and optional fix availability left many users choosing between data protection and system security during the interim period.
5Enterprise implications
The incident highlights challenges in enterprise Windows management, where IT teams must balance immediate bug fixes against change control procedures. Optional updates require manual approval in managed environments, while automatic Patch Tuesday deployments create lag. Organizations using File History for compliance must now evaluate whether to accelerate non-standard updates or maintain existing update schedules.
6Backup ecosystem context
File History's continued inclusion in Windows despite Microsoft pushing OneDrive integration reflects its role as a local-first backup solution. The incident underscores the importance of testing update compatibility for legacy features still used by professionals for offline workflows. As cloud adoption grows, such bugs reveal tension between maintaining older systems and transitioning to modern platforms.
7Quality assurance lessons
The bug's presence across six Windows versions suggests a shared codebase vulnerability missed in pre-release testing. Microsoft's acknowledgment came only after user reports, indicating potential gaps in automated backup system monitoring. The company's 'working on a resolution' statement followed by rapid optional update suggests backend diagnosis was quicker than full QA certification.
8Proactive update management
This incident reinforces best practices for monitoring Microsoft's known issues database before deploying updates. Professionals should maintain alternative backup methods during major update cycles and validate core functionality post-installation. The optional-but-critical update scenario creates decision complexity for users weighing stability against feature availability between scheduled patch cycles.
Original article: PCWorld — Microsoft fixes Windows 11 File History bug in optional update