Forum Discussion

sheraton's avatar
sheraton
Brass Contributor
Aug 30, 2026

File History Broken After KB5101684 & KB5120249?

Hello everyone,(Note: I previously posted this issue on several community channels and feedback hubs, but only received a few hundred views and a few responses. Because this issue severely impacts daily backups on multiple machines, and there has been no clear official response, I am summarizing and refining the technical details here to help other IT users and track the scope of this issue.) This is not spam.

Others also reported an anomaly in the file history log when updating security patch KB5101650 on July 14th.

I am tracking a file history error that exists on two completely different hardware configurations. Both machines were running perfectly before installing these updates, requiring no manual folder redirection or configuration changes.

 

Affected Environments:

  • Laptop: Windows 11 25H2 → KB5101684 (Installed July 29, 2026)
  • Desktop: Windows 10 22H2 → KB5120249 (Installed August 12, 2026)

Observed Symptoms:

  • Copying physical files to the backup drive (D drive) still works normally.
  • The Last Backup timestamp in File History in Control Panel remains unchanged.
  • Newly created files (Word documents, images, videos) consistently display No previous version available under Properties.
  • The automatic backup correction dates for some unbacked-up files and folders (desktop, favorites) have also changed.

Temporary Workaround: To force a logger restore:

  • Open Control Panel > File History > Select Choose Drive in the left-hand menu.
  • Reselect your existing backup drive and save.

If you encounter the exact same file history failure on Windows 10 or 11, click I'm having this problem too and leave your system version information. Collective data is our best tool for pushing Microsoft engineering to release official patches.

 

3 Replies

  • Amaribo's avatar
    Amaribo
    Copper Contributor

    The File History service fails during its startup process, generating an ESENT database error (-621) that prevents the service from enabling. This leads to the behavior you see: clicking "Turn on" does nothing, and the service remains stopped.