This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 36%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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?
What is frustrating is that users are being left to troubleshoot this themselves. Reset File History, reselect the backup drive, restart services, check settings, and repeat the same troubleshooting steps — but none of that actually answers the most important question:
What caused the problem in the first place?
If File History worked correctly before a Windows update and then started behaving incorrectly after the update, Microsoft should investigate the update itself instead of simply expecting users to keep resetting their configurations.
It is especially concerning when File History is still copying files into the backup folder, while the File History interface and Previous Versions do not correctly reflect what has actually been backed up.
That creates a serious problem for users because a backup system should not give users misleading or incomplete information about their backups.
Microsoft needs to take responsibility for investigating this properly.
Please don't just tell users to:
Reset File History
Remove and re-add the backup drive
Restart services
Recreate the File History configuration
Those may be temporary workarounds, but they do not explain why the problem appeared after the Windows updates.
I would really like Microsoft technical staff to investigate whether KB5101684 and KB5120249 introduced a regression affecting File History, including:
win 10/11 C:\Users\User\AppData\Local\Microsoft\Windows\FileHistory\Configuration、D:\FileHistory\User\D:\FileHistory\User\202108ACERPC\Configuration\Configuration Not destroyed
I am asking Microsoft to actually investigate the Windows update and determine whether it caused the regression.
If Microsoft knows that File History is affected, please acknowledge the issue and provide a clear explanation.
If Microsoft does not believe these updates are responsible, then please explain what is actually causing the problem.
Users should not have to spend hours repeatedly troubleshooting a Windows feature that was working correctly before an update, only to receive no clear answer.
Microsoft, please stop treating this as merely a user's configuration problem and seriously investigate whether your updates caused the regression.
If this is a Windows bug, Microsoft should acknowledge it. If it is not a Windows bug, Microsoft should explain what is causing it.
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 who report the same behavior, the harder it will be to dismiss this as an isolated problem.
Microsoft, we need an actual investigation and a real fix — not another round of “reset File History and see if it works.”
Thanks.
The following are the problems that users and I encountered.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 19%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
Hi @林宗昇
I have contacted Microsoft Support and they have stated that Microsoft isn't aware of any issues within the 2 updates, however they will be continue to investigate and collect feedback before stating the issue is recognized publicly, It has also been stated that feedback posts in the Feedback hub will be reviewed even if you don't see a response, the only thing we can do now is be patient and see if any more people encounters the same issues.
Best regards,
Nanta
Thoura Sopheak Nanta However, after these two updates, my archive history showed an anomaly. Users Darren and David Levine reported encountering the same problem.
Hi @林宗昇
I don't have the same problem as you, but I have directly contacted Microsoft support regarding this issue for both updates on behalf of all affected users.
I also have provided the link to this post to the support team on behalf of all affected users.
Best regards,
Nanta
1.How come the questions are different?
2.I've looked at all the forums and haven't seen any users reporting the issue of abnormal file history logs after updating KB5101684 and KB5120249. Are they encountering the problem but afraid to speak up?
3.I also hope Microsoft will resolve this issue as soon as possible in the September security patch, otherwise it will be very frustrating for us.
Thank you for contacting Microsoft Support and for sharing this post with them on behalf of the affected users. I really appreciate it.
I do have one question, though.
I’ve been checking Microsoft Community and other forums, but so far I haven’t found any other users publicly reporting this specific File History problem after installing KB5101684 or KB5120249.
Do you think there may actually be other users experiencing the same problem but simply not reporting it publicly?
Perhaps they have encountered the issue but are unsure whether it is related to the Windows updates, or they may not realize that other users are experiencing the same thing.
Have you come across any other users who have reported this problem directly to Microsoft Support?
I’m curious because if multiple users are experiencing the same issue, it would be much stronger evidence that this may be a Windows update regression rather than an isolated problem.
Thanks again for helping bring this to Microsoft’s attention.
Hi @林宗昇
I haven't come across on any users with the same or similar problem like you, but it still got my attention, as you mentioned, a few users has reported the same issues, and since when I saw users like you frustrated and you posted 3 times about the same issue and that Microsoft has no response on the post in Feedback hub, I decided to escalate and contact them directly, They have got the info this post and previous posts about File History errors, but there aren't simply enough users reporting or simply not enough users getting problems, probably you have different File History configs.... and more, probably your device behaves a little bit different with the update, our only way now is to stay patient, we wait until if there's other users who had relevant issues too, probably they didn't report it in this Q&A Forum but they probably reported in feedback hub, and hope Microsoft addresses this issue.
Best regards and have a good day,
Nanta
I also hope that Microsoft can resolve the issue of file history being backed up to the D drive but the time not being synchronized as soon as possible in the September security patch, otherwise it will be very frustrating for us.
Hi，
Thank you for the detailed information. Since you have already submitted feedback through Feedback Hub and contacted Microsoft Support, please continue to provide any additional details there, including your Windows version, KB number, File History logs, and reproduction steps.
More user reports with the same behavior will help Microsoft investigate whether this is a regression introduced by the updates. Please keep the existing FileHistory configuration and backup folders intact until the issue is confirmed.
In my post on Community Hub, a user commented that he had the same issue as me.
