If PackageManager cannot reach the package server — a common situation in mainland China or on an offline workstation — download the package file and install it directly in Rhino 8. It is the same package, installed the same way.
Nothing here replaces PackageManager — you still install through it, just from a local file instead of a search result.
Use the button below to download designtoolbox-latest-rh8_30-win.yak. This filename always points at the newest release — currently version 1.1.6 for Rhino 8.30 or later on Windows. The same folder also holds versioned copies named designtoolbox-<version>-rh8_30-win.yak if you need to keep a specific build.
Start Rhino 8, type -PackageManager on the command line and press Enter. Mind the leading hyphen - — it runs the scripted, command-line version instead of opening the dialog. When the options Search / Install appear, click Install (or type Install and press Enter).
At the Package file ( Browse ): prompt, click Browse to open the file dialog, select the .yak file you downloaded, and Rhino installs it. You can also paste the full path to the .yak file on the command line and press Enter.
Close Rhino completely and start it again. The plugin only loads after a restart.
Type DesignToolbox on the command line and press Enter to open the panel, then sign in inside the panel.
Prefer the standard route? If your network can reach the package server, simply run PackageManager and search for designtoolbox. See the standard installation steps.
The panel opens, but signing in fails with a network permission error. This is a local firewall or security-software setting on this computer, not an account or server problem.
The DesignToolbox panel opens normally, but signing in fails. The Rhino command line shows login failed together with An attempt was made to access a socket in a way forbidden by its access permissions — Windows socket error 10013.
Something on this computer is blocking the Rhino program itself from reaching the network. The panel's page loads in its own embedded browser process, so it can still open; the sign-in request is sent by Rhino directly, so it gets blocked. This has nothing to do with your account, password or the server. The most common causes are a Windows Firewall outbound rule for Rhino (often named "Rhino 8"), a security suite's program network control (for example Huorong or 360's "block network access"), or a company network policy enforced by device-management software.
If sign-in works while a VPN or proxy tool is running and fails as soon as you turn it off, this is almost certainly the cause. You can also open PowerShell as Administrator and run the command below to check for an outbound block rule that targets Rhino. It only lists matching rules — it does not change anything.
Get-NetFirewallRule | Where-Object { $_.Action -eq 'Block' -and $_.Direction -eq 'Outbound' -and $_.Enabled -eq 'True' } | Get-NetFirewallApplicationFilter | Where-Object Program -like '*Rhino*' | Select-Object Program
Windows Firewall. Open "Windows Defender Firewall with Advanced Security", find the outbound block rule for Rhino 8 (or Rhino.exe) under Outbound Rules, and disable or delete it. As Administrator, you can also run:
Get-NetFirewallRule -DisplayName 'Rhino 8' | Where-Object Direction -eq 'Outbound' | Disable-NetFirewallRule
Security software. In its program network control / network protection settings, set Rhino.exe to allowed.
Company computer. Ask your IT department to allow Rhino.exe to reach designtoolbox.ai on port 443.
After making the change, restart Rhino and sign in again.