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.
What Happened
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.
Users in Microsoft Community Hub threads report three symptoms:
- The “last backup” or “last copied” timestamp freezes, even though File History appears to run.
- New or edited files don’t show up under Properties > Previous Versions.
- File History shows “Reconnect your drive” while the drive is connected.
Microsoft has confirmed part of this. Microsoft’s KB5124010 release notes list a fixed known issue where File History “might fail to back up or restore files to an external drive or network location,” with an incorrect “Reconnect your drive” message even when a working backup drive is connected. Microsoft says updates released from KB5124010 onward resolve that issue.
A Tech Community discussion of the KB5124010 known issues repeats Microsoft’s wording. The claim that symptoms persist after those fixes comes from user reports, not from Microsoft.
Who This Affects
The reports cite Windows 10, version 22H2, and Windows 11, versions 24H2 and 25H2. KB5127648 also covers Windows 11, version 26H2, but the reports we found don’t mention 26H2. They come from people using built-in File History with local external drives or SMB shares. No source puts a number on how many PCs are affected. Treat this as a bug some users report, not a confirmed widespread outage.
How It Stacks Up: The Timeline
| Update | Platform | What’s reported | Source |
|---|---|---|---|
| KB5101684 | Windows 11 | First update users blamed for File History failures. The link comes from users only. | Tech Community |
| KB5120249 | Windows 10 22H2 | Same symptoms reported again | Tech Community |
| KB5124010 (Sept. 22, 2026) | Windows 11 | Microsoft’s release notes say it fixes File History failing to back up or restore to an external drive or network location, and the false “Reconnect your drive” message. Users say File History still has problems after later updates. | Known issues thread, follow-up |
| KB5127648 / KB5126657 (ESU) | Windows 11 / Windows 10 22H2 | Some thread posters report drive detection returning, but say the last-backup date still doesn’t update (anecdotal, Nov. 7, 2026 thread posts). Microsoft hasn’t confirmed a new defect. | Tech Community |
A separate thread follows Windows Latest’s outreach to Microsoft about the KB5124010 bug. No source names a confirmed root cause. Several reports describe data landing on the backup disk while the status screen stays stale. That points to the catalog or display layer as the failing piece, but nothing has proven it.
The Reaction
We couldn’t independently verify any reaction on X, Reddit, or Hacker News. A search summary of X found little to no discussion. No matching Hacker News stories turned up, and Reddit wasn’t checked. For now, the conversation lives in Microsoft’s own Community Hub threads.
What to Do Next: Verify Your Backups Directly
Don’t trust the status screen in either direction. It can show an old date while backups run, and it might look healthy while new versions aren’t saved. Check the backup itself:
- Open the backup drive or network share in File Explorer.
- Browse into the folders File History created and sort by Date modified.
- Edit a test file in Documents, then go to Control Panel > All Control Panel Items > File History and click Run now. Community replies suggest this. The exact location may differ slightly on your Windows build.
- Confirm a newly dated copy of that file shows up on the drive, then restore it to a different folder and open it.
If no new copy shows up, your backups aren’t current, whatever the screen says. A successful test only proves that folder and that run worked, so repeat it now and then and spot-check other folders you back up.
Our Take
Keep Windows on the latest cumulative update Windows Update offers you, for its security fixes and because Microsoft says KB5124010 and later builds fix the File History backup failure and false “Reconnect your drive” message. Don’t expect an update to guarantee the stale-date symptom is gone, though: some users report it after later updates. Those are community reports; Microsoft hasn’t confirmed a new defect in KB5127648.
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 in this story as history, not as your update target. Uninstalling an update isn’t an official fix, and nothing shows a rollback helps. Our worry level is moderate.
You can’t tell a stale date apart from a real backup failure without checking. The date is harmless only for the folders and runs your tests confirm, so keep testing. Until those tests consistently pass, keep a second copy of your important files. OneDrive or a spare external hard drive both work as a contingency.
Wrapping Up
Microsoft’s documentation says KB5124010 and later updates fixed File History failing to back up or restore and the false drive-reconnect message. Some users say they still see a frozen backup date or missing Previous Versions entries after more recent updates, and Microsoft hasn’t confirmed a new defect. We couldn’t independently confirm which updates or symptoms are involved.
Run the test-file check after every Patch Tuesday. If a fresh copy lands on the drive and restores cleanly, File History is doing its job even when the screen says otherwise.
