Windows 11 File History issue after installing KB5101684 – backup timestamp not updating unless I reselect the backup drive
Hi everyone,
I'm having a strange File History issue after installing Windows 11 KB5101684 on July 29, 2026, and I'm wondering if anyone else has experienced the same problem.
Whenever I save or modify a file, I go to:
Control Panel → All Control Panel Items → File History → Run now
However, the "Last copied" date and time do not update.
As shown below :

The only way I can get the timestamp to update is by going to:
Control Panel → All Control Panel Items → File History → Select drive
and then selecting my D: drive again. After doing that, File History runs normally.
What's confusing is that the files are actually being copied to my backup drive even before I reselect it.
I've already confirmed the following:
- My D: backup drive is connected and working normally.
File History is turned on.
The File History Service is running normally.
The backup location is correctly set to D:.
Modified files are being copied to: D:\FileHistory\user\--PII REMOVED--\Data\C\Users\user
As shown below

As shown below :

Disk management systems all have a D drive and are connected to...
However, I also noticed another problem.
When I right-click a Word document or picture and check Previous Versions, today's modified version does not appear.
In addition, if I download a brand-new image, Previous Versions simply says "There are no previous versions available."
As shown below :
If you download new images or add new Word documents, Previous Versions simply says, "There are no previous versions available."
I'd like to ask:
Is this normal behavior?
Could this be related to Windows 11 KB5101684?
Is it possible that KB5101684 caused a problem with the File History database, configuration, or related services?
Has anyone else installed KB5101684 and experienced the same issue?
I've been troubleshooting this for several days, and honestly I'm quite frustrated.
I also hope Microsoft will take this issue seriously and include a fix in the August 2026 security update, if this turns out to be a bug introduced by KB5101684.
Any suggestions or shared experiences would be greatly appreciated.
I contacted Microsoft support and asked a professional who said they would look into it again.
Thank you!