File History UI and Previous Versions Broken After Installing Recent Windows Updates (KB5101684 / KB5120249)

win 10 22H2 desktop computer os build 19045.7663 BIOS american megatrends inc P11-A4  202108acerPC

win 11 25H2 latop OS Builds 26200.9278 BIOS Inysde Crop A1.22 LAPTOP-GJTRIQFJ Nitro AN515-57

Hello everyone, I am writing to report and check if other Windows 10 and 11 users are experiencing the exact same File History bug following recent updates. I hope the Microsoft engineering team investigates this regression thoroughly.(Note: I had to use my local computer account because my previous account was temporarily suspended.)

Before installing the recent updates, File History on my devices worked flawlessly. The "Last backup" time updated correctly whenever files were successfully backed up to the D: drive. However, after installing KB5101684 on my Windows 11 25H2 laptop on July 29, 2026, and KB5120249 on my Windows 10 22H2 desktop on August 12, 2026, the following issues emerged on both independent machines:

Files are still physically copied and backed up to the D: drive.

The File History control panel UI fails to update the "Last backup" timestamp.

Newly created or saved files (such as Word documents, images, and videos) display "There are no previous versions available" under their Properties.

Folder modification timestamps change unexpectedly even when no actual data inside has been altered.

Problem screenshot:

The File History control panel UI fails to update the "Last backup" timestamp.

Files are still physically copied and backed up to the D: drive.

Newly created or saved files (such as Word documents, images, and videos) display "There are no previous versions available" under their Properties.

I have never deleted system folders, modified the registry, or tweaked advanced settings improperly prior to these updates.

Temporary Workaround: Going to Control Panel → File History → Select drive and re-selecting the D: drive forces File History to resume normal tracking temporarily, but the issue persists on subsequent automated backups.

I have already submitted this through the Feedback Hub with full diagnostic details from two separate computers, but have received no response yet. If Microsoft fails to investigate whether these security/quality updates caused this regression and provide a fix in an upcoming patch, I will continue escalating this through official support channels.

If you are experiencing this exact same File History synchronization and UI bug after these updates, please comment below and share your experience.Don't be afraid, speak up!

If you're experiencing the same issue as me, could you please refer my question to Microsoft? I would greatly appreciate it.