Did you update to 170303 before via comfortupdate? I saw a post in the forum with 170303 and thought it was a mistype by the poster. I currently being offered the update 2.62.2 (170203) via comfortupdate.
So you could be right, that the build version check routine isn't allowing a downgrade.

Yes, I updated to 170303 via ComfortUpdate from the latest release before 170303. The version number is wrong and most likely the problem here...

Yeah, that would have been me :) I already found it strange that the buildnumber was 170303, but now I can't use ComfortUpdate to check for updates.

Logging into LimeSurvey works fine btw.

Do you guys know of any way to fix this?

Today, 21 February 2017, I was able to update to 2.63.1, but the build number now says 170305? However, clicking on the ComfortUpdate button does not throw out the build_not_found error anymore.

Is there a way to fix the incorrect build number? It's rather annoying.

@celticalliance
You were able to update via Comfortupdate cause the buildnumber is in the future.
Fixing the buildnumber by hand will broke it.
Perhaps LS GmbH will fix it later, when the Comfortupdater can handle update which go "back in time".
Since the version scheme was changed, there is no need for the build-date.
Just focus on the version number.

Alright. Thank you :)