I am having the exact same issue. I just downgraded back to v0.14.49 and the problem goes away.
I wasn’t able to resolve the issue on 0.14.50 even with changing the folder name or re-adding folders. It happened to all three windows machines that I have using SyncThing which were all set to auto-upgrade (which I’ve now disabled.)
Can any of you run Go scripts (i.e. have Go installed or are willing to)? I.e. I provide a small script where you’ll need to enter a folder root path resulting in the failure and it will check a few things to narrow down the source of the problem.
Seeing the exact same error after automatic update to v0.14.50, Windows (32 bit), on two old machines with Windows XP Pro SP3. Haven’t tested extensively, but sync appears to be working both ways in spite of the error message on both PCs.
So what’s the best solution, roll back to v0.14.49 and stay there, or hope that a future release will fix the error? Will v0.14.49 keep working indefinitely (as long as XP )?
Ok thanks, now it’s clear what’s causing the problem, but not why it is happening. Meaning it’s easy to work around, but the problem shouldn’t occur in the first place. Which version of windows are you running?
After running the test on other drives in my system such as C, D, R etc it appears to work on those. But it won’t work on P. For example:
folderRoot: T:\Test
After drive hack, folderRoot: T:\Test
ExpandTilde: T:\Test <nil>
folderRoot is absolute
After longFileNameSupport, longRoot: \\?\T:\Test
After EvalSymlinks, evalRoot: T:\Test
After longFileNameSupport, evalRoot: \\?\T:\Test
rooted("", %v): %v, %v \\?\T:\Test \\?\T:\Test <nil>
The only thing I can think of is that P:\ on my systems is a RAMDISK. So it’s not a real physical disk and is instead created by software. Specifically IMDisk a driver.
All the prior versions of SyncThing worked fine with it though, no problems of any kind syncing folders/files with the RAMDISK. I’ve actually never had software that had an issue seeing or utilising it before, sometimes it even fools disk utilities.
The previous Syncthing version didn’t “work”, it just ignored this error, which didn’t have any consequences for you, as you don’t have symlinks in place.
It looks like the FindFirstFirstFile syscall is not supported with long path names on your driver (paths prefixed by \\?\).