GreatMarko

Sync can't currently be natively installed & run as a Windows Service, however this thread may be of use.

Agreed. Thread closed

Doozie, these forums are primarily for members of the community to assist each other. If other members of the community are unable to assist with your particular problem, consider opening a support ticket to get dedicated support from the Sync Team instead (although do bear in mind that ticket priority is given in the first instance to Sync Pro users)

Set your device's synchronization mode to "Disconnected" - you'll then be able to choose destination folders rather than syncing to the default folder. For more information, please see: Folder Synchronization Modes

The "y" in "x of y" Peers Online indicator persists based upon the advanced "peer_expiration_days" setting. By default this is set to 7 days (i.e. a device will continue to count towards a "y" total for 7 days of being offline, after which if the device hasn't been seen online, "y" will then be decremented)

Please see: What if several people makes changes to the same file?

Please see: User Management

That's correct - the Camera Backup folder is always a "classic" style folder 1.4. As mentioned previously, you can't "convert" this to a 2.0 style folder.

You will do - the correct URL is actually config.usyncapp.com/sync.conf, however I think that's actually probably largely irrelevant to your issue. Check your firewall/antivirus, and also folder permissions - there's instances of "failed to open" "C:\Users\yoharnu\AppData\Roaming\BitTorrent Sync\..." in your error log

This is actually an old thread which was started before 2.0 was available and when 1.4 was the latest version.

Whilst not a "remove" function as such, the latest 2.0.120 build at least includes the "Ability to hide offline devices in the My Devices list that you are not using anymore"

Sync does not store your data on any "external servers" For help with the "cannot identify destination folder" error, please see this help article.

Look for the sticky "Latest 1.4 Beta Desktop Build 1.4.x" thread near the top of the Sync General Discussion forum, and/or search for the forum for "latest desktop build" to locate older 1.4.x build threads

You'll need to ensure that the system clock on all your devices is correct. Ideally, by syncing all your device's clocks to an Internet Time Server.

As @Helen has indicated above, a missing "template.js" file will not be the cause of this issue. Are you running any extensions (i.e. AdBlock, etc) on Chrome which may be interfering with Sync's WebUI?

Modify your config file and replace: "webui" :{ "listen" : "127.0.0.1:8888"} ...with... "webui" :{ "listen" : "0.0.0.0:8888"}(0.0.0.0 will mean that Sync will listen for WebUI connections from ANY IP address)

Sync already performs "bi-directional" synchronization by default. The only exceptions are when using the Camera Backup feature of the mobiles apps, or "Read Only" shares

Not at present, but please consider adding your voice/vote to this thread in the Feature Request forum.

Sadly, Sync 2.0 isn't compatible with Windows XP - Please see Supported Platforms For XP, you'll have to run the latest 1.4.x build, which may be obtained here ...but you might also want to let the devs know that you'd like XP to be supported for Sync 2.0 by adding your voice to this thread.

Agreed - that's what it looks like to me as well!

In the Folder Synchronization Modes Help Center article

No - but consider adding your voice/vote to this thread instead.

You can change the current device's default folder status (Connected/Synced/Disconnected) at any time - simply go to My Devices, select your device and change it's state

What do the Receiving/Sending columns show? If they're blank but the "Status" line is showing something, it's a likely indication that Sync is simply refreshing its index of the folder post-rename.

Sync should detect a simple file rename within a folder location its monitoring, and rename other instances on your corresponding devices accordingly, rather than seeing it as a "new" file and transferring the entire file again - is this not happening?