Rhino 7 crash and freezes badly on start since a week or so

My installation of Rhino 7, all of a sudden (same NVidia Quadro video drivers since years), started to crash on startup: Rhino opens but it “freezes” before the viewports are starting to show the grid.

It’s not possible to force-close and the Rhino process is not appearing in Task manager: task manager itself kind of crashes (showing only a part of the processes and no icons of the processes) and becomes unresponsive. The only way is to hard reset the PC each time.

Now Rhino only works in safe mode with GPU OPENGL at minimum level, but as soon as I start to make it higher and re-start in normal mode, it freezes again. I tried to repair windows 11, repair Rhino 7 and update NVidia drivers to more recent ones (last available fr my PC are 2020 ones). Even re-installed Rhino. Nothing seems to work.

This is really big trouble for me: can someone help ?

Gianpietro


Here is my sysinfo from safe mode (Consider that these drivers are old but they worked since last week):

Rhino 7 SR38 2024-12-3 (Rhino 7, 7.38.24338.17001, Git hash:master @ 97e36efa02d7f71638988290bb2d190fcf1b18c5)
License type: Commercial, build 2024-12-03
License details: Cloud Zoo

Windows 11 (10.0.26100 SR0.0) or greater (Physical RAM: 16Gb)

Computer platform: LAPTOP - Plugged in [100% battery remaining]

Non-hybrid graphics configuration.
Primary display and OpenGL: Intel(R) HD Graphics 4600 (Intel) Memory: 1GB, Driver date: 8-16-2018 (M-D-Y). OpenGL Ver: (null)

    Integrated graphics device with 3 adapter port(s)

    Windows Main Display is laptop’s integrated screen or built-in port
    Secondary monitor attached to adapter port #1

Secondary graphics devices.
NVIDIA Quadro K1100M (NVidia) Memory: 2GB, Driver date: 1-22-2020 (M-D-Y).

    Integrated accelerated graphics device (shares primary device ports)

    This device is not being used

ATTENTION:
Safe Mode is enabled. Graphics device usage and OpenGL information cannot be collected.

OpenGL Settings
Safe mode: On
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 2.1

Anti-alias mode: None
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: Unknown
Render version: (null)
Shading Language: (null)
Driver Date: 1-22-2020
Driver Version: 25.21.14.2650
Maximum Texture size: n/a
Z-Buffer depth: n/a
Maximum Viewport size: 16777472 x 16777217
Total Video Memory: 2 GB

Rhino plugins that do not ship with Rhino

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.38.24338.17001
C:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.38.24338.17001

Viewport freezing is typically due to the graphics configuration.

Unfortunately it doesn’t appear to be any supported drivers for Windows 11.

Unluckyly I know. But the very strange thing is that I use these driver with Rhino 7 since years and they worked flawlessly until yesterday…or a couple of days ago, I can’t tell.

I think the problem must be in something happened in these few days: I’m suspecting about a damned Windows Update Package: right now I am suspecting security update KB5074109, as googling on this (it was the last installed on my machine, according to Updates History: it dates yesterday) some people refers about NVidia drivers problem after installing it…

Now I uninstalled it and I re-start the machine: will keep you informed.

That was my next question. Let us know if you want to try a older Rhino version, but the changes of the last several releases are fairly minor, so leaning towards the windows update / graphics compatibility.

Yeah you’re on borrowed time, Windows is going to change sooner or later and break it.

BINGO!

Here are the steps that solved the problem:

  1. I uninstalled Windows Update Security Package KB5074109 (that Win11 automatically installed yesterday, Jan 19) by running the command: wusa /uninstall /kb:5074109 in an elevated Command Prompt (run as Administrator).
  2. I restarted Windows to finish the uninstall procedure.
  3. I downloaded the “Show or Hide updates” windows tool: it’s deprecated but you can still download it from Microsoft and it works perfectly in win 11.
  4. I launched the tool and set the KB5074109 package as “hidden” to win update so it doesn’t ask anymore to install it.
  5. Re-started the system.

Et voilà !! Rhinoceros runs flawlessly again with OpenGL at maximum level and GPU antialiasing and tessellation ON. No more Rhino crashes and system freezing.

I can’t describe how happy I am.

By the way: thank you a lot, Microsoft, for these 4 hours of work lost for your damned updates.

PS: these are a couple of link for info and useful apps to solve this problem:

https://overclock3d.net/news/software/new-windows-update-ruins-nvidia-geforce-gpu-performance-reports-claim/

Thanks to everyone who gave at least some attention to my request !

I hope the little tutorial I posted can help someone facing a similar problem.

Good night (here in Italy it’s 10:18 p.m.)

Gianpietro

So the conclusion is dont install windows 11 unless you want to mess around in microsofts horse s*** of a modern OS​:joy:

I would be more generic: don’t install Windows (any version). Full stop. :grin:

PS: Unluckily there’s no Rhino porting for Linux: and that’s the only reason I still have Windoze in my studio and fight with KB#@#**sh1t#…

I have a same issue of Rhino freezing before it shows view windows, they are just black. Worked for years. Sometime ago just stopped. Running a win10 (computer good, no fancy new microshit chip inside). Running older rhino - a version 6

Check for last windows updates: code and date. Check for the one I named…

So, did you solve?

Update on windows updates.

Could Microsoft stop doing disasters with its f****ng updates ? Of course not.

So the same, identical behavior came again with a new (automatic!) security update: exactly same thing happened with security update KB 5077181 installed on February 12th, 2026.

Same procedure used for previous one, solves this new issue as well.

Thank you Microsoft !