Windows 10 User Folder Sync

[mikki]

Hi,

dont know when its started. But my User Folder is throwing Permission Errors in the last time. Its was not the case in the Past. These Folders dont even exist.

does someone have an idea what the problem is ?

[imsodin (Simon)]

I suspect it’s junctions, which we recently started to treat specially. Can anyone with more windowsy knowledge please confirm? @xarx @Catfriend1

[tomasz86]

@mikki

These Folders dont even exist.

They do exist, but may be hidden by default, and have restricted access. If you want to keep synchronising your whole user folder, then the only solution right now is to add each of them to .stignore.

Or you can perhaps just leave them like that and ignore the errors . The other files will still synchronise as before.

[Nummer378 (Max)]

Yes those are junctions Windows creates by default, but they are flagged as system files which means they are pretty hidden to the user.

v1.7.0 Attempting to open folders that do not exist

I am experiencing the same thing since 1.7.0. I’m sharing my Windows userprofile folder, which worked fine for many months. Since 1.7.0 I’m also getting exactly 13 Permission Denied errors on folders that cannot be normally seen in the Windows Explorer. That is, unless you enable “show system files” - then you can see the folders, but accessing them is not possible. I fixed this by adding the problematic folders to the ignores. My best guess is that these are protected directory junctions/link…

[mikki]

@tomasz86

If you want to keep synchronising your whole user folder, then the only solution right now is to add each of them to .stignore .

my ignore file is a nightmare already.

But ok thx Guys. Looking in a future with sunshine, rainbows and syncthing that can handle windows

[tomasz86]

@mikki

my ignore file is a nightmare already.

But ok thx Guys. Looking in a future with sunshine, rainbows and syncthing that can handle windows

Yeah, I personally have 1 non-functional junction and 1 non-Unicode file which are listed under the “Failed Items”, but I just ignore the errors.

[Catfriend1]

Yes, junctions that can be safely ignored as they are pointing to the other accessible and visible directories below the profile root. Funny thing is, one doesn’t have access using Windows Explorer to them. I wonder how the compatibility stuff Microsoft had in mind behind them works if the user application level cannot access the junction target data.