Forum Discussion
Why hasn't Microsoft fixed the issue with the July update causing problem with file history logging?
"I've been feeling really upset these past few days. Ever since my laptop installed update KB5101684 on July 29, File History has been malfunctioning. While files successfully back up to the D drive, the backup timestamp does not update. Furthermore, newly created or saved files (like Word documents, images, and videos) still show 'No previous versions available' under Properties → Previous Versions, and folder modification timestamps are unexpectedly altered even when no actual data inside the folders has changed.
Even more concerning, my Windows 10 22H2 desktop started experiencing similar File History sync issues after installing KB5120249 on August 12, 2026. I have already chatted with live support; they said they would investigate my issue, but who knows how long that will take, and they even told me to reinstall the OS. I refuse to reinstall it—especially since I don't even know how to fix it—and I'm worried it will never get fixed.
As a global operating system giant, please immediately have your development team investigate the File History and timestamp logic issues in these updates, and roll out a hotfix as soon as possible instead of just telling consumers to reinstall to dodge the problem. Please face up to your software quality defects and provide a concrete fix!"
If you're experiencing the same issue as me, could you please refer my question to Microsoft? I would greatly appreciate it.
1 Reply
Your backups appear to reach the D drive, but File History’s timestamp and Previous Versions view are not reflecting new files. First open Control Panel > File History and use Restore personal files; this is the authoritative place to confirm whether dated copies actually exist. Verify the affected folders are inside libraries protected by File History and are not listed under Exclude folders. Disconnect and reconnect the backup drive, then choose Select drive and reselect it without deleting existing backups. Check Event Viewer under Applications and Services Logs > Microsoft > Windows > FileHistory-Engine for errors at the last scheduled run. Do not reinstall Windows or delete the FileHistory folder while investigating. Microsoft’s July preview update specifically addressed an SMB File History issue, but it does not document your local-drive symptom. Install the newest cumulative update, retest with one file, and report reproducible logs through Feedback Hub or Microsoft Support.
