Forum Discussion
I've tried the methods but they still don't work. I don't know what to do.
This past month has been very frustrating for me. It's not that I like to ramble, but I've genuinely encountered problems after updating. I want to ask Microsoft: after updating my laptop and desktop to KB5101684 and KB5120249, I'm experiencing issues with file history:
- Files can still be backed up to the D drive normally.
- The "Last Backup" time in "File History" is not updating correctly.
- Newly created or saved Word documents, images, videos, etc., still show "No previous version available" in "Content → Previous Versions".
- I haven't modified some folders; please change the modification dates yourself.
Both updates state, "This update fixes an issue that affects File History automatic backups to network shares using Server Message Block (SMB). Backups did not work because Windows showed a false 'invalid credentials' error when connecting to SMB shares." I didn't expect the update to cause this problem; dozens of users have reported the same issue. Microsoft, please investigate and fix this. When will it be fixed?
If you have the same problem as me, please leave a comment below.
According to methods suggested by online users: Open File Explorer, navigate to C:\Users\[Your Username]\AppData\Local\Microsoft\Windows\FileHistory, and delete all contents in the Configuration folder. Next, go to Settings > System > Storage, turn off File History, and then re-add drive D as the backup destination. This method still did not work.
Both updates state, "This update fixes an issue that affects File History automatic backups to network shares using Server Message Block (SMB). Backups did not work because Windows showed a false 'invalid credentials' error when connecting to SMB shares." I didn't expect the update to cause this problem; dozens of users have reported the same issue. Microsoft, please investigate and fix this. When will it be fixed?
If you have the same problem as me, please leave a comment below.
2 Replies
Enabled
The update notes you found address File History access to network shares; they do not promise a repair for local-drive history or create missing versions. Because the target is D: and new files show “No previous versions,” first confirm File History is enabled and D: remains the selected drive. Then use “Restore personal files” to look for an older copy of a file changed before the issue; versions exist only after a successful history run captured them. Check the File History event log for errors when a backup should run, confirm D: is connected with its normal letter, and verify available space. Avoid deleting the configuration until you copy any history elsewhere, because a new configuration can establish a new baseline. If the log shows repeated failures, record the event IDs and Windows build before escalating. The SMB release-note fix is not evidence that it resolves this local-drive symptom.
