How to prevent Rhino 8 from loading plugins registered only for Rhino 7?

[FakerMan]

I have a .NET plugin (IsDotNETPlugIn = 1) that was designed for Rhino 7. It is registered under:

HKEY_LOCAL_MACHINE\SOFTWARE\McNeel\Rhinoceros\7.0\Plug-Ins\{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}

with LoadMode = 2.

There is no corresponding entry under the 8.0\Plug-Ins\ path. However, Rhino 8 still picks it up and loads it on every startup, which causes problems.

I want to keep using this plugin in Rhino 7, but prevent Rhino 8 from loading it.

What I’ve tried

• Created a key under HKLM\...\Rhinoceros\8.0\Plug-Ins\ with the same GUID and set Enabled = 0, LoadMode = 0, and FileName pointing to a non-existent path — none of these prevented Rhino 8 from loading the plugin.

• Disabling in PlugInManager does not persist across restarts.

• Renaming the .rhp file works, but also breaks Rhino 7.

Is there a supported way to block a specific plugin from loading in Rhino 8 while keeping it functional in Rhino 7?

[Tom_P]

related:

@dale

Also, a plug-in’s OnLoad member can check the version of Rhino that is loading and refuse to load if needed by returning a value other than LoadReturnCode.Success.

(Bug / Frozen) Preparing Plug-ins for First Use

Please make “Preparing Plug-ins for First Use” smarter and optional ! from a user perspective: Please: An initial dialog - Do you want to load plugins from old rhino installations. if yes - Allow users to select Plug-ins that should be loaded or not: skip all load all load selected from a developer perspective rhino I think the behaviour of “Preparing Plug-ins for First Use” must be very solid. (currently 31. July 2025) it is not) This means, there should be a time-out mechanism if a plu…

Plug-in freezes the loading window when installed using *.yak file

Hi @dale, @stevebaer, The plug-in has been updated internally to reference Rhino 7 and .Net framework 4.8. When installing it manually using the plug-in manager window, it works fine. However, when trying to install it using *.yak file, it freezes the loading window. Thank you for your help. [image]

[jeremy5 (Jeremy)]

@FakerMan

Disabling in PlugInManager does not persist across restarts

This could be a plugin-specific issue, because I’ve successfully done what you want to do and it persisted. Which plugin are you having trouble with?

PS. You can still see evidence of your plugin in menus and toolbars, but they don’t mean the plugin is loaded - plugin commands found there come back as unrecognised if you try to run them.