Something must have changed between SR21 and SR22 that causes this …
I still can’t replicate this on our end. I’ve now updated our user data script so that it runs through an two-stage installation…. more or less following the same steps outlined in this guide… and everything works pretty much as expected. I don’t get the .dll error and I’ve created a new non-admin user called RhinoComputeUser.
Hi, I’m getting the RhinoCore.dll error too.
I tried everything I found on the forum but nothing works so far.
Is there a fix?
@brian sent me the list of builds between SR21 and SR22, and I narrowed down using bisecting when it was introduced. I sent the result via PM.
1 Like
Thanks to bisecting and feedback from @brian, we could solve this issue. For some reason, the updated code signing certificates are not installed as expected by the Rhino installer during our provisioning process. The installer runs as an administrator of the Windows Server 2025 instance, so it’s unlikely to be an issue related to permissions. Brian sent the certificates to me (see attachment), and I added a PowerShell script to our provisioning scripts, which installs the certificates.
rhino8_root_certs.zip (5.6 KB)
Install-Rhino-Certificates.zip (879 Bytes)
Many thanks for your great support @AndyPayne @brian !
Note: As mentioned above, our provisioning process installs Rhino as the admin user of the Windows Server, then reboots, logs in a non-admin user, and starts Rhino. If we don’t install the certificates, the pop-up is shown, and Rhino doesn’t start. However, if I log in using RDP as this non-admin user, and start Rhino manually, it works. I noticed something strange when reviewing the installed certificates using the certificate manager: The new certificates didn’t show up until after manually starting Rhino.
It makes no sense to me that the certs don’t show up until starting Rhino, as Rhino doesn’t install them (the installer does).
I wonder if restarting the computer after installing Rhino would also work? It’s so strange.
Yep it makes no sense to me either; the issue is super strange. We are restarting the instance after installing Rhino.