Registering Plugins (Windows)
Windows only


While a Rhino plugin can simply be distributed as a .rhp file, and loaded using Rhino’s PlugInManager command, it is often necessary to install the plugin as part of a product installation process. To install plugin from an installer, your installer will be required to access a number of entries in the Windows Registry.

While reading this article, it is helpful to use the standard Windows Registry editing tool, REGEDIT.EXE, to follow along and see how Rhino’s Registry entries are structured.

Finding the Rhino Registry Key

Rhino plugins are registered at the following location in the Windows Registry:


Where MajorVersion is the major version of Rhino (e.g. 6, 7, 8).

Registering Your Plugin

To register your plugin with Rhino, you will need to create a new Registry key at the above location. The name of the Registry key will be your plugin’s GUID, formatted as a string. For example:


Under this new Registry key, create two new value names, Name and FileName that contain strings that identify your plugin’s name and the full path to the .rhp file, respectively. For example, if you had created a new plugin named “MySamplePlugIn”, the registry might look something like the following:


Value:  Name
Type:   REG_SZ
Data:   MySamplePlugIn

Value:  FileName
Type:   REG_SZ
Data:   C:\Program Files\My Company\My Sample PlugIn\MySamplePlugIn.rhp

Automatic Loading

Rhino will attempt to load your plugin the next time Rhino launches if the Name and FileName Registry values and data are present in your plugin’s Registry key. Rhino will briefly display a “Preparing plugins for first use” dialog if the plugin loads correctly.

When your plugin loads for the first time, the rest of the normal Registry keys/value pairs in your plugin’s Registry key will be filled in.

Other Useful Values

There are other useful key values that are found in the following locations depending on the Rhino version:



  • InstallPath contains the full path to the Rhino installation folder.
  • Path contains the full path to the System folder under the Rhino folder.


Look in the Registry with REGEDIT.EXE and confirm that existing plugins follow these conventions.

Use the right-click context menu in REGEDIT.EXE to access the “Copy Key Name” and “Rename” functions so you can get accurate copies of names and values in the Registry.

Test your installer to handle all of these situations:

  1. No Rhino is installed on the computer.
  2. Only the Rhino Evaluation or Beta editions are installed.
  3. Rhino is too old to run your plugin.
  4. Your plugin is already installed.
  5. The user wants to uninstall your plugin and its Registry entries.