Windows 10: "Directory was not backed up because it is a reparse point:" errors using Windows File History

Discus and support "Directory was not backed up because it is a reparse point:" errors using Windows File History in Windows 10 Gaming to solve the problem; I keep getting the "Directory was not backed up because it is a reparse point:" error from Windows File History and it stops backing up. I originally... Discussion in 'Windows 10 Gaming' started by Ira Sch, Nov 25, 2023.

  1. Ira Sch Win User

    "Directory was not backed up because it is a reparse point:" errors using Windows File History


    I keep getting the "Directory was not backed up because it is a reparse point:" error from Windows File History and it stops backing up. I originally set it up about 2 weeks ago and it ran fine for several days. Then I noticed it stopped backing anything up. When I checked the error log, I saw the above error for every folder it tried to back up. Eventually I deleted the files from the Config directory one online suggestion, renamed the file history folder on my backup drive, turned off file history, and started it up from scratch. It worked for about 2 days and now I'm getting the same err

    :)
     
    Ira Sch, Nov 25, 2023
    #1

  2. File History and reparse points.

    It turns out that File History hasn't been keeping a history of my important files. Ever. The error events say that the various folders in my home directory are reparse points. For example, it complains that C:\Users\whn\Documents is a reparse point.
    If I open that file's properties, it says that it is a folder, however there is a tab labeled Location which says "Files in the Documents folder are stored in the target location below." In the location below it says that the files are stored at "C:\Users\whn\Documents".
    That is to say, the reparse point is a folder that is stored where the reparse point is. ??

    This can't be good. And it can't be normal, else File History would not be working for anybody. Any suggestions on how to fix it? I guess I could, for each of Desktop, Documents, etc., move the contents to a temp dir, delete the self-referential
    link, the rename the temp dir back to Desktop, Documents, etc... But that doesn't sound good.

    So, I created a new user account, signed in, and discovered that it has the same pattern as my main account (desktop and documents are reparse points that refer to themselves). Which means it is normal for this version of Windows and that File History shouldn't
    be working for anyone anywhere. How can that be?

    A couple of points: This is Windows 10 Pro version 1803. This machine is four years old and was originally a Windows 8 machine that got the free upgrade to 10.

    I hope you can help, thanks!
     
    WilliamNicholls1, Nov 25, 2023
    #2
  3. File history not working. Directory was not backed up because it is a reparse point:

    I was getting errors like the ones below.

    Event ID: 202 Unusual condition was encountered during scanning user libraries for changes and performing backup of modified files for configuration

    Event ID: 106 Directory was not backed up because it is a reparse point: If you want it to be protected, remove the reparse point.





    As usual no answers here just stupid random time wasting solutions many involving reinstalling your operating system (lol).

    Anyhow what I did was closed down my browsers and other running stuff, disconnected my backup drive and reconnected

    it again, they ran the backup (file history) and it worked fine.

    So......... worth trying that isn't it.

    Merry Xmas.
     
    brensmith9911, Nov 25, 2023
    #3
  4. "Directory was not backed up because it is a reparse point:" errors using Windows File History

    Windows 10 File History backup fails for every directory: "Directory is not backed up because it is a reparse point"

    Appears to be problem reported as "Your data is not yet backed up"

    Windows 10 Home version 1803 current as of 7/11/2018.

    Since application of

    KB4284848 on 7/05/2018

    File History has stopped working. It no longer backs up any directories.

    The Error log message is "Directory id not backed up because it is a reparse point."

    After the failure,

    1) I ran DISM.exe /Online /Cleanup-Image /Restorehealth

    "The operation completed successfully"

    2) Then I ran sfc /scannow

    "Windows Resource Protection Aid did not find any intergrity violations"

    3) Then, again, I ran DISM.exe /Online /Cleanup-Image /Restorehealth

    "The operation completed successfully"

    4) Then I rebooted again

    5) Windows Settings > Update & Security > Backup > more options > File History backup options.

    Starting status is "Your data is not yet backed up"

    Select "Back up now"

    Briefly I get the message "Backing up your data"

    Then the status returns to "Your data is not yet backed up":

    6) Control Panel > System aand Security > File History > Advanced settings >

    Open File History event logs to view recent events or errors recorded in

    Microosoft-Windows-FileHistory-Engine/File History backup log

    Final message is Error Event ID 201

    Unable to scan user libraries for changes and perform backup of modified files for configuration C:\Users\ben\AppData\Local\Microsoft\Windows\FileHistory\Configuration\Conf "

    Preceding messages are all Warning Event ID 106: for example,

    Directory was not backed up because it is a reparse point

    C:\Users\ben\AppData\Local\Microsoft\Windows\/Net Cachje\Low\Content.IE5

    Among the 60 or so failed directories are

    C:|Users\ben\My Documents

    C:\Users\ben\Local Settings

    C:\Users\ben\Cookies

    C:\Users\ben\Application Data



    How would a "reparse point" have been created,

    and how do I delete it?

    Or is the warning message incorrect?
     
    paidilukous, Nov 25, 2023
    #4
Thema:

"Directory was not backed up because it is a reparse point:" errors using Windows File History

Loading...
  1. "Directory was not backed up because it is a reparse point:" errors using Windows File History - Similar Threads - Directory was backed

  2. "Directory was not backed up because it is a reparse point:" errors using Windows File History

    in Windows 10 Software and Apps
    "Directory was not backed up because it is a reparse point:" errors using Windows File History: I keep getting the "Directory was not backed up because it is a reparse point:" error from Windows File History and it stops backing up. I originally set it up about 2 weeks ago and it ran fine for several days. Then I noticed it stopped backing anything up. When I checked...
  3. "Directory was not backed up because it is a reparse point:" errors using Windows File History

    in Windows 10 Installation and Upgrade
    "Directory was not backed up because it is a reparse point:" errors using Windows File History: I keep getting the "Directory was not backed up because it is a reparse point:" error from Windows File History and it stops backing up. I originally set it up about 2 weeks ago and it ran fine for several days. Then I noticed it stopped backing anything up. When I checked...
  4. Error Backing Up with File History

    in Windows 10 Customization
    Error Backing Up with File History: I have just started the first backup yesterday. It worked fine, but now I removed two folders from the backup set and now when I try to back up I get this error....
  5. Back up using File History

    in AntiVirus, Firewalls and System Security
    Back up using File History: Hi thereI have a portable Samsung external hard drive attached to my computer which I use for backup purposes.However File History does not recognise it as a usable drive. When I click on 'add a drive' in Back Up it says 'no usable drives found'. How can I make it recognise...
  6. Back up using File History

    in Windows 10 Installation and Upgrade
    Back up using File History: Hi, I am trying to back up using file history but when I try to add a drive it says "No usable drives found". My WD Elements drive works fine and I can save my work there but when I try to Add a drive for back up using file history it says no usable drives found. Please help....
  7. Backing up using File History

    in Windows 10 Installation and Upgrade
    Backing up using File History: If I back up using File History to an external storage, will it erase the existing data on the external storage? https://answers.microsoft.com/en-us/windows/forum/all/backing-up-using-file-history/4126a239-ea5d-4b3d-84be-7a8dca371d5b
  8. The the file or directory is not a reparse point

    in Windows 10 BSOD Crashes and Debugging
    The the file or directory is not a reparse point: HI When i use to open my Power point,Excel,Word it show the file or directory is not a reparse point please try to help out of me as soon as possible. Your earlier response will be highly appreciated...
  9. File history not working. Directory was not backed up because it is a reparse point:

    in Windows 10 Installation and Upgrade
    File history not working. Directory was not backed up because it is a reparse point:: I was getting errors like the ones below. Event ID: 202 Unusual condition was encountered during scanning user libraries for changes and performing backup of modified files for configuration Event ID: 106 Directory was not backed up because it is a reparse...
  10. How to protect reparse points ignored in File History backups

    in Windows 10 Backup and Restore
    How to protect reparse points ignored in File History backups: Hi It appears that the FH default catalog does not include <username>\AppData - I cannot imagine why, as its contents are obviously needed. My difficulties, mainly in understanding I think, started after adding AppData to the catalog: I received a batch of Event Log...