This issue occurred after I and other users installed KB5101684, disrupting File History.

Jamony​ 

Thanks, Jamony, for your professional analysis and practical advice.

As you pointed out, the core danger here is that even though files are physically written to the D:\FileHistory folder, the broken restore catalog and misleading timestamps mean users cannot trust their backups when an actual emergency occurs. For a backup feature, losing trust in the restore function is a critical failure.

Other users are running into this exact same crisis after these recent updates, and they are left in the dark without official tracking or fixes. Since a backup system giving false reassurance poses a severe risk to user data, I strongly urge the Microsoft team to escalate this as a high-priority servicing regression rather than treating it as isolated configuration errors.

We truly need an official investigation and a reliable fix from Microsoft so users don't have to live in fear of silent backup failures.