File History timestamp sync bug still broken in KB5124010 - Anyone else?

Six days ago, Microsoft executive Marc sent me an email saying that the matter was under review by a dedicated team. He also advised me to temporarily avoid contacting them via instant messaging to inquire about the issue. The investigation is ongoing, and additional instant messaging contact will not expedite the review process.

I'm getting the same problem since the recent updates.  My backup, and my wife's backup on her laptop, both work OK, but her backup on our Desktop, as you can see in the screenshot below, is stuck with a timestamp of 15/10/2026 6:46 AM.  So every time it backs up, it adds ALL her files, regardless of whether they have been modified, causing the backup drive to run out of space.  For now, I am running a script which deletes the oldest copies of everything, and that is helping, but it's a bodge at best.  We really need Microsoft to fix the bug they just introduced.

The safest temporary approach is to separate "the files were copied" from "the File History UI reports the correct state." After Run now, browse the backup drive and locate the newly created test file under the FileHistory data folder. If the file and its modified version are present there while Last backup and Previous Versions remain stale, you have strong evidence that backup storage and shell metadata are failing differently.

Export the Microsoft-Windows-FileHistory-Engine event log after each test and keep the exact Windows build, backup-drive file system, and test filename with the report. Avoid deleting the FileHistory configuration folder or formatting the backup disk; several users have already shown that rebuilding does not cure this regression and it removes useful evidence.

Until Microsoft ships and documents a fix, make a second ordinary copy of current work folders to another location and verify it manually. That does not replace version history, but it prevents the unresolved timestamp defect from becoming the only protection for new files.

I am have the same problems as you and everyone else. I am I the UK. After the last patch update they have it almost working again. It backup all the files but the problem is it fills up all the SSD drive and it's a 2TB drive. The other problem is when I try to restore files or folder there is a blank screen and a message say cannot restore until the file history as finished. I have tried everything to fix it from formatting the drive and going into my user AppData and removing the file history folder and stating from scratch. Nothing works and Microsoft have know about the bugs and errors and are doing nothing about it. When you ask for help from them you are given answers like robots telling you to check links that a useless. I am not a business or I.T. person. My computer is for personal use. I have read other forums and can see a lot of business and I.T. people are not happy with Microsoft. I have my own windows 2019 server. I am aware some business use some other file back and restore software to backs up to a large file storage system. I was shown the server room because they knew I was into server and computers. It was interesting to see over a £100.000 worth of equipment. Microsoft was taken over a few years ago and the company are more interested in profit than their customers. They are to busy trying to compete with apple and Linux rather than concentrate on their own operating system and make it run the way it should. At the moment I have to back folder and files the old manual way until they fix file history. They did the same thing with PHP Manager withdrew support and updates for it and now it show PHP version are obsolete. They also withdrew all support for all office software bought on DVD ROM disc. They are trying to force people into using their 365 thing that requires subscriptions and costs a fortune to use. It must be a nightmare for businesses and I.T. people. Microsoft need to get a grip and start listening to us because if a better operating system comes along just like Windows and is fully supported fixed very fast we all know what will happen