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

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.