Win11 File History Troubleshooting

Question

Win11 File History Troubleshooting

Tony Catanese 10

Win11 file history is no longer executing the scheduled file backups to my network connected external hard drive. The network drive is connected and working. Files can be manually saved to the external drive, but the File History is not backing up to the disk. I could use some troubleshooting tips to find out the problem. The files to be backed up are all in Libraries, which is what File History seems to have set as the default for what is to be backed up. Backup is Turned On and scheduled for Daily.

Diane King 0 Reputation points

2026-09-27T21:12:38.2666667+00:00
Press Win + X and select Event Viewer > Navigate to:

Applications and Services Logs

Microsoft

Windows

FileHistory-Engine

Operational

Did this but there is nothing shown in Operational
Lychee-Ng 28,810 Reputation points Microsoft External Staff Moderator

2026-09-28T06:38:47.5266667+00:00

It's 5 different locations, Diane King, and you might find errors there or not. It'll not show anything if there's just nothing recorded.

3 answers

Your answer

Diane King 0 Reputation points

2026-09-27T21:12:38.2666667+00:00

Press Win + X and select Event Viewer > Navigate to:

Applications and Services Logs

Microsoft

Windows

FileHistory-Engine

Operational

Did this but there is nothing shown in Operational
Lychee-Ng 28,810 Reputation points Microsoft External Staff Moderator

2026-09-28T06:38:47.5266667+00:00

It's 5 different locations, Diane King, and you might find errors there or not. It'll not show anything if there's just nothing recorded.

Answer 1

Lychee-Ng 28,810 Microsoft External Staff Moderator

Hi Tony Catanese,

I understand how worrying it this can be when scheduled backups have silently stopped running, especially when all other configurations seem correctly set up. Since manual file copies to the network drive work, the issue is less likely to be basic network connectivity and more likely related to File History's configuration, service state, or backup catalog. Let's check:

1 - Test whether File History can run manually

Open Control Panel > System and Security > File History > Select Run now
Wait a few minutes and check whether a new backup is created on network drive.
If yes, that points more to a scheduling/service issue rather than a backup problem.

2 - Reset the setup and configurations

Disconnect the network location in File History > turn off File History
Press Win + R > type %LocalAppData%\Microsoft\Windows > Enter
Delete the FileHistory folder (might need admin right)
Restart the PC > leave it off for a (few) days.
Reconfigure File History and select the network drive
Verify that the network share remains available after a reboot.
Test with Run now and check the next day for the scheduled file backups.

3 - Verify the File History Service

Press Win + R and enter services.msc
Locate File History Service and right-click it
Make sure the Startup type is Manual (Trigger Start)
If it's stopped, click Start. If it's already running, click Restart.

4 - Identify why scheduled backups are failing

Press Win + X and select Event Viewer > Navigate to:
- Applications and Services Logs
- Microsoft
- Windows
- FileHistory-Engine
- Operational
Look for recent Errors or Warnings around the time the backup should have run.
Check its content to see whether the problem is permissions, network location, file paths, corrupted catalog...

Let me know the results of the testing above, as those details can help narrow down the sources of the issue. Also, just wondering, is the backup destination a mapped drive letter (for example Z:) or a path (e.g. \\Server\Share)?

If you think the answer is helpful to you, please click "Yes" below. If you have extra questions about this answer, feel free to click "Add Comment" and ask!

Note: Follow the steps in our documentation if you want to enable and receive the related email notifications for this thread.

Tony Catanese 10 Reputation points

2026-08-01T16:19:37.6733333+00:00
Thank you so much for the detailed response. I’ll do my best to respond with relevant screen shots.

I followed your suggestions, sometimes not in the order you presented and I still cannot get a successful backup (BU) from File History (FH). Most of the points you brought up I had probed earlier, but not understanding the technicalities, I was not confident of being on the right path to fixing this problem.

Last Question/Answer: drive mapping is a path (screenshot DRIVE1.png). However, this is a Buffalo Link Station external drive, directly plugged into my internet gateway and blue toothed to a couple of home PC’s which are being backed up (to that point, the BU problem is with both PCs). There is a drive letter mapping (L: ) to a segment of this external drive (screenshot DRIVE2.png) which is used for shared files among the two home PCs. This has been the setup for quite a while and I haven’t changed anything since.

1. FH Run Now – unsuccessful BU. Turned OFF FH and turned back ON – unsuccessful BU.

2. Deleted FileHistory folder, turned OFF FH. Rebooted and reconfigured FH with the network drive. Tested writing directly to the network drive with success. Ran FH and unsuccessful backup. Obviously didn’t wait for a “few days” as you suggested. (screenshot FHSetUp1.png)

The File History service was not “Manual”. It was “Automatic Delayed Start”. (screenshot FHService1.png ). I had tried just the “Automatic” setting before with no resulting change. Following your note, changed the setting to “Manual” and still no success.

Attached is the error message being received now after attempting to run FH (screenshot FHError1.png). I was getting several warnings about “Directory was not backed up because it is a reparse point: “, but it wasn’t until making your changes that I’m getting the error “File was not backed up due to an error: C:\Users\AppData\Local\ElevatedDiagnostics Windows will not attempt to back up the file again, unless it is modified. “

I am not technically savvy enough to understand the reason behind the error message. The detail screen is in the screenshot (FHErrorDetail1.png).

Grateful for any further insight you might have to offer. Any questions, let me know.
Lychee-Ng 28,810 Reputation points Microsoft External Staff Moderator

2026-08-03T09:55:08.6933333+00:00
Hi Tony Catanese, thanks for the detailed follow-up! Since a lot of PII are shown in the screenshots, I've moved them to Private Messages, and if you have any other things to share in the future, please send via there to protect your personal information.

Now, back to the issue. The Event 107 message may simply indicate a file or folder that File History skipped. By itself, that would not normally explain why backups have stopped on two separate PCs. What stands out to me most is that the same behavior is occurring on both computers that use the same LinkStation.

Since both systems are affected, I'm currently leaning more toward a change involving the LinkStation or the network share used by File History than a problem isolated to Windows on a single computer. Right now, a simple test against a USB drive should provide much clearer direction:

Connect a local USB hard drive or large USB flash drive.

Configure File History to use that device instead of the LinkStation.

Run File History manually and compare the result:

If File History still fails on the USB drive, that would suggest a Windows/File History problem on the PC itself.

If File History works on the USB drive, that would point toward a compatibility, authentication, SMB, or File History-to-LinkStation issue.

In addition, if both PCs began failing around the same period without any NAS changes, that could indicate a Windows update or File History change interacting poorly with the LinkStation. A few questions come to mind:

Do you know whether the LinkStation recently received a firmware update?

Can either PC create a completely new folder directly in the same File History target location?

Approximately when did both PCs stop backing up? Did it occur around the same date?
Tony Catanese 10 Reputation points

2026-08-03T21:08:47.58+00:00

Thanks so much for your help!

I connected a USB flash drive, ran FH. It created Configuration and Data files on the USB, but it did NOT backup any files.

The last successful BU on PC 1 (the one I'm on) was around 07/13/2026. The last successful BU on PC 2 seems to be 07/27/2026. Before I started looking at the BU problem, I knew for awhile that LinkStation had an outstanding firmware update, so on 07/29/2026 I did the LS firmware update (about the time PC 2 stopped updating automatically).

I ran FH BU on PC 2 manually just now and it worked. Why hasn't it been auto running since 7/27/2026, not sure.

So I'm guessing my PC 1 and PC 2 issues might not be related.

Yes I can create a completely new folder directly in the same File History target location.
Keith Mander 0 Reputation points

2026-09-21T09:22:05.4133333+00:00

My File history will not TURN OFF. So this method fails at the first hurdle.

Answer 2

SD - IA 179.8K Independent Advisor

Fixed with the Optional update released on 22nd September.

https://yourwindowsguide.com/2026/09/file-history-not-working-after-september-update.html

https://support.microsoft.com/en-us/servicing/os/windows-11/2026/09/kb5124010-windows-11-24h2-25h2-update

[File History] This update addresses 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 your drive” message even when a compatible backup drive is connected and working properly.

0 comments

Answer 3

Lychee-Ng 28,810 Microsoft External Staff Moderator

Thank you for continuing to test this, Tony.

The USB flash drive result is actually very helpful. Since File History behaves the same way when using a USB drive and when using the Buffalo LinkStation, that significantly reduces the likelihood that the network drive itself is the root cause. You're also saying that PC2 is working, so I'll probably focus back on PC1 now.

The fact that File History cannot successfully back up to either the Buffalo device or a USB flash drive suggests that something within the source data being scanned on PC1 may be preventing File History from completing normally. This might be a bit troublesome, but as a diagnostic step, could you try temporarily reducing the scope of what File History is backing up?

Uncheck / Remove the folders from backup source
Temporarily remove other custom folders (if any) from Libraries.
Run File History again and see whether a backup completes successfully.

If a minimal library backs up successfully, we can gradually add folders back until the failure reappears. That may help identify whether a specific folder, reparse point, or file is causing File History to stop.

Tony Catanese 10 Reputation points

2026-08-04T18:22:13.3533333+00:00
I really appreciate your help. Unfortunately, I will be away from this computer configuration for a couple of weeks. I will not be able to follow thru with getting this fixed until mid August.

How would I know which folders are really included in the backup source? When I configured this backup (without any Win 11 idea of how File Explorer's virtual directory works), I created a custom Library and mapped my desired folders to this newly created custom Library. I did this because FH says that it backs up "Libraries, Desktops, Contacts & Favorites". Sure enough it picked up the files I wanted and backed them up.

Per your latest suggestion, I excluded my custom Library and ran FH BU. It seems to be working for 10 minutes or so. No resulting files were backed up. The FH log doesn't show any error or warnings for this date (there is nothing in the log for this date).

Should I start excluding Documents, Pictures, Desktop etc. It would help if I knew which folders were actually being picked up by FH.

Not sure what to try next, but given my PC access constraints can we get back on this mid August?
Lychee-Ng 28,810 Reputation points Microsoft External Staff Moderator

2026-08-05T07:17:31.8766667+00:00
Sure, Tony!! You can reach out whenever suitable, I'll also try to reply in my timeframe. Just to give some ideas on what we can check later, here's something for you to do when you get back (I add a few screenshots for easier following):

Create a new folder on your Desktop named Test and open it.

Right-click inside the folder > New > Text Document > name it Test.txt

In File Explorer, right-click the left panel > select Show Libraries (if it's not already shown)

If you saw Libraries, right-click it > New > Library > name it Test Library

Open the new Test Library > Include a folder > browse to Test folder and add it

Open Control Panel > File History > select Exclude folders.

Exclude everything, leave only Test Library available.

Return to the File History window > Run now.

Wait a while and check the result.

If the Test Library backs up correctly, we'll know the backup engine itself is still working and can then add the folders from the custom Library back one at a time to identify which folder is triggering the issue.
Tony Catanese 10 Reputation points

2026-08-20T16:55:17.86+00:00

I'm back at my PC. On August 5th, before leaving I followed your instructions. Created a new folder and test file. I created a new Library for the newly created folder. Excluded all other Libraries from the FH backup. Manually ran FH backup, no files copied to external drive. No error messages in the FH log.

Returned to the PC on August 18th and did some work. Noticed that the FH BU must have automatically run on Aug 18th with no files backed up nor any error messages in the log.

On August 20th, created a couple of more files in the test folder/library. Manually ran FH BU. No files copied to external drive. No messages in the FH BU Log.

Checking today, PC 2 FH BU is working just fine. Backing up recent files.

What settings can I show you to help me unravel why my PC 1 libraries are not backing up? Any other thoughts?
Lychee-Ng 28,810 Reputation points Microsoft External Staff Moderator

2026-08-21T07:00:08.2933333+00:00
Hi Tony Catanese, welcome back! Thanks for sharing the result, but I must say, this leaves me quite confused as well. Like what puzzles me here is that File History appears to be running and updating its "last copied" timestamp, yet it is neither generating errors nor producing backup copies of even a simple test file. Could you try running BU to USB on a local account?

Open Settings > Accounts > Other users > Select Add account

Choose I don't have this person's sign-in information

Select Add a user without a Microsoft account

Sign into the new account and configure File History.

Disconnect your external drive and connect the USB flash drive

Run Back up now > confirm whether this is profile or system-wide issue.

Also, even though the issue is point to the PC itself now, it'd be helpful to confirm that the external drive is working correctly. Since you mentioned PC 2 successfully backed up, can you connect this drive to that PC and test backing up there? That'd narrow down a lot.
林宗昇 8,360 Reputation points

2026-08-21T10:38:41.8+00:00

Is it related to updating KB5101684 and KB5121767?

My problem is that after the update, the archive history can be backed up, but the time cannot be updated. It can only be resolved by pressing the disk drive again. The service can run.
Tony Catanese 10 Reputation points

2026-08-22T18:18:44.89+00:00

Thanks again Lychee for hanging in here with me on this problem. You are stretching my technological abilities with all of these test, but in a good way. I'm learning new things.

I created a new MS user. Created a new file in 'documents' for that the new user. FH configured to a USB. Ran FH BU and it worked, the new MS user files were backed up on the USB drive.

You lost me on the "Disconnect your external drive". My external drive is Wi-Fi connected to PC 1 and PC 2 As a matter of fact, this brings up another area of my lack of knowledge working with MS Windows. Network mapping and connecting to the external hard drive years ago was a big learning curve for me, however I haven't really retained the knowledge of how I got it done.

Back to the current test......with the new MS user and the successful FH BU to the USB, I thought a good test would be to see if I could BU the new MS user files to the external hard drive. Unfortunately, I am now clueless as to how to map the new user data to the external drive. My attempts failed.

PC 2 is daily continuing to successfully BU to the shared external hard drive (PC 1 & PC 2 were FH BU on the same external hard drive, different folders). I don't understand your last question. "can you connect this drive to that PC and test backing up there?" Are we confusing each other here now?

Next step? What should I look for now?
Lychee-Ng 28,810 Reputation points Microsoft External Staff Moderator

2026-08-24T07:31:35.03+00:00
I was a way so sorry about the late reply, Tony, and I think my wording was a bit confusing. Sorry about that too.

When I mentioned disconnecting the external drive, I was talking about unlinking the Buffalo LinkStation. However, since setting it up again might be a complicated process for you, please do not worry about that. About the drive, I meant try testing the BU on the same location with the PC2. But if they're only on different folders, that's fine.

The good news is that your recent testing gave us another useful clue: the new Microsoft user account on PC 1 successfully backed up files to a USB drive, which didn't happen on your normal account (as you previously tested). That suggests the problem appears to be something specific to your original user profile on PC 1.

I would not spend more time trying to get the new account connected to the network drive yet, since it might be troublesome for you. We now need to find what is different between the working account/PC2 and the original account. Were there any updates or new applications installed around the time issue first appeared?

At this point, we kind of exhausted all troubleshooting too, so if you're interested, you can try to perform a reinstallation repair (keeping files and apps) to attempt to fix Windows problems (if any). Since another profile worked, this might make a difference:

Use built-in repair option

Open Settings > System > Recovery > Fix problems using Windows Update

Click Reinstall now > follow the onscreen instructions to reinstall Windows.

Or you can try an in-place upgrade:

Refer to Reinstall Windows with the installation media - Microsoft Support

Navigate to the bottom of the page and check under In-place Upgrade > follow the instructions.

Download the ISO > Mount it and run setup.exe as Administrator > select Keeping files and apps.

Guidance from one of the Moderators: How to run In-place upgrade in Windows 11 - Microsoft Q&A

Disclaimer: Both Windows reinstallation and in-place upgrade will refresh your Windows files and operating system without removing files or applications. That being said, we always recommend that if you have important data, you should back it up first before making large system changes.

One of the possible solutions for this is to setup the new profile and if the BU works, move there completely. But that also mean reconfigure everything, which might be a hassle for you. So if you want to preserve and repair the original profile, I think this is the time to contact Microsoft Support for deeper profile-level diagnostics:

Visit Contact Us - Microsoft Support > Sign in

Type in your problem > click Get Help to make request

Scroll down and click Contact Support to connect to an agent

Select category and continue > you should be added to a chat queue.

If you don't see chat option, go through another category (e.g. Billings...)

Note: The support contact team only works at certain times, so if the last window shows that it's unavailable, try opening it again the next day. If you prefer phone support, you can leave a phone number. This way, they can call you and help you.

I wish I could come up with more things, but we actually tested almost everything. The Support team might be able to do a remote session or use high-level diagnostic tools to analyze what's going on.