Windows 10: File history not working. Directory was not backed up because it is a reparse point:

Discus and support File history not working. Directory was not backed up because it is a reparse point: in Windows 10 Installation and Upgrade to solve the problem; I was getting errors like the ones below. Event ID: 202 Unusual condition was encountered during scanning user libraries for changes and... Discussion in 'Windows 10 Installation and Upgrade' started by brensmith9911, Dec 21, 2018.

  1. 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, Dec 21, 2018
    #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, Dec 21, 2018
    #2
  3. File History and reparse points.

    The details you posted indicate that the folder "Documents" is a physical folder, not a reparse point, as you appear to have found out by yourself.
     
    Frederik Long, Dec 21, 2018
    #3
  4. File history not working. Directory was not backed up because it is a reparse point:

    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, Dec 21, 2018
    #4
Thema:

File history not working. Directory was not backed up because it is a reparse point:

Loading...
  1. File history not working. Directory was not backed up because it is a reparse point: - Similar Threads - File history working

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

    in Windows 10 Gaming
    "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 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...
  4. "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...
  5. File History back up not working

    in Windows 10 Installation and Upgrade
    File History back up not working: Hi, Firstly, does any one know if Windows 10 Back up File History remains a focus for the Windows team? The UI is kinda clunky to say the least. I have been trying to use Back up but haven't had any success. If I right click on FileHistory on the external drive and choose...
  6. File History Back Up Stopped Working

    in Windows 10 Installation and Upgrade
    File History Back Up Stopped Working: My File History Back up has stopped working. I have disconnected and reconnected my external back up drive and restarted my computer. When I ask it to do a back up NOW it says it's doing it but nothing happens and it then says "Your data is not yet back up". How do I get...
  7. 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...
  8. File History is not backing up my work

    in Windows 10 Backup and Restore
    File History is not backing up my work: I have been using File History to back up my work every 1/2 hour. The backups are being written to a shared folder on a NAS. I check periodically to make sure my files are being backed up and have not noticed any problems until now. I have been doing a lot of work in one...
  9. Windows 10 File History backup fails for every directory: "Directory is not backed up...

    in Windows 10 Installation and Upgrade
    Windows 10 File History backup fails for every directory: "Directory is not backed up...: 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...
  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...

Users found this page by searching for:

  1. Directory was not backed up because it is a reparse point:

    ,
  2. the file or directory is not a reparse point.

    ,
  3. Directory was not backed up because it is a reparse point: C:\Users:assil AppData\Local\ Microsoft Windows\INetCache Content.JES If you want it to be protected remove the reparse point

    ,
  4. directory not backed up reparse point,
  5. file history backup error reparse point,
  6. Directory was not backed up because it is a reparse point:,
  7. your data is not yet backed up windows 10,
  8. reparse point filehistory,
  9. fiel history not backing up directory,
  10. filehistory onedrive Directory was not backed up because it is a reparse point,
  11. file history directort reparse point,
  12. unusual condition was encountered scanning windows 10 filehistory,
  13. Directory was not backed up because it is a reparse point,
  14. windows 10 file history directory not backed up as a reparse point,
  15. The file or directory is not a reparse point backup error