thanks for the info, hoping for the release-software!!! ...same issues here. Verified with Linux/Ubuntu 14.04 and Linux/QNAP, too. I think, this is broken by design since filenames and paths do not have an encoding; the OS only deals with sequence of bytes. Individual applications may choose to interpret them as being encoded in some way... it's not allowed, for my opinion, to assume, filenames could/should/etc be in "UTF-8"-encoding. The only not allowed-byte-Value in Filenames is NUL, isn't it? --- Impossible to use btsync for any data until this is fixed.