Windows 11 File History Not Updating Correctly After Installing KB5101684

Hello,

Thank you for providing the additional details and repeated test results.

As of August 11, 2026, Microsoft has not officially listed this File History issue as a known problem with KB5101684. The official KB page still states that Microsoft is not currently aware of any issues with this update: https://support.microsoft.com/help/5101684

However, KB5101684 did include a change to File History, specifically a fix for automatic backups to SMB network shares. Since your problem started immediately after this update and the files are copied while the File History timestamp/version index is not refreshed, a regression related to the update is certainly possible, but it cannot yet be confirmed officially.

I would keep the existing D:\FileHistory data intact and avoid deleting its configuration or catalog files. Please install the August security update when it becomes available and test File History again.

I also recommend submitting the reproduction through Feedback Hub using Win + F. Microsoft confirms that a new problem report can still be submitted without signing in, and using “Recreate my problem” will provide diagnostic data directly from the affected PC: https://support.microsoft.com/en-us/windows/apps/send-feedback-to-microsoft-with-the-feedback-hub-app

At this point, we will need to wait for Microsoft to either acknowledge the issue on Windows Release Health or include a correction in a subsequent update.

I very much have both of these problems - the GUI not updating to show any backups since July and it copying files that have not in any way changed. The latter has been severe as I found out when it had gobbled up the remaining 2TB of my backup drive by repeatedly seemingly randomly copying many (not all) files over and over again (it won't stop)!

The August update has made no difference.

There is no easy way to reverse the duplicates and recover the huge amount of disk space. The built in cleanup option will remove all of my old versions going back several years that is NOT in any way an option.

I considered a script to id and remove all the dupes but it would not be able to update the catalog as MS has not shared the schema details and hence it would leave the GUI broken, still referring to all the removed files.

Gemmini AI told me that the August update has made things worse by changing how FH recovers from a missing local catalog - apparently it used to regenerate the catalog from the actual backed up files but that's no longer an option so all it can do is copy the identical backup catalog from the backup drive. If that also unavailable then FH can't recover the backup drive at all (the files are all safely still there but FH can't use them).

Unfortunately, even if the screw ups are reversed, unless Microsoft creates a tool to seek out the duplicates, remove them and update the FH catalog then the duplicates or very broken GUI will remain (very unlikely to happen as FH has been depreciated).

@microsoft, are you listening to this MAJOR screw up you have made?

I have the same problem, but my issue started on July 14th, or at least that's the date of the last successful backup.