Forum Discussion
Windows 11 to KB5101684 File History bug
Hello everyone, I have a question about Windows 11 File History.
After updating my laptop to KB5101684, I modified a file today and confirmed that it was successfully saved.
However, after enabling "File History" and clicking "Execute Now," the backup time still shows yesterday's date (2026/7/28), not today's.
I have confirmed the following:
The backup drive D is properly connected.
File History is enabled.
The File History Service is started and running normally.
The backup location is set to drive D.
The modified files and images were indeed backed up to:
D:\FileHistory\user\LAPTOP-GJTRIQFJ\Data\C\Users\user
However, in the "Restore Profile" section of File History, I don't see the new version date after today's modification.
Additionally, I found that if I go to:
Control Panel → All Console Items → File History → Select Drive → Select D drive again
and then re-specify the same backup drive, then perform the backup, the update works normally; unlike before the update, where simply clicking "Execute Now" would create a new backup version.
Furthermore, before this problem occurred, I did not change any File History settings, nor did I delete any related files or system folders, so I suspect the problem only started appearing after installing KB5101684.
I would like to ask everyone:
Is this a normal phenomenon?
Could it be related to the Windows 11 update KB5101684?
Does this indicate a possible anomaly in the File History database, settings, or related services?
Has anyone else encountered the same situation after updating KB5101684?
Currently, the original files can be opened, modified, and saved normally, and the backup drive is connected normally. I'm just worried that the File History isn't creating a new version correctly, so I want to confirm if further action is needed.
Do you have any suggested troubleshooting methods, such as re-establishing the file history settings, checking related services, or other repair methods?
Thank you for your assistance!
2 Replies
That is not the expected File History result: after Run now, a changed file in a protected folder should have a restorable version, not only a copied file under D:\FileHistory. Reselecting the same drive and then succeeding suggests the configured history set was not refreshed until the drive association was renewed. KB5101684’s notes mention a fix for File History backups to SMB network shares and currently list no known issue matching a local D: drive, so a connection with the update is possible but unconfirmed. Keep the existing backup untouched. Create a small test file in Documents, run File History, and check Restore previous versions. If it fails, reselect D:, run again, and record the OS build, drive type, timestamps, and result. Do not delete File History configuration or catalog files manually. If the behavior repeats consistently, report it through Feedback Hub and Microsoft Support with the reproduction steps.
I don't want to create a small test file in File, run the file history, and select Restore previous version. I'll leave it as is for now and accept this for the time being, reporting this issue to Microsoft support.
Waiting for Microsoft's quick fix in August.
