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?
60 Replies
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%.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".
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.
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.
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.
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
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?
Using a network share (win11 to win11) totally busted (can't attach share and turn on File History). Worked OK before 9/8/2026 updates.
OK, I'm going to stop beating my head against the MS wall. I believe since I signed out of OneDrive (which I refuse to use), the FileHistory utility will no longer work. At least that's what I suspect might be going on. If you ask AI, you get a whole list of reasons why FileHistory may not work. Like file path too long, file name too long, encrypted files, etc.
I deleted and uninstalled OneDrive. It actually, in my opinion, slows down whatever I am doing, because it takes longer to open and/or save my work. I like my stuff local, on my PC. I deleted everything in it. Then I went into settings (Win + I) and uninstalled it. I think I'm better off, even with all the other Windows 11 problems I seem to have. FWIW.
Whelp, I gave up and downloaded a free backup program. So that's the only advice I can give...... it works well! Microsoft won't let me post the name of it here lol
BUT...... today my wife ran the latest updates on her computer and guess what? File history doesn't work for HER anymore either!!!! It keeps saying "files will be backed up to your computer until you connect your backup drive", even though it says right on the screen it is connected. so i reselected the drive and file history turned it self off, and now the "turn on" button does nothing. Certainly seems the process has been corrupted and won't work anymore.
Honestly wondering if microsoft killed it on purpose because they want to sell cloud storage to people.
I have a cynical point of view. I agree with the sentiment expressed by you (and others) that Microsoft has ignored File History because they want people to backup files through OneDrive.
I gave up relying on filehistory long ago. I, too, have an online backup service -- Carbonite -- which includes Webroot, IMO, an excellent antivirus. I check filehistory once in a while, just to see how it's doing: although it may have some important files saved, I don't think it would be sufficiently comprehensive in an emergency. FWIW.
Yes, I have heard of Carbonite. I use iDrive.
I am one of the victims, and I am furious with Microsoft for corrupting File History. Since the KB5101684/KB5120249 update, files can still be backed up to the D: drive normally. However, the "Last Backup" time in File History is not updating correctly. Newly created or saved Word documents, images, videos, etc., still show "No previous version available" in "Content → Previous Versions". No folders are corrected; their dates are automatically updated. File History was forcibly disabled after KB5124008/KB5120249, resulting in an "InconsistentState" entry in C:\Users\User\AppData\Local\Microsoft\Windows\FileHistory\Configuration.
This is no longer a simple matter of "the time on the screen not updating."
This makes me reasonably suspect that the File History settings, indexing, or internal state management mechanism may be malfunctioning after Windows updates.
If files are indeed backed up, but Windows cannot correctly track, display, and restore versions, then this is a very serious backup reliability issue for users.
Microsoft, please stop being silent. Please answer Windows 10/11 users directly: Did KB5101684, KB5120249, and subsequent updates cause File History regression? If not, please provide technical evidence to explain the true cause.
If so, please acknowledge, investigate, and fix it as soon as possible. What we need is a formal answer and a real fix, not one temporary workaround after another. Please, Microsoft technical teams, take this issue seriously.
100% agree. My File History backup is definitely not working since early September. This is deeply frustrating to the point of questioning whether Microsoft have completely given up on supporting this. I am a long time OneDrive user and value it for many reasons, but I very deliberately run a dual backup strategy that uses File History and local hard drives as well for certain files (darn sight quicker and I have full security control). Seems like I need to spend time and money with 3rd party providers rather than being able to simply rely on the native File History feature any longer. Big shame MS.
Makes me want to switch to Apple. If it was 30 years ago I could make a batch file as a primitive and sloppy substitute but I don't even understand DOS anymore . . .
No more troubleshooters for this sort of thing anymore, eh?
