We recently purchased Rhino 7 for one of our clients. When I ran the installer, it requested a restart, but nothing happened after the workstation came back up. I ran it again, and it completed but seems to have deleted Rhino 6. It replaced the icon on the desktop, and in the start menu, only Rhino 6 (Safe mode) remains. I ran the Rhino 6 installer again and it seems that both are now working but I am still left wondering if this is expected, or if there is something I can do to troubleshoot this.
That isn’t possible. The V7 installer doesn’t touch V6.
It’s far more likely that close to the same time you installed V7, V6 updated too.
An installed Rhino can not be “patched” in place, so a Service Release update first deletes the old V6, then installs the new one. Think of it as a sleight of hand like a card trick.
Occasionally, Windows botches the update so the old one is deleted and the new one not.
The fix is to just run the full V6 installer again. Get a fresh one from the Download page.
Also remember that the most recently run installer sets the Windows File Association of 3dm files to the most recently installed Rhino.
This process happened in exactly the same way on 2 different workstations. I could be wrong on what’s happening in the background, but I’m describing what I’m visually seeing happen. It would be a huge coincidence for 2 workstations to decide to update Rhino 6 at the exact same time as I run the Rhino 7 installer. As stated in my original post, reinstalling Rhino 6 afterwards worked out, but if this is not expected behavior then I’d like to know how to fix it. I’ll try redownloading the Rhino 7 installer from the website to see if anything changes. I wasn’t able to do that earlier due to some network issues.
That would be a huge coincidence.
I can’t explain it.
Based on my understanding of now the installers work, this should not be possible.
Maybe @brian has some ideas.
This is definitely not expected. Can you tell me which version of Rhino 6 was installed before you installed Rhino 7? I’m guessing it was a very old one.
I strongly encourage you to install Rhino 6.32 for your clients, too, as it fixes a bug that will delete Rhino 7 license files. I’m contemplating making it impossible for users to install Rhino 7 if Rhino 6.31 or older is installed… but that might be too heavy handed.
By the way @John_Brock, thanks for the quick response!
@brian, I checked in on this and most of them are on 6.31.20315.17001
If it helps, I went through 5 more Rhino 7 installs at this client. Of those, strangely enough 1 of them was able to open Rhino 6 after the install. It was on version 6.13.19058.00371
@brian Please don’t do this - I have a couple of industrial clients who sell Rhino to their customers with a custom plug-in and basically they want their customers to NOT update Rhino past a certain fixed version number so that they know exactly what the client is running. That should not preclude them from installing a Rhino 7 update at a later time or to test. I know this is a ‘special case’, but there might be others in the same situation.