File History Broken After Windows 11 Update KB5124008: How to Fix the InconsistentState Error

Why Did File History Stop Working After the September 2026 Update?

Windows 11's September 2026 Patch Tuesday update, KB5124008, put File History into a broken state Microsoft calls "InconsistentState." Once that happens, File History stops running scheduled backups, and trying to turn it back on from Settings fails silently or throws an error.

Users started reporting the problem on Microsoft Q&A and the Microsoft Community Hub within days of the update landing on September 8, 2026. The same corruption pattern also showed up on machines running KB5126052, KB5126146, KB5122878, and KB890830, so if you have any of those installed alongside KB5124008, you're in the affected group too.

This isn't the first time File History has broken this way in 2026. An earlier round of updates, KB5101684 and KB5120249, caused nearly identical corruption back in the summer. Microsoft never published a root cause for that earlier break, which is part of why this one caught people off guard again.

How Do You Know If Your File History Is Affected?

Open Settings, then System, then Storage, then Advanced storage settings, then Backup options. If File History shows as off even though you remember turning it on, or if clicking to enable it produces an error instead of turning the toggle on, you're affected.

You can confirm the specific error by checking Event Viewer. Go to Applications and Services Logs, then Microsoft, then Windows, then FileHistory-Engine. Look for recent error-level events around the time you installed KB5124008. Users reporting this issue have found entries referencing an inconsistent or corrupted configuration state, which matches what Microsoft's own support threads are calling "InconsistentState."

A second symptom worth checking: open File Explorer and navigate to your backup drive. Look inside the FileHistory folder for your username. If the folder's last modified date stopped updating around September 8, your backups have silently stopped even if the Settings page still shows things as configured.

What Should You Do First If Your Backups Stopped?

Don't panic about data loss yet, but do stop relying on File History until you fix it. Copy anything critical to a second location manually while you work through the steps below. This buys you protection during the gap without waiting on Microsoft's fix.

Next, check whether a newer cumulative update has shipped. Go to Settings, then Windows Update, and check for updates. If Microsoft has released a follow-up patch since September 8, install it before trying anything more invasive. Regressions like this sometimes get quietly patched within a couple of weeks.

If no newer update is available, move on to one of the two fixes below depending on how much risk you're willing to accept.

How Do You Fix File History Without Removing Your Security Update?

Try rebuilding the File History catalog first. This works without giving up the September security patches.

1. Turn off File History in Settings, then System, then Storage, then Advanced storage settings, then Backup options, if it shows any state other than fully off.
2. Open File Explorer and go to your backup drive.
3. Find the hidden FileHistory folder for your username. You'll need to enable "Show hidden files" in File Explorer's View options to see it.
4. Rename the corrupted configuration and catalog subfolder rather than deleting it outright, in case you need to recover data from it later. Something like FileHistory-old works fine as a temporary name.
5. Go back to Backup options and turn File History on again, selecting the same backup drive.

Windows treats this as a fresh backup setup and builds a new catalog from scratch. You lose the ability to browse old versions through the File History interface, but the renamed folder still holds your prior backups if you ever need to dig a file out of it manually.

This fix has worked for some affected users, but not everyone. If File History still won't turn on or immediately reverts to InconsistentState after the rebuild, move to the next option.

How Do You Fix It by Removing KB5124008?

Uninstalling the update is the fix with the highest success rate reported so far, but it comes at a cost: you lose the security patches KB5124008 shipped until Microsoft issues a replacement.

1. Open Settings, then Windows Update, then Update history.
2. Scroll down and select Uninstall updates.
3. Find KB5124008 in the list and click Uninstall next to it.
4. Restart when prompted.
5. After restart, check Backup options again and confirm File History turns on normally.

Treat this as temporary. Reinstall KB5124008, or whatever cumulative update supersedes it, as soon as Microsoft ships a fix for the File History regression. Leaving a security update uninstalled for weeks trades one problem for a bigger one.

What If Neither Fix Works?

Some affected users report that File History stays stuck in InconsistentState even after rebuilding the catalog and uninstalling KB5124008. If that happens to you, the corruption likely reaches beyond the catalog folder into the File History service configuration stored in the registry.

Before touching the registry, back up whatever you can manually. Copy your Documents, Desktop, and Pictures folders to a USB drive or cloud storage. This step matters more than any of the fixes below, because a broken backup tool is still better than no backup at all while you troubleshoot.

Next, try restarting the File History service directly instead of going through Settings. Open the Services app, find "File History Service" in the list, right-click it, and choose Restart. If the service refuses to restart or shows as stopped with no option to start it, that confirms the corruption sits in the service layer rather than just the catalog files.

At that point, a clean File History setup on a different backup drive, even temporarily, sometimes succeeds where reusing the original drive fails. Windows creates a new configuration tied to the new drive, bypassing whatever got corrupted in the old one's registry entries.

If you've tried the catalog rebuild, the update uninstall, and a fresh drive without success, your best move is reporting your findings on the Microsoft Community Hub thread tracking this issue. Microsoft asked affected users for memory dumps to diagnose the root cause, and more data points from people hitting the "nothing works" case help that investigation move faster.

Is There a Backup Option That Won't Break Like This?

Given that this is the second time in 2026 File History has broken from a cumulative update, it's worth treating it as unreliable going forward rather than waiting for a permanent fix.

Windows Backup, the built-in app that handles settings, apps, and credentials, plus OneDrive Folder Backup for your Desktop, Documents, and Pictures folders, don't share File History's code path and haven't shown the same corruption pattern. OneDrive Folder Backup also gives you versioning and off-machine storage, which protects you even if your PC or backup drive fails entirely, something File History never covered.

Microsoft has been steering users toward these tools for a few release cycles now. Given how often File History has broken this year, switching your primary backup method away from it is a reasonable call even after you get it working again.

Key Takeaways

• KB5124008 broke File History for many Windows 11 users starting September 8, 2026, putting it into an "InconsistentState" that silently stops backups.
• Check Event Viewer under FileHistory-Engine and your backup drive's FileHistory folder timestamp to confirm you're affected.
• Renaming the corrupted FileHistory catalog folder and re-enabling backups fixes it for some users without touching the security update.
• Uninstalling KB5124008 has the highest reported success rate but removes September's security patches until you reinstall.
• Consider moving to Windows Backup or OneDrive Folder Backup, since this is the second File History regression from a cumulative update in 2026.