On November 7, 2026, a Microsoft Tech Community thread reported that Windows File History still shows a stale “last backup” date after recent Windows 11 and Windows 10 updates. This article reflects information available as of that date and may not capture later developments.
Posts in that thread mention KB5127648 on Windows 11 and KB5126657 on Windows 10. KB5127648 is Microsoft’s October 13, 2026 cumulative update for Windows 11, and KB5126657 is that month’s Extended Security Update for Windows 10, version 22H2, which only reaches PCs enrolled in the Extended Security Updates program, per BleepingComputer. Some posters in that thread describe drive detection returning after those updates, but say the displayed backup date still won’t move. These are individual reports we couldn’t independently verify. Microsoft hasn’t confirmed a new defect in either update.
File History is the free backup tool built into Windows 10 and Windows 11. It copies the user folders you select to an external drive or network location on a schedule. It also feeds the Previous Versions tab in a file’s properties.
Windows File History Stale Backup Dates: What Users Are Reporting
Users across Microsoft Community Hub threads have highlighted persistent concerns following the application of recent cumulative and security updates. While some individuals note that drive detection mechanisms have recovered after installing packages like KB5127648 and KB5126657, the underlying status displays frequently fail to reflect active operations. These discussions remain entirely community-driven; Microsoft has not issued an official confirmation regarding a brand-new defect tied specifically to these updates.
Recognizing the Symptoms: Stale Timestamps and False Warnings
Discussions in Microsoft Community Hub threads point to three distinct symptoms experienced by users operating File History on Windows 10 and Windows 11:
- The “last backup” or “last copied” timestamp freezes, even though File History appears to run normally.
- New or edited files fail to show up under Properties > Previous Versions.
- File History erroneously displays a “Reconnect your drive” notification while the backup drive remains actively connected.
Official Microsoft Fixes vs. Unresolved Community Reports
It is important to distinguish between official documentation from Microsoft and unverified community observations. Microsoft previously confirmed a known issue—documented in KB5124010 release notes—where File History “might fail to back up or restore files to an external drive or network location,” accompanied by an incorrect “Reconnect your drive” message even when a working backup drive was plugged in. Microsoft stated that updates released from KB5124010 onward successfully resolve that specific issue.
A Tech Community discussion of the KB5124010 known issues repeats Microsoft’s wording, but claims that symptoms persist after those fixes originate purely from user reports rather than official Microsoft advisories. These reports cite Windows 10, version 22H2, and Windows 11, versions 24H2 and 25H2, as well as KB5127648 covering Windows 11 version 26H2 (though our found reports do not mention 26H2). Affected setups rely on built-in File History with local external drives or SMB shares. No source puts a definitive number on how many PCs are affected, meaning this should be treated as a bug reported by some users rather than a confirmed widespread outage.
A separate thread follows Windows Latest’s outreach to Microsoft about the KB5124010 bug, though no source names a confirmed root cause. Several reports describe data successfully landing on the backup disk while the status screen stays stale, pointing to the catalog or display layer as the failing component, though nothing has been definitively proven.
How to Verify Your Windows Backups Manually
Because status screens can prove unreliable—showing old dates while backups run or looking healthy while new versions are ignored—users must verify their archives directly. Follow these steps to test your backup integrity:
- Open your backup drive or network share directly in File Explorer.
- Browse into the specific folders created by File History and sort the contents by Date modified.
- Edit a test file in your Documents folder, then navigate to Control Panel > All Control Panel Items > File History and click Run now (note that the exact location may differ slightly depending on your specific Windows build).
- Confirm that a newly dated copy of that file appears on the backup drive, then test restoring it to a different folder and opening it.
If no new copy shows up, your backups are not current, regardless of what the screen indicates. A successful test only proves that folder and that specific run worked, so you should repeat the process periodically and spot-check other folders you back up.
Best Practices and Contingency Planning for Data Safety
Keep Windows on the latest cumulative update that Windows Update offers you for its essential security fixes, and because Microsoft states that KB5124010 and later builds fix the core File History backup failure and false drive-reconnect messages. However, do not expect an update to guarantee that the stale-date symptom will vanish, as some users continue to report it after later updates.
Microsoft’s Windows 11 update history also lists newer releases than KB5127648, including KB5134133 (out-of-band, October 26, 2026) and the KB5127936 preview (October 28, 2026), so treat the KB numbers discussed here as history rather than an update target. Uninstalling an update is not an official fix, and rollback procedures show no evidence of helping.
Because you cannot tell a stale date apart from a real backup failure without checking, treat dates as unverified until confirmed by testing. Maintain a second copy of your important files—using OneDrive or a spare external hard drive as a contingency—until your manual tests consistently pass after every Patch Tuesday.



































