Clarification about upgrade 1.30 to 2.0.10

I have 2 identical cloned laptops on Windows 10 that I keep in sync on a regular basis (one is backup).

One of them has been automatically upgraded to 2.0.10 without any prompt to do so and seems to work fine.

The other is still on 1:30 and prompts me to upgrade manually, warning me about incompatibility with old version.

Why the difference between 2 clones? Pls advise if it’s OK to go ahead and upgrade.

Thanx.

How is Syncthing installed on the two systems? Syncthing proper doesn’t automatically upgrade from v1 to v2, but if you’re using some kind of a wrapper (or run synching upgrade), then it may autoupgrade. Otherwise, you do need to press the button manually.

I would recommend reading the “Major changes in 2.0” section at https://github.com/syncthing/syncthing/releases first and then proceed with the upgrade if everything looks fine to you.

Thanks.

There is no wrapper – SyncThing straight. This is very weird because the same version was installed on both at the same time, I never saw an upgrade button before, and yet one is 2.0.10 and one is 1.30. My recollection is that updates are automatic, which is why I never worried about updates until I saw this button.

I tried to read about the changes, but I am not technical enough to figure out how it will impact me – other than pressing the button do I have to do anything else on Windows 10? It seems to me that if 2.0.10 works ok on the one that has it, it should be OK on the other, which is a clone, no? Anything bad can happen if I update?

I am not familiar with ST upgrade–unless it runs by default I have not activated it, in which case I do not think it runs on one and not the other. How do I check if it runs?

It’s difficult to say what happened exactly unless you’ve still got logs from the time the upgrade happened. The upgrade from v1 to v2 isn’t automatic, because there are some incompatibilities between then two, which may cause breakage.

If you’re not very technical, I’d say the main thing to check is whether you’re currently using command line arguments starting with a single -. If that’s the case, you need to change them to a double -- before proceeding with the upgrade (e.g. change -home to --home, etc.).

Considering that the other device is running v2 just fine, I wouldn’t be too worried about the upgrade personally and just press the button :slight_smile:.

I am not using command line.

I upgraded and it seems OK.

I am still puzzled about the auto update, though.

Thanx again for your help.

If you haven’t added any command line arguments yourself, then I think you can just go on with the upgrade and don’t worry about it. The auto-upgrade thing will probably remain a mistery without the logs from that time :confused:.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.