Forum Discussion
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?
52 Replies
- sheratonIron Contributor
Hello, everyone , on September 23, I contacted Microsoft Support online and reported the issue I was experiencing. After installing update KB5124010, a minor issue appeared in the File History log. Other users have also reported experiencing the same problem.
Today, Microsoft Support emailed me and told me that they are aware of the issue and are currently investigating it.
This is the content of the letter :
- sheratonIron Contributor
Please see my opinion feedback report here: https://aka.ms/AA13mnfk
The KB5124010 File History backup issue persists (Unresolved issue from KB5101684)
- sheratonIron Contributor
After the recent update KB5124010, File History finds the backup drive and runs but the files last copied date doesn't change and yet backup new files. Yet another epic failure of MS QA if they know what that means.
- sheratonIron Contributor
Although updating KB5124010 allows me to restore file history, the console > System and Security > File History > Last copied file date and time are not synchronized every time I save a file.Although updating KB5124010 allows me to restore file history, the console > System and Security > File History > Last copied file date and time are not synchronized every time I save a file.I suspect it is after updating KB5101684. However, the "Console" > "System and Security" > "File History" > "Last copied file date and time" is not synchronized each time a file is saved
- sheratonIron Contributor
Hello everyone
Microsoft has acknowledged that file history (KB5124008) has been disabled and will provide a fix update in the future.
- CJ1Tin Contributor
I'm having the same issues.
Have formatting 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%. - sheratonIron Contributor
Hello
After I updated KB5124008 recently, file history was disabled, and many users reported being affected. Some netizens said they had spoken with others and confirmed that other users had encountered similar issues, but they had not yet confirmed that KB5124008 was the root cause.
https://learn.microsoft.com/zh-tw/windows-insider/release-notes/beta/preview-build-26220-9492
Microsoft released version 26340.9502/26220.9492.
These two URLs contain fixes for the issue where backups using [File History] unexpectedly fail and display the error message "No available disk drive found".
- savamacCopper Contributor
I have seen many reports of problems with File History. It is unacceptable for Microsoft to say "install critical updates" and then ignore the fact that THEIR backup facility no longer works. There is no sign of a remedy. I am looking for alternate (working) backup software.
- jmcd7Copper Contributor
I have recently had a File History problem and getting message "Reconnect your drive - Your files will be temporarily copied to your hard drive until you reconnect your file history drive and run a back-up". I spent 4 hrs with co-pilot carrying out a string of actions to no avail. Then spoke to Microsoft L1 support and the first call cut off and the person did not ring me back. The second person refused to share screen but dismissively said i needed to restore to factory settings as it was probably a corruption. I had already run DISM to RestoreHealth and no problems were encountered. I have since bought a new laptop and apart from the windows updates there is nothing else on it and I get exactly the same message when I try to run File History. I think it is time for Microsoft to come clean and admit the problem and provide a solution.
- savamacCopper Contributor
As far as I can see, File History has been malfunctioning since April. In my case, it has stopped working on two machines (Win 10 and 11) since early September. I have attempted every suggested solution, without success. Microsoft are clearly ignoring the problem, hoping customers will "go away". In many cases this may literally happen, as customers defect to MAC.
- sheratonIron Contributor
I have just installed the most recent update available, newly available today, 2026-09 Security Update (KB5129195) (26200.9457) and the external hard drive back-up inability problem still persists. As this was a second Security Update within a month, (only a week since the last one), I assume there must have been lots of bugs in last week's one.
Many of us want to backup to an external hard drive.
Get a grip Microsoft!
Please give us a fully functioning back-up ability
- JavenCopper Contributor
I’m also experiencing this on Windows 11 25H2, build 26200.9457.
File History reports “Reconnect your drive” despite my Toshiba 2 TB USB drive being connected and readable. After reselecting it, File History shows as off, and clicking “Turn on” does nothing visibly, even after restarting.
Checks so far:
- The drive is NTFS with roughly 1.7 TB free.
- The File History service is running.
- Both local and external backup catalogues were last modified on 4 September.
- The local Configuration folder contains a zero-byte InconsistentState file dated 16 September.
- The latest BackupLog entries are from 9 September, concerning excessive path lengths in Unity cache files. There are no newer errors for the failed activation attempts.
I haven’t confirmed whether a Windows update caused this. Is there a confirmed fix, or a way to collect useful diagnostics without deleting the existing backup?