File History timestamp sync bug still broken in KB5124010 - Anyone else?
To the Microsoft technical team Hi everyone,Quick post to see if anyone else is still running into File History timestamp sync issues on the latest builds. Test Environments: Laptop: Windows 11 25H2 (OS Build 26200.8973) Desktop: Windows 10 22H2 (OS Build 19045.7725) Home version The Issue:This problem started back in July (KB5101684 / KB5120249). While KB5124010 fixed the scheduled backup failure and Reconnect drive prompt from KB5124008, the timestamp and version sync bugs remain unfixed: Triggering Run now manually in Control Panel does not update the Last backed up timestamp to the current time. For newly created files (such as Word files), File Properties > Previous Versions displays: No previous versions are available. Changes to the contents of older files will not display the latest timestamp version; only the date and time of the previous version will be shown. A new entity version of the file has been created without any modifications. Other users (including community members in Japan and previous discussion threads) have confirmed identical behavior. File History is essential for daily backups, so getting this sorted out is critical.I'm really on the verge of a breakdown... Hopefully, the security patch will be completed in October. If you are experiencing this issue, please upvote and comment on my Feedback Hub report so the Windows engineering team prioritizes a fix: Feedback Hub Link: https://aka.ms/AA13n22wMicrosoft Store Issues After Updating to 26H2 (Blank pages)
Hi, After updating to 26H2, I see a blank screen in the Microsoft Store: Updates & Downloads (Recent Updates) and Library (All - Apps - Games, etc.) I've tried everything, but nothing helps: wsreset.exe, store: reset, restore, reinstall the Store, sfc /scannow, restore health, etc. The updates in the store work just fine; they download and install. But after that, the information is gone. Everything displays correctly on the main screen. I have an offline account. Before the update, everything worked without any problems, with an offline account Store bug—any workaround? Thank you for your help or for providing a solution. Bas.
Windows 11 File History recopies unchanged files whenever its Control Panel page is opened
I am reporting a repeatable File History problem on a fully updated Windows 11 computer. File History is configured to back up my libraries every hour to a separate physical internal HDD that Windows accepted as the File History destination. To eliminate the possibility of an old or damaged backup configuration, I reformatted the destination drive and configured File History again from the beginning. Steps and observations: The initial File History backup completed successfully and consumed approximately 38 GB. I did not modify the protected source files after the initial backup. I closed and reopened Control Panel > System and Security > File History merely to check the backup status. Immediately after the File History page loaded, it changed to “Saving copies of your files.” The destination drive then consumed approximately another 38 GB, creating new physical versions of files that had not been modified. Pressing Stop ends the active backup cycle. However, after closing and reopening the File History Control Panel page, another backup cycle starts again. This behavior is repeatable whenever the File History page is reopened. A scheduled hourly backup also added approximately 14 GB, despite there being no corresponding amount of intentionally changed source data. I understand that File History is supposed to preserve multiple versions of files that have actually changed. The problem is that it is physically recopying unchanged files and rapidly consuming the entire backup drive. Expected behavior: Opening the File History Control Panel page should only display its current status or scan for changes. Only new or modified files should be copied during the next backup cycle. Actual behavior: Opening the File History page itself triggers a backup cycle that writes another large physical copy of unchanged data. Has anyone else reproduced this behavior on Windows 11? I would also appreciate it if the Windows team could investigate whether opening the legacy File History Control Panel applet is incorrectly forcing a complete or partial re-indexing and recopying of unchanged files. Feedback Hub report: https://aka.ms/AA13n2f3
October 2026 Windows Update causing major issues
We have had about 50 computers in our organization giving boot failures after Windows restarts to apply the October update, KB5127648. Affected machines are Dell devices, both laptops and desktops. The most common error message is "file missing or containing errors \windows\system32\winload.efi" The only fix for now is to try booting into Safe Mode and uninstall the October update. We use a 3rd party tool to patch our devices, Automox, but manually triggering updates from Windows Settings yields similar results. But what I have noticed is that when running Windows Update from Settings, multiple drivers and firmware udpates are also being installed, so I'm wondering if there is incompatibility with outdated stuff in our machines. So we're pushing Dell updates for drivers, firmware, and BIOS, along with Windows Updates hoping that this will take care of the issue. Has anyone else experienced anything similar with this update? Or have any ideas on what may be the root cause in our case? Any feedback will be much appreciated.File History has stopped functioning
My file history program has stopped functioning. I tried searching the internet for some of these error messages and I have not found anything that has a solution that works. I tried deleting the backup on my backup drive, and also deleting the file history data/configuration folders so it would "start fresh" and I still keep getting errors. Here are some of the errors: Also have gotten a bunch of different errors for "reparse points". This is one example. I tried to exclude some of these folders from the backup but it didn't seem to help. But how do I find and eliminate a "reparse point" so it doesn't cause the file history to fail? And why doesn't file history just ignore those folders and go on and back up everything else?Are file history records still in use?Protest and appeals against Microsoft's technical support team
KB5101684 and KB5120249 both state that 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 displayed a false invalid credentials error when connecting to SMB shares. Fixing this issue leads to the following problems. File History Issue Symptoms Affected Systems: Windows 11 25H2 (after installing KB5101684) and Windows 10 22H2 (after installing KB5120249). Key Anomalies: Data successfully backs up to the D: drive, but the Last backup timestamp in the Control Panel fails to update. Newly created or edited files (such as Word documents, images, and videos) display There are no previous versions available under Properties → Previous Versions. Temporary Workaround: Users must manually navigate to Control Panel → File History → Select drive, re-select, and confirm the D: drive to temporarily restore normal functionality. Before updating these two, I never deleted system folders, login files, or messed with settings. Protest and Appeal to the Microsoft Technical Support and Development Teams To the Microsoft Support and Engineering Teams: As long-time, loyal users who heavily rely on built-in Windows backup mechanisms, we are profoundly disappointed and frustrated that recent updates—specifically KB5101684 for Windows 11 and KB5120249 for Windows 10—have broken the File History feature, freezing backup timestamps and rendering Previous Version completely useless. File History is far from being an obsolete or unused feature. For countless professionals, students, and everyday users who prefer or require local data protection as a critical safeguard against file corruption, accidental deletion, and ransomware, this is an essential line of defense. However, after installing official cumulative updates, two entirely independent computers—neither of which had altered system registries or deleted system folders—simultaneously suffered the exact same failure. This proves beyond a doubt that the updates introduced a regression or damaged the underlying sync mechanisms. What is even more infuriating is: A Complete Lack of Official Communication: Users facing these update-induced silent failures are left stranded in community forums without any official acknowledgment or explanation from Microsoft. Ignored Feedback: Detailed reports submitted through the Feedback Hub, complete with cross-computer diagnostic comparisons, have met with radio silence. We hereby formally demand that the Microsoft technical team: Acknowledge and Investigate Immediately: Treat the regression caused by KB5101684 and KB5120249 on File History, VSS (Volume Shadow Copy Service), or directory indexing as a high-priority bug and launch an immediate investigation. Provide a Fix and Clear Transparency: Roll out a definitive patch in the upcoming security or optional updates to resolve the frozen Last backup indicator and broken previous versions, and provide a clear public statement to affected users. If Microsoft continues to neglect this essential feature or turns a blind eye to its decline, we will have no choice but to continuously escalate this issue through all available official support channels, technical forums, and community networks until this critical bug is thoroughly investigated and resolved. Since most people use File History, if you have the same issue as me, don't worry, feel free to leave a comment.The KB5124010 File History backup issue persists Unresolved issue from KB5101684
Current version: Laptop: Windows 11 25H2 OS Build 26200.8973 Desktop: Windows 10 22H2 OS Build 19045.7725 After installing KB5124010, the previous KB5124008 issue was resolved, and the scheduled backup function returned to normal. However, the serious file history synchronization error initially introduced after installing KB5101684/KB5120249 on July 28th still persists. Steps and Observations: After modifying and successfully saving files on drive D, manually triggering a backup via Control Panel > System and Security > File History > Execute Now : Timestamp mismatch: The date and time of the last copy failed to update to the latest save time. For newly created files (such as Word files), File Properties > Previous Versions displays: No previous versions are available. The contents of older files do not show the latest timestamp version; only the date and time of the previous version are displayed. A new entity version of the file without modification was created. Expected Behavior: Initially, the KB5124010 update was intended to address issues with KB5124008 and KB5101684. Actual Behavior: However, unexpectedly, it only fixed the following issue: This update resolves an issue where file history might fail to back up or restore files to an external drive or network location. Affected devices might incorrectly display a "Reconnect Drive" message even if a compatible backup drive is connected and functioning correctly. Feedback Hub report: https://aka.ms/AA13n22w I'm telling the truth; the file history was normal before updating KB5124010 and KB5101684. I don't see export Application log events for FileHistory.exe or KERNELBASE.dll in the Event Viewer. Has anyone else reproduced this behavior on Windows 10/11? I would also greatly appreciate it if the Windows team could investigate and fix this issue. This is a post I made where people commented that they had encountered similar issues, and there were also test results from others. : 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 has not 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.w2eb.com/kb5124010-file-history-initial-backup-incomplete/https://www.w2eb.com/kb5124010-file-history-initial-backup-incomplete/ https://www.nichepcgamer.com/archives/post-132469.html https://gazlog.jp/entry/windows11-file-history-not-fixed-for-some/ https://www.windowslatest.com/2026/09/23/microsoft-confirms-windows-11-quietly-stopped-backing-up-your-files-due-to-a-new-bug-in-september-2026-update/ https://error-daizenn.hatenablog.com/entry/2026/10/01/000906#google_vignette https://aka.ms/AA13n2f3 https://aka.ms/AA13n22w My question is shown in the screenshot below: After modifying and successfully saving files on drive D, manually triggering a backup via Control Panel > System and Security > File History > Execute Now : Timestamp mismatch: The date and time of the last copy failed to update to the latest save time. For newly added files such as Word documents, File Properties > Previous Versions shows: No previous versions are available, or the content of older files does not display the latest timestamp version of updated/newly added files.Why does my laptop ask me to reset fTPM every time I turn it on?
Why does my Acer Nitro AN515-45 show a "Press Y to reset fTPM" prompt every time I boot it up after an automatic Windows update? I'm not very tech-savvy, and I've been pressing N every time, which lets it boot normally, but I don't want to keep doing that forever. I haven't pressed Y because I'm afraid it will lock me out if BitLocker or device encryption is enabled. I tried looking for BitLocker in Settings but couldn't find anything. Is this prompt related to the TPM, the update, or something with Secure Boot? And what's the safe way to make it stop appearing—should I check BitLocker status first, or is there a setting in the BIOS that needs changing? My OS build is 26200.9457.
