I understand how this is confusing. And I also understand why it works this
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.
Robert McNeel & Associates