This is not due to permissions. I’ve tried to create the path manually, and it fails due to being too long.
mkdir AR424G1V086TJM4E4PO4118448HUHN67KFG7S6E12JS471KD9L29MG8G8QTR4Q050LP3ADBN3FD9BNELR759Q0SEL26KOGU8TQRRE7OUK6BLLH2IAODK81BA9DS4N67RMG8QOFNAAQJKLTCQDUDA2VGJMMTCUM5AIGDRLPNL7FQIEHAM9MHHD9CGCK5FL4EQ9GEDPIFF
The full path of AR424G1V086TJM4E4PO4118448HUHN67KFG7S6E12JS471KD9L29MG8G8QTR4Q050LP3ADBN3FD9BNELR759Q0SEL26KOGU8TQRRE7OUK6BLLH2IAODK81BA9DS4N67RMG8QOFNAAQJKLTCQDUDA2VGJMMTCUM5AIGDRLPNL7FQIEHAM9MHHD9CGCK5FL4EQ9GEDPIFF is too long.
I think it could be the same problem as https://forum.syncthing.net/t/access-is-denied-on-long-file-paths/16097, although there are no UNC paths in my case. Syncthing is supposed to work around the long path limitation, isn’t it though? I wonder what’s failing on my system. For the record, the LongPathsEnabled registry tweak mentioned in the other topic is enabled.
In this state, I’d say this is kind of a deal breaker for me when it comes to Receive Encrypted folders (for now), because in contrary to normal folders, here I’ve got no control over path length, unless I put the folder directly in C:\ or similar.
The overall path in this case isn’t that long either. It’s basically something like C:\Users\User\Desktop\Folder1\Folder2\Folder3 and then Syncthing fails to create 2.syncthing-enc\RI\AR424G1V086TJM4E4PO4118448HUHN67KFG7S6E12JS471KD9L29MG8G8QTR4Q050LP3ADBN3FD9BNELR759Q0SEL26KOGU8TQRRE7OUK6BLLH2IAODK81BA9DS4N67RMG8QOFNAAQJKLTCQDUDA2VGJMMTCUM5AIGDRLPNL7FQIEHAM9MHHD9CGCK5FL4EQ9GEDPIFF inside it.