Windows 10: Local OneDrive folder always returns to "Read-Only" Not a reparse point error 4390

A new problem has developed. I have spent two days fighting it, including all day chatting with Microsoft Support. With no warning, my local OneDrive folder has become labeled "Read-Only." It cannot be defeated, no matter how deeply I go into permissions, etc. It always goes back to "Read-Only." The result is that my GoodSync, which used to work perfectly cannot access the local Outlook folder to complete synch to an external drive, as it used to do until recent days. GoodSync reports "-> target-unknown: DeviceIoControl: The file or directory is not a reparse point. error 4390" The

:)

 

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!

 

Reparse points preventing cloud backups from working

I have two cloud-based backup services (Crashplan, which is withdrawing its consumer services) and Acronis (which I have set up as a replacement). My primary aim is to back up my OneDrive files, since OneDrive is not a backup service, only a syching mechanism.

I have always had the OneDrive "Files on demand" feature turned OFF, to ensure that all my files are physically present on my local drive, thus enabling the backup services to copy them to the cloud. However, both Crashplan and Acronis are exhibiting problems,
and failing to back some of my documents and pictures folders (especially newly-created folders). Through my contacts with Acronis, and testing with the “fsutil reparsepoint query” command, I have established that the problem is caused by the fact that on
my C: drive, the folders C:\Users\[Username]\OneDrive\Documents and C:\Users\[Username]\OneDrive\Pictures are classified as "Reparse Points" rather than normal folders.

Acronis have advised me that their software will not reliably back up a folder which is a Reparse Point, but are unable to help me further.

I don’t know what a Reparse Point is, and I certainly never created them intentionally. The only reason I can think of for the Reparse Points having been created is that a few years ago I used the “Location” tab in File Explorer to redirect my standard
user folders to OneDrive (so for example my “Pictures” folder in Windows moved from c:\users\[username]\Pictures to c:\users\[username]\OneDrive\Pictures). Could that be the explanation?

Anyway my question is, how do I stop a folder within OneDrive being a Reparse point, and revert it back to being a “normal” folder? Are there any dangers in attempting to do so – I obviously cannot afford to lose data, and if any of my OneDrive folders are
deleted or emptied, I fear that the data loss will quickly be replicated to the cloud as well

 

chkdsk reparse point errors - repeatedly


Hello,

Does anyone have experience of repeated 'extended attribute set and a reparse point detected in file xxxxx'errors in chkdsk in windows 10? - even though it apparently corrects the errors with 'deleting extended attribute set due to presence of reparse point in file xxx' - the errors are still there whern I reboot (immediately once Windws has loaded).

I've done the full chkdsk /f /r and repaired the image using DISM and the latest .iso from Techbench. sfc /scannow does not return any error messages.

Thanks.