Rhino 8 crashes while loading the Speckle Connector

Hi everyone,

I’m experiencing an issue where Rhino 8 crashes during startup when it reaches the Speckle Connector loading stage.

Here’s what I’ve already tried:

  • Uninstalled the Speckle Connector through Rhino.

  • Used Revo Uninstaller to completely remove Speckle and any remaining files.

  • Manually deleted any Speckle-related files and folders I could find.

  • Deleted the Rhino registry entry for the Speckle plug-in:

    HKEY_CURRENT_USER\Software\McNeel\Rhinoceros\8.0\Plug-Ins\2153799A-0CEC-40DE-BC3A-01E5055222FF
    
  • Completely uninstalled Rhino 8, then downloaded and installed a fresh copy.

  • Restarted the computer after each major step.

Despite all of this, Rhino still attempts to load the Speckle Connector during startup and crashes at the same point, as if the plug-in is still installed somewhere.

One interesting observation is that Rhino opens and runs normally when launched through Rhino.Inside.Revit. The crash only occurs when starting Rhino 8 directly.

Has anyone encountered a similar issue or knows where Rhino might still be finding the Speckle Connector? Are there any additional registry locations, package folders, or cache files that I should check?

Any help would be greatly appreciated.

image

What Revit version? Note that Rhino 8 can run in the older .netframework or newer .netcore 8 (default)

Opening in an older Revit (2024 & below) uses .netframework.

hey
It works on Revit 2024 and 23. Didn’t test on newer versions

That points to Speckle being a .netframework application, temporarily change your Rhino default .net version to test.

ok so this means that it clashes with .NET Core. And it makes sense, especially since it was a very old version of Speckle. But how can I solve it?
I was trying to uninstall the plugin and then reinstall it correctly afterward. But I did manage to do it.

Here is their latest and greatest. https://releases.speckle.systems/

Hey @Japhy , I installed the newest version, and the issue still exists. i think there are some corrupted files somewhere I cannot replace or find. That’s why I wanted to remove the plugin first. Then install a clean version later