Forum Discussion
File History problems after installing KB5124008, KB5126052,KB5126146, KB5122878, and KB890830
This morning, I ran Windows Update on two Windows 10/11 computers, but the file history feature stopped working completely after the update.
Previously, after updating KB5120249 and KB5101684, files could 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, pictures, videos, etc., still show "No previous version available" in "Content → Previous Versions". No folders were corrected; their dates are automatically updated.
After running Windows Update again today, the file history feature stopped working on both computers. The File History panel pops up but cannot be used, prompting for a hard drive connection. (The hard drive is connected and I've confirmed it can read and write.) resulting in an "InconsistentState" entry in C:\Users\User\AppData\Local\Microsoft\Windows\FileHistory\Configuration.
I'm very angry. If Microsoft doesn't address this, I'll keep complaining. If anyone else has encountered the same situation, please leave a comment below. You can also check Microsoft Q&A or the Microsoft Community Hub.
The five updates installed are:
September 8, 2026—KB5122878 (OS Builds 19045.7725 and 19044.7725)
September 8, 2026-KB5126146 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2
2026-09 Security Update (KB5124008) (26200.9445)
2026-09 .NET Framework Security Update (KB5126052)
Windows Malicious Software Removal Tool x64 - v5.145 (KB890830)
Deleting the %LocalAppData%\Microsoft\Windows\FileHistory folder also failed.
Furthermore, "File History" itself is not listed in Microsoft's "Deprecated Features List." While other backup features suggest that Microsoft has no plans to discontinue it.
Microsoft is going to pretend it doesn't exist.
These worked normally before the update but stopped working afterward.
This is to inform other users experiencing the same problem.
32 Replies
If you have the same problem as me (after the recent KB5124010 update, "File History" can find and run the backup drive, but the last copy date of the files has not changed, and any new files can be backed up),Please feel free to leave a comment on my new post:
File History timestamp sync bug still broken in KB5124010 - Anyone else? | Microsoft Community Hub
Jesus Christ - I've received like 13 emails from replies you've made within 30 minutes. What´s going on?
The "InconsistentState" entry you found indicates that the Windows File History service database has become corrupted or unaligned with your external drive due to changes introduced in the recent September 2026 patches (specifically KB5122878 or KB5124008).
Since a basic deletion of the configuration folder failed, the system is likely locking the files or preserving the broken state in the registry. You can resolve this issue by following these steps:
Fully Reset the File History Service
If Windows is actively running the service, you cannot delete or fix the configuration cache. You must stop it manually first:
Press Win + R, type services.msc, and press Enter.
Scroll down to find File History Service.
Right-click it and select Stop.
Now, open File Explorer and navigate to: C:\Users\YourUsername\AppData\Local\Microsoft\Windows\FileHistory\
Delete everything inside the Configuration and Data folders. (If it fails, restart your PC in Safe Mode and delete them).
Clear the Target Drive Hidden Metadata
The "InconsistentState" usually writes a hidden tracking configuration file directly to your backup drive (D:), which prevents Windows from recognizing it as a clean destination.
Open your D: drive in File Explorer.
In the top menu, ensure Hidden items is checked (under the View tab).
Look for a folder named FileHistory on the root of the D: drive.
Rename it to FileHistory.old (this preserves your old backups just in case, while forcing Windows to look at the drive as a brand-new target).
Re-engage the Feature via Control Panel
Do not use the modern Windows Settings app, as it often fails to re-initialize corrupted backup states.
Open the classic Control Panel (press Win + S, type Control Panel).
Go to System and Security → File History.
It should now say that no drive is selected or that File History is turned off.
Click Select drive on the left menu, choose your D: drive, and click OK.
Click Turn on.
Temporary Workaround: Roll Back the Update
If the steps above fail, the September update contains a core code regression affecting the backup engine. You can temporarily roll back the update while waiting for a hotfix from Microsoft:
Go to Settings → Update & Security → Windows Update.
Click View update history → Uninstall updates.
Find KB5122878 (or KB5124008 depending on your Windows version) and click Uninstall.
Pause your updates for 1-2 weeks until Microsoft addresses the bug on Microsoft Q&A or the Microsoft Community Hub.
If you have the same problem as me (after the recent KB5124010 update, "File History" can find and run the backup drive, but the last copy date of the files has not changed, and any new files can be backed up),Please feel free to leave a comment on my new post:
File History timestamp sync bug still broken in KB5124010 - Anyone else? | Microsoft Community Hub
Windows Latest reported on this:
You can ask other people if they have the same situation as me.
Does anyone know when it will be fixed and if we'll know
I have spent several hours investigating this issue. I ended up doing a “repair installation” of Windows (10 in my case), and File History started working. That is until the KB5122878 update was installed, which broke File History again.
I can confirm that uninstalling KB5122878 re-enabled File History on my system.
It’s important to note that even though File History stops working there is no reporting to the logs.
The fix is to uninstall the mentioned update and then pause updates to prevent it from being re-installed on reboot, however Windows is not letting me pause this update for some reason.
Unfortunately, I’ve had several issues with File History over the years, and file backup is far too important a task to leave to chance, so I have begun my search for an alternative backup solution. For those who might be interested, the open source project Kopia seems to be a good candidate.
I had the same issue, so uninstalled KB5122878. The Bad: Backup (System Settings) still showed “Your data is not backed up”. The Good: I could once again view “Previous Versions” in the properties panel. The https://support.microsoft.com/en-us/servicing/os/windows-10/2026/09/kb5122878-windows-10-21h2-22h2-security-update referenced Control Panel > System and Security > File History, which isn't my normal path to backup.
So, I checked Control Panel → File History and it still displayed "File History is On". So, I hit “Run” and crossed fingers it would only take a few minutes seeing it was 1-2 days of backup. Which it did! Backup date adjusted to today 10/1! When I searched "Backup" in System Settings (like normal) it also updated to 10/1/26!!Ran another backup through the Backup in System Settings and it worked again!
If you have the same problem as me (after the recent KB5124010 update, "File History" can find and run the backup drive, but the last copy date of the files has not changed, and any new files can be backed up),Please feel free to leave a comment on my new post:
File History timestamp sync bug still broken in KB5124010 - Anyone else? | Microsoft Community Hub
I'm having the same issues.
Have formatted the entire drive, which has worked before when this has happened. Alas, it is not working.
Have deleted the File History structure on C:\ as well with no success.
Have tried restarting it in services and restructuring the index also.
It is locked in showing this error 100%.Discovered File History had stopped working back just after July's updates.
I rolled back OS to July 01 backup. File History was working again.
Reinstalled KB5126146 and KB5122878. File History stopped working. Unable to reselect network drive!
Came across these Posts so I rolled ahead to yesterday's backup and will wait for fix! Hurry up MS!!!!After the recent KB5124010 update, "File History" can find and run backup drives, and all new files are copied, but the last copy date of the files is not changed. Under "File Properties" -> "Previous Versions," either it displays "No previous versions available," or it cannot list the most recent backup timestamp, and some unmodified archive files are backed up indefinitely. If Microsoft's quality assurance department knows what this means, it's another major oversight. This should be an unresolved issue from KB5101684.
Yes, it's definitely the KB5124008 update. I managed to uninstall it to see if that helped and it did. However, even after setting Pause Updates to on and turning off the get the latest updates option, that update re-installed itself on the next restart.
I did try to uninstall it again but it wasn't available this time.
I have also reported it on the Feedback Hub and said it would be good manners to publicly admit it was caused by that update and to send out a fix as soon as possible.
If you're experiencing the same issue as me—namely, abnormal file history logs after Windows 10/11 updates KB5124008, KB5126052, KB5126146, KB5122878, and KB890830—you can ask a question at the Feedback Center. After asking your question, please let me know.Leave a comment below saying "Question asked".
Same problem, unable to backup to or restore from File History since the September 2026.
Acknowledgement and rectification of the problem required from Microsoft, this is a critical problem.
FileHistory was broken by the 9/8/26 updates on my PC also
Has Microsoft acknowledged the problem?
