There is problem with file history logging after the recent Windows updates (KB5101684 / KB5121003)
Hi everyone, This is not spam, I did not spam the site. It appeared after the update. I hope Microsoft can resolve this issue, and I also hope other users experiencing the same problem can reply to me. Please, please. Ever since the latest Windows updates (specifically around KB5101684 / KB5120249 on Windows 11 Build 26200/Windows 10 Build 19045), The File History feature is almost unusable for me; although it works, the problem only occurs after an update. Symptoms: 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". The Correct folder's date is automatically changed. System details: OS: Windows 11 25H2 (Build 26200.9278) OS: Windows 10 22H2 (Build 19045.7663) Recent Updates Installed: KB5120998, KB5120249, KB5101684. Has anyone else experienced this issue with recent Windows updates? Currently, the only solution is to go to Control Panel → All Console Items → File History → Select Drive → Select D: drive again. After completing this step, File History will return to normal. This is a post I made. Other users who have experienced the same thing left comments below. KB5101684/KB5120249 caused File History errors, but Microsoft has not acknowledged them. | Microsoft Community Hub Welcome to comment if KB5101684 or KB5120249 caused the same File History issue. | Microsoft Community Hub I want to ask Microsoft, why are there abnormal in the file history logs after these two updates? | Microsoft Community Hub Win 10/11 file history is malfunctioning after an update why hasn't Microsoft fixed this issue yet? | Microsoft Community Hub https://learn.microsoft.com/en-nz/answers/questions/5972265/windows-11-file-history-not-updating-correctly-aft https://learn.microsoft.com/en-nz/answers/questions/5978256/win-11-25h2kb5101684-os-builds-26200-8973-and-2610 https://www.reddit.com/r/computerhelp/comments/1vituh0/comment/p6dxvs4/?context=1&screen_view_count=2&ext-referrer=DIRECT https://www.reddit.com/r/WindowsHelp/comments/1w6zlem/comment/p8bbu3j/?context=1&screen_view_count=2&ext-referrer=DIRECTI'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. I want to ask Microsoft, why are there abnormal in the file history logs after these two updates? | Microsoft Community Hub 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.I want to ask Microsoft, why are there abnormal in the file history logs after these two updates?
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.Broken File History after July/August Updates (KB5101684 on Win11 25H2 / KB5120249 on Win10 22H2)
Hi everyone, I am writing to report a major regression bug with File History that was introduced in the recent Windows updates. This is happening across two entirely different machines with no settings changed, no system files modified, and no registry tweaks applied. The Issue: Windows 11 25H2 > after installing KB5101684 (July 29, 2026) Windows 10 22H2 > after installing KB5120249 (August 12, 2026) On both PCs backing up to a local drive (D:), the underlying files are actually being written to the drive, but the File History interface is completely broken: TheLast Backup time stamp in Control Panel frozen and fails to update automatically. In File Explorer, right-clicking new files > Properties> Previous Versions shows There are no previous versions available, making daily time-travel restoration impossible. Temporary Workaround: The only way to force it to sync is to go to Control Panel > File History > Select Drive, and re-select the D: drive again. This proves the backup engine works, but the automatic scheduling and catalog syncing are completely frozen by these updates. Please Help Upvote on Feedback Hub: I have already submitted this issue via the Feedback Hub but have received no official response yet. Since File History is critical for users who prefer local offline backups over OneDrive, we need to bring this to Microsoft’s attention immediately so they can patch it in the next cumulative update. If you are experiencing the same issue, please upvote my feedback link below:[Post your Feedback Hub sharing screenshot]win 11 25H2 KB5101684 Preview and win 10 22H2 KB5120249 issue
Hi everyone, I’m wondering if anyone else is experiencing the same File History problems on Windows 10 or Windows 11. My laptop is running Windows 11 25H2. Before installing KB5101684, File History worked normally. After installing the update, I started noticing several strange problems: The Last backup time does not update correctly. Previous Versions still shows no new versions. Files are still being written to D:\FileHistory\..., but File History does not properly update its backup information. Folders such as Desktop and Favorites can have their modification dates changed even when I did not actually change their contents. I did not manually change File History settings, registry settings, or delete Event Viewer entries. I also experienced a similar problem on my Windows 10 22H2 desktop after installing KB5120249. So my situation is: Windows 11 25H2 → KB5101684 → File History problem Windows 10 22H2 → KB5120249 → File History problem At this point, I have to ask: Could these Windows updates have introduced a File History regression? I have already reported this to Microsoft This is the part that is really frustrating. I have already reported the problem through the Feedback Hub, and I also contacted Microsoft Support and chatted online with a support professional. I was told that the issue would be handled and looked into. But now several days have passed, and I still have not received any meaningful follow-up or explanation. So honestly, I have to ask: What exactly is Microsoft doing with this report? If Microsoft tells users that the issue will be handled, then users should at least receive some kind of follow-up. Instead, it feels like the report disappears into a black hole. I have already spent a lot of time checking File History settings, services, the backup drive, and the actual files being written to the FileHistory folder. I have also provided detailed information about when the problem started and which Windows updates were installed. At this point, simply telling users to reset File History or reselect the backup drive is not good enough. Those may be temporary workarounds, but they do not answer the fundamental question: Why did File History start behaving incorrectly after the Windows update? If File History worked correctly before the update and then started showing incorrect backup timestamps, missing Previous Versions, and other abnormal behavior afterward, Microsoft should investigate the update itself. Microsoft needs to take this seriously A backup system is not something users can afford to treat casually. If File History is still copying files into the backup folder while the File History interface and Previous Versions do not correctly reflect the actual backup state, users can easily be misled into thinking their backups are working properly when they are not. That is a serious reliability issue. Microsoft should investigate whether KB5101684 and KB5120249 introduced a regression affecting File History, including: Incorrect backup timestamps Missing Previous Versions Incorrect modification dates File History database/catalog problems Unexpected or repeated backup behavior I am not asking Microsoft to magically fix my computer without investigation. I am asking Microsoft to actually investigate the Windows update and determine whether it caused the regression. I have already used the Feedback Hub. I have already contacted Microsoft Support. I have already spoken with a support professional online. I was told that the issue would be handled. win 10/11 C:\Users\User\AppData\Local\Microsoft\Windows\FileHistory\Configuration、D:\FileHistory\User\D:\FileHistory\User\202108ACERPC\Configuration\Configuration Not destroyed But several days later, there is still no meaningful response. This is extremely frustrating. Microsoft cannot keep telling users to troubleshoot the same thing over and over again while providing no explanation of what is actually happening. If this is a Windows bug, Microsoft should acknowledge it. If it is not a Windows bug, Microsoft should explain what is causing it. What users should NOT get is silence. If other Windows 10/11 users are experiencing the same issue, please share your Windows version, KB number, when the problem started, and whether files are still being written to the FileHistory folder. The more users report the same behavior, the harder it will be to dismiss this as an isolated configuration problem. Microsoft, please stop leaving users to figure this out on their own. Investigate the problem, explain what is happening, and provide an actual fix. We need answers, not silence. The following are the problems that users and I encountered.
