Syncthing Windows Setup v1.20.1

Syncthing Windows Setup is a lightweight yet full-featured Windows installer.

Documentation and download: GitHub - Bill-Stewart/SyncthingWindowsSetup: Syncthing Windows Setup

Summary of installer features:

  • Installs the appropriate 32-bit or 64-bit version of Syncthing using a single installer

  • Supports administrative (all users) and non administrative (current user) installation

  • When installing for all users, installs Syncthing as a Windows service using NSSM

  • When installing for the current user, supports creating a scheduled task that starts Syncthing at logon

  • Supports adding a Windows Firewall rule

  • Supports silent (hands-free) installation

Please note the following from the documentation if upgrading from v1.19.1 or older:

Administrative installations in versions 1.19.1 and older configured the Windows service to run using the Windows built-in LocalService account. To improve security, Setup versions newer than 1.19.1 configure the Windows service to run using a local service user account instead (SyncthingServiceAcct by default). As a part of this change, the Syncthing configuration data is now located in the CommonAppData\Syncthing folder (e.g., C:\ProgramData\Syncthing).

When upgrading from version 1.19.1 or older, Setup automatically migrates the Syncthing configuration folder from the legacy LocalService account user profile (e.g., C:\Windows\ServiceProfiles\LocalService\ApplicationData\Local\Syncthing) to the new location. If the migration succeeds, Setup displays a dialog asking whether you want to remove the legacy configuration folder. (In silent installation mode, Setup automatically removes the legacy configuration folder if the migration succeeded.)

After upgrading from version 1.19.1 or older, you must follow the steps in Granting Folder Permissions for the Service Account to grant the local service user account permission to each synchronized folder in your Syncthing configuration. Until you do so, the Syncthing GUI configuration page will report “access denied” errors because the local service user account does not have “Modify” permissions to the folder(s).

1 Like