I have the same issue on my Windows Server 2012 R2 machines. Version 4.19 was fine. I am running Syncthing as a service configured by nssm. If I run the executable directly without command line arguments, it launches fine, but I’d really like this to run as a service with the logfile specified.
Answering my questions myself, sorry, for asking the obvious.
Syncthing is such a great tool, the upgrade process just upgrades the executable and does nothing more. (I was sceptic, if the upgrade process would start syncthing and the whole process of syncing…)
14:01:18 INFO: Upgrade available (current “v0.14.20” < latest “v0.14.21”)
14:01:27 INFO: Upgraded to “v0.14.21”
And my Synology Box:
/var/packages/syncthing/target/bin# ./syncthing -upgrade
13:59:09 INFO: Default folder created and/or linked to new config
13:59:09 INFO: Upgrade available (current “v0.14.20” < latest “v0.14.21”)
13:59:16 INFO: Upgraded to “v0.14.21”