Forum Discussion
Is anyone else's Windows 10 File History failing to update after the August/September updates?
Hi everyone,Since installing the KB5120249 update on August 11th, my Windows 10 (version 22H2) has been experiencing an issue where File History can find and run backups to my target drive (Drive D), but the last copy date and time of files remain unchanged, preventing any new or modified files from being backed up properly.
The specific issues are as follows:
- Version and Timestamp Not Updating: The read and write functions of Drive D are working normally. Even after confirming that a file has been successfully saved, clicking the Run now button in Control Panel does not update the last backup timestamp or version time to the actual latest save time.
- Missing Previous Versions: In a file's Properties -> Previous Versions, modified or newly added files show past versions, but fail to display the latest update date. New versions are omitted as well, continuing to show No previous version available, which fails to reflect the latest changes.
- Strangely enough, the system sometimes backs up files even when they haven't been modified at all. I haven't changed anything on my end, and I haven't been able to successfully back up since the KB5122878 update on September 8th.
I didn't mess with the settings; the problem occurred after the update.
After the recent KB5124010 update in Windows 11, the file history can find and run backup drives, but the last copy date of the files remains unchanged, and any new files can be backed up.
I suspect the problem persists after KB5101684 on July 29th.
Is anyone else still experiencing this issue? On September 23rd, I contacted Microsoft Support to report this File History glitch caused by recent updates (including subsequent impacts from the KB5124010 update). Several other users had also reported the same problem. Two days later, Microsoft Support sent an email confirming that they were aware of the issue and were investigating.
9 Replies
This is STILL a problem, no updates released to date have fixed it.
Three days ago (October 27th), I chatted on Instagram with a contributing editor for the foreign tech media outlet Windows Latest, who lives in Abhijith M B, India. I followed him and described in detail the bug that appeared after updating the Win11/Win10 file history.
That afternoon and evening, he replied to me intermittently, saying the situation was serious and he would help contact Microsoft engineers to investigate. That day, I asked him if he had an Outlook account, and he said yes. I described my problem and others who encountered the same problem to him via email, and he said he received it. I reminded him again to contact Microsoft engineers to investigate, and he readily agreed. Until two days ago (October 28th), he replied late at night with "Okay, received," and then never replied again. I didn't swear or get angry on October 27th. Since then, he hasn't replied to my messages for six days. I messaged him again today.
You can ask him. When you ask him, please mention me.
this is my feedback report:
Please click to view, second, and provide feedback. You can also view the file history. After updating from Windows 11 KB5124010/Windows 10 KB5120249 to Windows 11 KB5127648/Windows 10 KB5126657, the backup drive can be found and executed in "File History," but the last backup date of the files has not changed. If you encounter the same problem as me, you can submit feedback here. You can ask others if they have the same problem and ask them to second and add feedback to my feedback hub.
yes
Six days ago, Marc, a senior executive at Microsoft, sent me an email saying that a dedicated team was investigating the matter. He also advised me not to contact them via instant messaging to inquire about it for the time being.
I'm getting the exact same problem. Timestamp doesn't update so every time it backs up, it backs up literally EVERY file, modified or not, and the backup drive fills up. I've created a script to remove the older copies to prevent running out of space but it's a bodge. We need Microsoft to fix this ASAP.
This is my feedback report:
Please second this. (Adding a response) Could you do me a favor? You could ask others if they have the same problem and ask them to second this. (Adding a response)
Your report describes two different symptoms: a stale “last backup” display and modified files missing from recoverable versions. The second is the more important risk, because an unchanged timestamp alone does not prove that backups stopped. Make an independent copy of current files before testing, and preserve the existing File History drive and catalog. Create one new test document and modify another inside a backed-up library, then run File History manually. Open the restore interface and inspect whether both versions can actually be recovered; restore them to an alternative location so the originals are not overwritten. Record the file modification times, backup run time, Windows build, and installed update details. Since you already have a support investigation, add these reproducible results to that case. I cannot substantiate those updates as an officially confirmed regression or provide a release date for a fix; keep another backup until recovery tests succeed.
I've tried all the methods you mentioned.
Furthermore, on September 23rd, I contacted Microsoft support representative Vensky and chatted with him, reporting a minor issue with the file history log caused by the KB5124010 update. Several other users also reported this problem. On October 6th, Vensky, a Microsoft support representative, sent an email confirming that they were aware of the issue and were currently investigating.
It's caused by KB5120249/KB5124010. I'm not lying; users have already reported this.
