File History isn't working anymore!

Piero Tamagni 40 Reputation points
2026-10-30T13:35:20.5733333+00:00

Hello, I thought that after installing 26H2, File History would start working again, but unfortunately, I was wrong. As soon as I enable it, it starts immediately and runs in a continuous loop, with no errors appearing in the Event Viewer. I’ve set only one folder to be backed up, but to no avail. Nothing shows up, and it just keeps stating that the initial file backup is in progress!

They’re pathetic !

Screenshot 2026-10-29 183700

Screenshot 2026-10-29 184046

Windows for home | Windows 11 | Recovery and backup
0 comments

6 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-10-30T13:35:37.69+00:00

    This matches the known File History issue introduced by the September 2026 Windows updates. The documented symptoms include File History being unable to create or update backups, showing incorrect drive-related status such as "Reconnect your drive", not updating Last Backup, and sometimes showing "No previous version available."

    For Windows 11 version 26H2, this issue is resolved by installing Windows updates released on and after September 22, 2026, such as KB5124010. Microsoft recommends installing the latest Windows update because it includes the fix.

    For Windows 11 version 26H2, the practical path is:

    1. Open Settings > Windows Update.
    2. Select Check for updates.
    3. Install the latest available cumulative update for 26H2, specifically an update on or after September 22, 2026 such as KB5124010.
    4. Restart the PC.
    5. Test File History again from Control Panel > System and Security > File History.

    If the device is already on 26H2 but still showing continuous backup behavior, the supported guidance in the available documentation is still to install the latest Windows update for the device, because the fix is delivered through the updated cumulative package.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Piero Tamagni 40 Reputation points
    2026-10-30T13:55:38.38+00:00

    Update KB5124010 is already installed, but unfortunately the error persists.

    Thank you

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. TaoLi 120.6K Reputation points Independent Advisor
    2026-10-30T15:18:44.0166667+00:00

    Thanks for confirming. Try refreshing File History’s settings:

    Turn off File History and close its window.

    Press Win + R, enter %LocalAppData%\Microsoft\Windows, then rename FileHistory to FileHistory.old.

    Restart your PC, select your backup drive again and turn File History on.

    Leave the backups on your backup drive untouched. Let me know whether it still gets stuck.

    Was this answer helpful?

    0 comments
  4. Parker A. Davis 0 Reputation points
    2026-11-09T16:30:39.74+00:00

    I have the same issue and I'm on Windows 11 Pro 26H2, OS build: 26300.9818.

    I downloaded 2 updates for: 2026-09 Cumulative Update Preview for Windows 11, version 26H2 for x64-based Systems (KB5124010) (26300.9550):

    1. windows11.0-kb5124010-x64_95a6272121df38221bfafc90b50baa8ec3e5294e.msu
    2. windows11.0-kb5043080-x64_953449672073f8fb99badb4cc6d5d7849b9c83e8.msu

    Neither update would install saying it was not appropriate for my computer. If those aren't the right updates, I didn't see any others listed that would be (e.g. ARM, x64 24H2 or x64 25H2).

    Please help, I'd like to get this fixed so File History, as imperfect as it was, works again as it used to.

    Was this answer helpful?

  5. Piero Tamagni 40 Reputation points
    2026-11-12T16:54:27.8366667+00:00

    Hello,

    File History has started working again after the update to build 26300.9974, but with one caveat:

    it only works on an external HDD.

    Is there any way to get it to work with an internal, non-system drive as well?

    Thanks.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.