Hi all, we are working with WineRider directly for his original issue!

For anyone who doesn't already know, the developers intentionally set the program update notification to lag behind by one or two updates - this is to prevent severe issues if any are found soon after the build is released.

It is common in the software industry to delay updates for parts of the userbase - Microsoft does this with Windows Updates, which is why you can check for Windows Updates on two different machines and get different results. It's a way of staggering the updates, so that if a major issue is discovered, not everyone is affected - for example, the last major Windows update didn't show up on my computer for well over a month. This is a very common practice, and since being one minor build update behind with Band-in-a-Box is not critical, we choose to follow the same practice as Microsoft (and many other companies).

For us, the in-program updates are always only one release behind, though it may look like 2 or 3 versions since we don't release every build update we create.

I work here