win 11 25H2 KB5101684 Preview and win 10 22H2 KB5120249 issue

Hi everyone,

I’m wondering if anyone else is experiencing the same File History problems on Windows 10 or Windows 11.

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

After installing the update, I started noticing several strange problems:

• The Last backup time does not update correctly.
• Previous Versions still shows no new versions.
• Files are still being written to D:\FileHistory\..., but File History does not properly update its backup information.
• Folders such as Desktop and Favorites can have their modification dates changed even when I did not actually change their contents.
• 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.

So my situation is:

Windows 11 25H2 → KB5101684 → File History problem
Windows 10 22H2 → KB5120249 → File History problem

At this point, I have to ask: Could these Windows updates have introduced a File History regression?

I have already reported this to Microsoft

This is the part that is really frustrating.

I have already reported the problem through the Feedback Hub, and I also contacted Microsoft Support and chatted online with a support professional.

I was told that the issue would be handled and looked into.

But now several days have passed, and I still have not received any meaningful follow-up or explanation.

So honestly, I have to ask:

What exactly is Microsoft doing with this report?

If Microsoft tells users that the issue will be handled, then users should at least receive some kind of follow-up.

Instead, it feels like the report disappears into a black hole.

I have already spent a lot of time checking File History settings, services, the backup drive, and the actual files being written to the FileHistory folder. I have also provided detailed information about when the problem started and which Windows updates were installed.

At this point, simply telling users to reset File History or reselect the backup drive is not good enough.

Those may be temporary workarounds, but they do not answer the fundamental question:

Why did File History start behaving incorrectly after the Windows update?

If File History worked correctly before the update and then started showing incorrect backup timestamps, missing Previous Versions, and other abnormal behavior afterward, Microsoft should investigate the update itself.

Microsoft needs to take this seriously

A backup system is not something users can afford to treat casually.

If File History is still copying files into the backup folder while the File History interface and Previous Versions do not correctly reflect the actual backup state, users can easily be misled into thinking their backups are working properly when they are not.

That is a serious reliability issue.

Microsoft should investigate whether KB5101684 and KB5120249 introduced a regression affecting File History, including:

• Incorrect backup timestamps
• Missing Previous Versions
• Incorrect modification dates
• File History database/catalog problems
• Unexpected or repeated backup behavior

I am not asking Microsoft to magically fix my computer without investigation.

I am asking Microsoft to actually investigate the Windows update and determine whether it caused the regression.

• I have already used the Feedback Hub.
• I have already contacted Microsoft Support.
• I have already spoken with a support professional online.
• I was told that the issue would be handled.

win 10/11 C:\Users\User\AppData\Local\Microsoft\Windows\FileHistory\Configuration、D:\FileHistory\User\D:\FileHistory\User\202108ACERPC\Configuration\Configuration Not destroyed

But several days later, there is still no meaningful response.

This is extremely frustrating.

Microsoft cannot keep telling users to troubleshoot the same thing over and over again while providing no explanation of what is actually happening.

If this is a Windows bug, Microsoft should acknowledge it. If it is not a Windows bug, Microsoft should explain what is causing it.

What users should NOT get is silence.

If other Windows 10/11 users are experiencing 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.

The more users report the same behavior, the harder it will be to dismiss this as an isolated configuration problem.

Microsoft, please stop leaving users to figure this out on their own. Investigate the problem, explain what is happening, and provide an actual fix.

We need answers, not silence.

The following are the problems that users and I encountered.