Forum Discussion
There is a problem with File History; a protest is lodged.
Your Microsoft technical team has repeatedly corrupted file history. Since the July 28th/August 13th updates KB5101684/KB5120249, my file history has reappeared. Backups to the D drive are successful, but the backup times cannot be synchronized. Newly created or saved Word documents, images, videos, etc., still show "No previous version available" in "Properties → Previous Versions".
The folder is not being corrected; its date is automatically changed. Until Wednesday's updates KB5124008, KB5126052, KB5126146, KB5122878, and KB890830, the file history was corrupted and disabled, resulting in an "InconsistentState" entry in C:\Users\User\AppData\Local\Microsoft\Windows\FileHistory\Configuration. Why did Microsoft disable it? Everyone is using it, and I'm extremely angry.
Many users have reported encountering this issue on various forums. Microsoft, stop deceiving us!
I demand that Microsoft review this matter immediately and release an emergency update as soon as possible to restore the file history to its original state.
The five updates installed are:KB5122878,KB5126146,KB5124008,KB5126052,KB890830
Anyone else experiencing the same issue as me can report it to the media and have Microsoft confirm the error.
Furthermore, "File History" itself is not listed in Microsoft's "Deprecated Features List." While other backup features suggest that Microsoft has no plans to discontinue it.
Microsoft is going to pretend it doesn't exist.
1 Reply
A successful backup to drive D does not by itself prove that File History has created a recoverable version for every recently changed file. First, test one small document in a standard library folder such as Documents: edit it, save it, wait for or run a File History backup, then open the original folder location and select Properties, Previous Versions. Microsoft notes that previous versions must be checked from the file’s real location, not from the library view. If the test still shows no version, preserve the FileHistory configuration folder and record the FileHistory-Engine operational events before resetting anything. The listed updates are not enough to establish a confirmed regression. Back up important files separately before reconfiguring File History, because restoring an older version can overwrite the current copy. Include the exact file path, File History target, event IDs, and a before-and-after test in any support report.
