Why does my Windows desktop client not offer any update?

[bcutter]

One of my Windows desktop clients thinks it is at latest version running v3.14.3:

Other clients discovered newer releases (like 3.15.2, 3.15.3) and offered to update. Restarting the client of that single machine changed nothing.

Is there something holding back the distribution of newer releases maybe?

[bcutter]

Great discussion. Updated manually, so this question now is for educational purposes only.
Now let's see if the next updates after v3.15.3 will be discovered...

[bcutter]

Still don't get any update offered by the client's integrated update check mechanism. Always have to manually update. Clearly broken.

[bcutter]

%appdata%\Nextcloud\nextcloud.cfg contains this, is this to be expected or an indicator for an issue?

[General]
...
updateSegment=54
...
updateChannel=Stabil
...
[Updater]
autoUpdateFailedVersion=3.0.3
seenVersion=3.0.3

[Nextcloud]
autoUpdateCheck=true

[nilsding]

I'm surprised that the updateChannel value is translated to German... could be the behaviour of an older client

can you try to remove this line?

[bcutter]

I'm surprised - after comparing the nextcloud.cfg with another productive client recently set up - the .cfg of the specific update-avoiding client is so different (contains much more settings/lines).

E. g. the other (fine) client does not have this section at all:

[Updater]
autoUpdateFailedVersion=3.0.3
seenVersion=3.0.3

I removed this section plus the updateChannel=Stabil line now.

As I don't want to downgrade just to test if discovering and offering updates works now, I'll wait for the next stable release. Currently running 3.16.2.

[camilasan]

I will close the discussion now, I do think the wrong update channel was the issue.