Forum Discussion
This issue occurred after I and other users installed KB5101684, disrupting File History.
My question
Hello,I would like to ask whether other Windows 10/11 users have experienced the same File History problem, and I hope Microsoft will seriously investigate it.
My laptop runs Windows 11 25H2. Before installing KB5101684, File History worked normally.
After installing KB5101684, I noticed:
- Last backup does not update correctly.
- Previous Versions still shows no previous versions.
- Files are still written to D:\FileHistory\..., but File History does not properly update its backup information.
- Folders such as Desktop and Favorites have their modification dates changed even when their contents were not changed.
- I did not manually change File History settings, registry settings, or delete Event Viewer entries.
I also experienced a similar problem on my Windows 10 22H2 desktop after installing KB5120249.
In short:
- Windows 11 25H2 → KB5101684 → File History problem
- Windows 10 22H2 → KB5120249 → File History problem
Could these updates have introduced a File History regression?
Microsoft, please investigate whether these KB updates are related to the incorrect backup timestamps, missing previous versions, and unexpected File History behavior.
Please do not simply ask users to reset File History or reselect the backup drive. Users need to know what is actually causing the problem and whether Microsoft will provide a fix.
If other Windows 10/11 users have experienced the same issue, please share your Windows version, KB number, when the problem started, and whether files are still being written to the FileHistory folder.
Please also consider sharing this post with other Windows users or Microsoft technical staff so this issue can receive proper attention.
Microsoft, please investigate this issue seriously and provide a clear explanation and solution.
Thank you.
The following are the problems that users and I encountered.
3 Replies
Thanks, Jamony, for your professional analysis and practical advice.
As you pointed out, the core danger here is that even though files are physically written to the D:\FileHistory folder, the broken restore catalog and misleading timestamps mean users cannot trust their backups when an actual emergency occurs. For a backup feature, losing trust in the restore function is a critical failure.
Other users are running into this exact same crisis after these recent updates, and they are left in the dark without official tracking or fixes. Since a backup system giving false reassurance poses a severe risk to user data, I strongly urge the Microsoft team to escalate this as a high-priority servicing regression rather than treating it as isolated configuration errors.
We truly need an official investigation and a reliable fix from Microsoft so users don't have to live in fear of silent backup failures.
There were no errors in the OS build, update history, event viewer errors, or restore results. The problem only occurred after updating these two programs. This is all true. I hope Microsoft will address this quickly.
My only current solution is: Open the console → All console items → File history → Select drive → Select drive D again, specify the same backup drive, and then perform the backup. This works correctly, unlike before when clicking "Execute Now" would create a new backup.
This is the only method I can think of right now; I can't think of any other way.
That's why I don't trust Microsoft Windows Update.
You are seeing File History write files while its last-backup time and Previous Versions catalog no longer advance after the cited updates, on Windows 11 25H2 and Windows 10 22H2. That timing makes a servicing regression plausible, but copied files do not prove the restore catalog is healthy, and Microsoft’s release-health information does not document this issue or a fix. Preserve the D:\FileHistory tree elsewhere before changing anything, and do not delete the Config catalog. Install the newest cumulative update offered, reconnect the configured drive, choose Run now in Control Panel > File History, and test restoring one known file to a different folder. Record the OS build, update history, event-log errors, and restore result. Submit one Feedback Hub report with reproduction steps and diagnostics, then attach that evidence to a Microsoft support case. Until a fix is published, use a separate verified backup rather than trusting the changing timestamps.
