Forum Discussion

Takket's avatar
Takket
Copper Contributor
Apr 11, 2026

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?

 

 

5 Replies

  • Zaidpin's avatar
    Zaidpin
    Copper Contributor

    Based on my research, the issues you're experiencing likely stem from the drive not being properly detected by Windows services or corruption in the system components that File History relies on.

    • Takket's avatar
      Takket
      Copper Contributor

      Windows is having no trouble finding and using the drive. I created a full system image on the drive and windows had zero errors when it did so. So I'd love to fix whatever system components are corrupt but where do I find them? DISM and SFC are both coming back clean

  • Takket's avatar
    Takket
    Copper Contributor

    Ran DISM and SFC. DISM ran for quite a while and repaired some things, but it didn't tell me what. File History still doesn't work. Same problem. Though the error message has changed:

     

    Unusual condition was encountered during finalization of a backup cycle for configuration C:\Users\jctak\AppData\Local\Microsoft\Windows\FileHistory\Configuration\Config

     

    I was able to run a full system image which ran without any errors at all. 

     

    Update: Ran chkdsk which corrected many "reparse" points (which is an error i had seen a few times on File History). After doing that i deleted the config/data files to start file history fresh and ran it again. it ran for over 30 minutes so i was thinking it was actually copying files but then... nope. it ended, threw the same error, and a check of the backup drive showed no files had been copied. so... i don't know what it thought it was doing for 30 minutes? but it did nothing.

  • Aaravov's avatar
    Aaravov
    Iron Contributor

    Since you've already tried resetting File History manually, the most likely cause is corrupted Windows system files. The built-in SFC and DISM tools can find and repair these hidden issues.

  • cjthelder's avatar
    cjthelder
    Copper Contributor

    I have a similar problem.  But in addition, although File History appears to be ready to run, it in fact does not.  I click on "run now," and it starts to run, but stops right away.  It is set up for the default of every hour (which I'll change if I ever get it to run), The data folder is empty and the "date modified" has not changed since it was set up. Nor does it appear in the task manager.  Sure would like to get this working.  Thanks.