# Beta install - something went wrong first run

**URL:** <https://discourse.mcneel.com/t/beta-install-something-went-wrong-first-run/220333>\
**Category:** Serengeti (Rhino BETA)\
**Tags:** windows, mac\
**Created:** [June 26, 2026, 7:22am UTC](https://discourse.mcneel.com/t/beta-install-something-went-wrong-first-run/220333 "2026-06-26T07:22:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Helvetosaur](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/helvetosaur/32/635974_2.png) [@Helvetosaur](https://discourse.mcneel.com/u/Helvetosaur)\
**Post date:** [June 26, 2026, 7:22am UTC](https://discourse.mcneel.com/t/beta-install-something-went-wrong-first-run/220333/1 "2026-06-26T07:22:18Z")

</div>

Installed the Beta just now - after getting the notice of a new version from the WIP, closing that and letting the automatic installer run. Double click on the Beta icon, and something appears to start, but no Rhino window appears. Went in Task Manager and there was no “ghost Rhino” running, but I did find this:

 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/a/7/f/a7f2a1ea09b62d1e9654960bac85fcb85712d4b3.png)

After five minutes, it was still running, so I assumed something went wrong. I killed the process and started again, and this time the Beta opened. Seems normal now. Just a heads-up.

---

<div class="post-metadata">

**Author:** ![jesterking](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jesterking/32/771114_2.png) [@jesterking](https://discourse.mcneel.com/u/jesterking)\
**Post date:** [June 27, 2026, 2:56am UTC](https://discourse.mcneel.com/t/beta-install-something-went-wrong-first-run/220333/2 "2026-06-27T02:56:04Z")

</div>

> [@Helvetosaur](#):
>
> After five minutes, it was still running, so I assumed something went wrong. I killed the process and started again, and this time the Beta opened. Seems normal now. Just a heads-up.

That is the program that compiles the RhinoCycles kernels. The compile time can be even up to 20 minutes or more. The program will automatically close if the compile takes longer than 30 minutes. When I created the program the goal was to keep Rhino responsive when switching to Raytraced or using Rhino Render while kernel compilation is still in progress. This is when Raytraced/Rhino Render should show that it is running on the CPU even though GPU is selected. In days of old Raytraced/Rhino Render would just appear to hang for the time it took to (re)compile the kernel in the Rhino process. The compiler is doing that outside of the Rhino process in a separate one.

It should not prevent Rhino from starting though, and I don’t think it does. Unless code around this has changed (but doesn’t look like it has [Commits · mcneel/RhinoCycles · GitHub](https://github.com/mcneel/RhinoCycles/commits/rhino-9.x/) )
