Just so you know, this has happened many times:
I open the WIP and goes straight to the check for update to get the latest build. And as you can see, it states that there are no new updates and that it HAS checked, but the link show that there is a new one:
And when I close it and open the check for update agan then it shows that it is downloading.
@brian can you help here?
Hi Jorgen,
I understand how this is confusing. And I also understand why it works this
way…
First, the update service only checks for updates when Rhino is started. We
figured there wasn’t any sense checking for and downloading updates on a
machine where Rhino is never run.
So, when you start Rhino, it asks the service “hey, you got an update?”.
If this is the first launch since the update was available, the service
says “Nope” and then starts a background process to check.
A minute or two later, the update service has figured out there is a new
build available and starts downloading it.
The delay you see in the update dialog box is because of the delay in the
update service. I’ll see if I can figure out a way to make it faster.
http://mcneel.myjetbrains.com/youtrack/issue/RH-30009
Brian Gillespie
Rhinoceros Development
Robert McNeel & Associates
Or maybe it doesn’t necessarily need to work this way? Perhaps Rhino could could simply say “Checking for update - please wait” as the first response under the circumstances you described.
Hi Jørgen,
I understand how this is confusing. And I also understand why it works this
way…
First, the update service only checks for updates when Rhino is started. We
figured there wasn’t any sense checking for and downloading updates on a
machine where Rhino is never run.
So, when you start Rhino, it asks the service “hey, you got an update?”.
If this is the first launch since the update was available, the service
says “Nope” and then starts a background process to check.
A minute or two later, the update service has figured out there is a new
build available and starts downloading it.
The delay you see in the update dialog box is because of the delay in the
update service. I’ll see if I can figure out a way to make it faster.
http://mcneel.myjetbrains.com/youtrack/issue/RH-30009
Brian Gillespie
Rhinoceros Development
Robert McNeel & Associates
Logged as RH-38397.
Back from the dead! This is STILL happening in 2026. You might note that this is nearly 9 years later. I don’t mean to rush anybody and this is entirely not a big deal at all. But, it’s kind of silly. If you’re still checking for updates, just say that. Don’t say it’s up to date and then when I click the button to check online it shows that Rhino is a liar. That doesn’t seem to have any rational reason to happen. I get that the update checker needs time. Just say you don’t know if you don’t know and let it keep checking in the background. Having said that, this is such a minor issue of no importance. But, it has been 9 years. Well, 11 since the problem was first brought up. Maybe someone could take a couple of minutes and fix this after 11 years?
I have High hopes, so Have a sigar and give it Time and listen to this while you wait, it might make you Comfortably numb 
I complained about this last week and was told it was on purpose to ease the load on the servers…I’d rather it just worked as it looked like it’s supposed to work, don’t they use a big cloud service to distribute those anyway…?
And if I’m actually looking at that tab odds are not bad that it’s because I’m wondering why it hasn’t updated yet and am about to manually check, no bandwidth will be saved by pretending it’s up-to-date.
It does seem to kind of be on purpose. At least, the asynchronous nature of the update checking is on purpose. However, there is still no practical reason why the app cannot be honest about the state of things. Sure, it is checking updates in the background. I get it. Let it do that. JUST TELL ME THAT. I don’t otherwise care. If the app said ‘I dunno, wait a couple of minutes and I’ll know’ Fine, that’s reality. But, don’t lie to my face. That’s the only irritating thing. Just don’t have your app lie about it. Surely it can’t take that long to have three status outputs in the app
Honestly, not that super difficult. And, sure, there are WAY more important things to work on. But, letting a crappy design decision go for 11 years and pretty much actively fighting against fixing it just seems odd. That’s all, it’s not a big deal bit it is a little annoying and odd that they’re so dead set against fixing a small bug after 11 years.
