Task Schedule won't start SyncThing after Upgrade to 2.0.5

[NateC]

After much searching & struggling, found my own solution. Posting it to help others.

Running Windows 11

Syncthing had been starting automatically from Windows Task Scheduler. A beautiful, trouble-free setup.

After upgrading Syncthing to 2.0.5 (from a 1.3.4), it wouldn’t start.

Sometimes the Web GUI would demand authentication, but that ended up being irrelevant, not the issue.

Syncthing would start from the command prompt, but then stop when I closed the command prompt.

So when I ran “syncthing.exe -no-console -no-browser”, the problem was replicated.

But when I changed it to “syncthing.exe --no-console --no-browser”, PROBLEM SOLVED.

I made the change in my Windows Task Scheduler, and operations were back to normal.

Hope this helps someone.

[tomasz86 (Tomasz Wilczyński)]

@NateC

After upgrading Syncthing to 2.0.5 (from a 1.3.4), it wouldn’t start.

Was it really v1.3.4? I’m asking, because that would be mean an upgrade from a very old version .

As for the -- double dash requirement, this is explained under “Major changes in 2.0” (e.g. see https://github.com/syncthing/syncthing/releases/tag/v2.0.5).

[NateC]

Yes, I haven’t upgraded in a while. It’s been working flawlessly this whole time. Such a beautiful piece of software.

[tomasz86 (Tomasz Wilczyński)]

Good to hear that, and also good to know that a direct upgrade from such an old version to Syncthing v2 is possible .