Forum Discussion

sheraton's avatar
sheraton
Brass Contributor
Aug 16, 2026

Win 10/11 file history is malfunctioning after an update why hasn't Microsoft fixed this issue yet?

Hello,

I would like to ask whether other Windows 10/11 users have experienced the same File History problem. I also hope the Microsoft technical team can seriously investigate this issue.

My laptop is running Windows 11 25H2. Before installing KB5101684, File History had always worked normally.

In Control Panel → All Control Panel Items → File History, the backup time would update normally whenever files were backed up to my D: drive.

Around July 28–29, 2026, at approximately 10:00 AM, before KB5101684 was installed, File History was still working normally.

I want to make this very clear: I did not manually change my File History settings, delete Event Viewer entries, or modify or delete relevant registry settings.

The problem started after KB5101684 was installed.

I have already confirmed the following:

  1. File History is still enabled.
  2. The D: drive is working normally and can be accessed without any problems.
  3. After selecting Control Panel → All Control Panel Items → File History → Run now, files are indeed written to:

D:\FileHistory\user\LAPTOP-GJTRIQFJ\Data\C\Users\user

  1. However, the "Last backup" time displayed by File History does not update correctly.
  2. Even after modifying a document, confirming that it was successfully saved, and then clicking Run now, the latest backup time and file versions do not update as expected.
  3. Under File Properties → Previous Versions, it still says:

"There are no previous versions available."

  1. I also noticed that every time a backup runs, folders such as Desktop and Favorites under the FileHistory folder on the D: drive continue to have their modification dates changed, even when their contents have not actually been modified.

What makes this even more concerning is that my Windows 10 22H2 desktop computer also started experiencing File History synchronization problems after installing KB5120249.

In other words:

Windows 11 25H2 → KB5101684 → File History problem

Windows 10 22H2 → KB5120249 → File History problem

This makes me seriously concerned that these problems may be related to a recent Windows Update change or regression affecting File History.

To be honest, I am extremely frustrated with Microsoft.

The problem is not simply that Windows has a bug. Any large operating system can have bugs.

The real problem is that users have reported the issue, provided detailed testing results, identified the Windows versions and specific KB updates involved, provided the actual File History paths, and spent considerable time troubleshooting, yet it is already August and there still does not appear to be a clear official confirmation from Microsoft regarding whether these issues are related to KB5101684 or KB5120249.

Users should not have to repeatedly troubleshoot the same problem without receiving a clear explanation or effective solution.

I would like the Microsoft technical team to seriously investigate the following:

  1. Could KB5101684 be causing File History backup timestamps or version information to behave incorrectly on Windows 11 25H2?
  2. Could KB5120249 be causing similar File History problems on Windows 10 22H2?
  3. Why are files actually being written to the FileHistory directory while the "Last backup" time does not update correctly?
  4. Why does "Previous Versions" continue to report that no previous versions are available?
  5. Why do folders such as Desktop and Favorites have their modification dates changed during backup even when their contents have not been modified?
  6. Could this be a File History regression introduced by a recent Windows Update?

Please do not simply ask users to repeatedly reset File History, reselect the backup drive, or recreate the File History configuration without investigating the underlying cause.

Microsoft needs to determine what is actually happening.

I would also like to ask other Windows 10/11 users who have experienced similar File History problems to leave a comment with the following information:

Windows version

KB update number

Date when the problem started

Whether the backup location is a local drive or network drive

Whether the "Last backup" time is incorrect

Whether "Previous Versions" is unavailable

Whether files are still being written to the FileHistory folder

Please also consider sharing this post or bringing it to the attention of other Windows users and the Microsoft technical team. The more independent cases Microsoft can compare, the easier it should be to determine whether this is a common problem.

I am not asking Microsoft to guarantee that Windows will never have bugs. I am asking Microsoft to properly investigate problems that users have clearly reported, provide an explanation, and deliver an actual fix when appropriate.

This issue has now continued into August, and I am extremely disappointed with the way the File History problem has been handled so far.

Microsoft, please do not ignore this issue. Please investigate it seriously and provide users with a clear response and an actual solution.

Thank you.

5 Replies

  • File History is writing folders, but that does not prove a restorable version was committed or either KB caused a regression. I could not find an official Microsoft release-health notice confirming that link, so avoid uninstalling updates solely on timing. First copy a recent backup elsewhere. Create a uniquely named file in Documents, run File History, modify it, run again, and use Restore personal files to check both revisions; test Previous Versions on the file’s actual folder. Record any File History event-log errors, timestamps, Windows build, KB, and destination type. If data is written but neither interface can restore the test versions, preserve the current configuration and submit a Feedback Hub trace plus a Microsoft support case. Continue a separate verified backup meanwhile. Folder modification times alone are not proof of new file versions, and resetting the catalog now could remove the evidence Microsoft needs.

  • JakeyG's avatar
    JakeyG
    Copper Contributor

    Well, my File History broke on August 8th, 2026 and absolutely NONE of the suggested work arounds I've seen online have succeeded.  Seems using Artificial Intelligence to code for you, ain't so intelligent after all...  Before destroying our home planet, Microsoft, please fix this rather vexing bug.

    Thank you in advance!

    ~J

    • sheraton's avatar
      sheraton
      Brass Contributor

      JakeyG​ 

      https://learn.microsoft.com/en-au/answers/questions/

      You can also ask questions about this file history issue through the Microsoft Forums.

    • sheraton's avatar
      sheraton
      Brass Contributor

      JakeyG​ 

      The current temporary solution is as follows:

      Console → All Console Items → Archive History → Select Drive → Select D Drive again

      After re-specifying the same backup drive, perform the backup again, and the update will proceed normally.

    • sheraton's avatar
      sheraton
      Brass Contributor

      JakeyG​ 

      You too!

      1. My laptop running Windows 11 is experiencing issues after updating KB5101684 on July 28th.

      2. My desktop running Windows 10 is experiencing issues after updating KB5120249 on August 12th.