# Roon 3.0 ROCK access **URL:** \ **Category:** Early Access\ **Created:** [October 12, 2026, 6:59pm UTC](https://community.roonlabs.com/t/roon-3-0-rock-access/326036 "2026-10-12T18:59:43Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Rugby](https://community.roonlabs.com/user_avatar/community.roonlabs.com/rugby/32/360588_2.png) [@Rugby](https://community.roonlabs.com/u/Rugby)\ **Post date:** [October 12, 2026, 6:59pm UTC](https://community.roonlabs.com/t/roon-3-0-rock-access/326036/1 "2026-10-12T18:59:43Z")
I just noticed this. > [@Early Access: RoonOS (Nucleus/ROCK) #284 is live!](https://community.roonlabs.com/t/early-access-roonos-nucleus-rock-284-is-live/326027/1): > > ROCK on a supported Intel NUC Does that mean if I have a MOCK ROCK, for example using a newer gen Intel chip, that it won’t ever update to 3.0. Or, if I am using ROCK on a NUC with an AMD chip? ---
**Author:** ![Suedkiez](https://community.roonlabs.com/user_avatar/community.roonlabs.com/suedkiez/32/107321_2.png) [@Suedkiez](https://community.roonlabs.com/u/Suedkiez)\ **Post date:** [October 12, 2026, 7:09pm UTC](https://community.roonlabs.com/t/roon-3-0-rock-access/326036/2 "2026-10-12T19:09:49Z")
I think it just means that it must be an UEFI installation, as has been the case for all RoonOS updates since 2.1 (and the final 1.0 update as well) ---
**Author:** ![Rugby](https://community.roonlabs.com/user_avatar/community.roonlabs.com/rugby/32/360588_2.png) [@Rugby](https://community.roonlabs.com/u/Rugby)\ **Post date:** [October 12, 2026, 7:11pm UTC](https://community.roonlabs.com/t/roon-3-0-rock-access/326036/3 "2026-10-12T19:11:31Z")
Maybe, but, it would be good to know officially. ---
**Author:** ![Suedkiez](https://community.roonlabs.com/user_avatar/community.roonlabs.com/suedkiez/32/107321_2.png) [@Suedkiez](https://community.roonlabs.com/u/Suedkiez)\ **Post date:** [October 12, 2026, 7:15pm UTC](https://community.roonlabs.com/t/roon-3-0-rock-access/326036/4 "2026-10-12T19:15:36Z")
I wouldn’t expect this to have changed, but I don’t think it ever excluded MOCK. Surely someone with a MOCK would have said something by now? > [@RoonOS 3.0 supported devices](https://community.roonlabs.com/t/roonos-3-0-supported-devices/319853/5): > > The supported devices for Roon OS v3.0 is Nucleus One, Nucleus Titan, and the existing support for NUC UEFI boxes. ---
**Author:** ![Paul\_Argue](https://community.roonlabs.com/user_avatar/community.roonlabs.com/paul_argue/32/372416_2.png) [@Paul\_Argue](https://community.roonlabs.com/u/Paul_Argue)\ **Post date:** [October 12, 2026, 7:32pm UTC](https://community.roonlabs.com/t/roon-3-0-rock-access/326036/5 "2026-10-12T19:32:04Z")
UEFI devices will continue to get update notifications regardless of the processor type. Machines outside of the list of supported devices are supported best effort. ---
**Author:** ![Roland\_von\_Unruh](https://community.roonlabs.com/letter_avatar/roland_von_unruh/32/5_5575768a8748004e209b776fc1b2916d.png) [@Roland\_von\_Unruh](https://community.roonlabs.com/u/Roland_von_Unruh)\ **Post date:** [October 12, 2026, 7:36pm UTC](https://community.roonlabs.com/t/roon-3-0-rock-access/326036/6 "2026-10-12T19:36:06Z")
RoonOS 3.0 early access works fine as a MOCK installation on a GMKTec G3plus (intel N150) device. In fact, while RoonOS 2.0 doesn’t support the GMKTecs USB ports properly, this works fine in RoonOS 3.0, supposedly thanks to the updated Linux kernel supporting newer hardware. ---
**Author:** ![Leroy\_la\_Fontaine](https://community.roonlabs.com/letter_avatar/leroy_la_fontaine/32/5_5575768a8748004e209b776fc1b2916d.png) [@Leroy\_la\_Fontaine](https://community.roonlabs.com/u/Leroy_la_Fontaine)\ **Post date:** [October 14, 2026, 7:59pm UTC](https://community.roonlabs.com/t/roon-3-0-rock-access/326036/7 "2026-10-14T19:59:16Z")
I have no success on virtualized ROCK. The production release has been working like a charm, but when I put the .bin-file in the reinstall map, and I click install, it just reboots RoonOS 2.1 (build 271) production instead. EDIT: Nevermind, there’s a wrong link in this article: > **[Roon Early Access download links - Roon Early Access Program](https://help.roonlabs.com/portal/en/kb/articles/roon-early-access-program#Roon_Early_Access_download_links)** > > If you are uncertain about where to post your issue then please post it to the #Early Access category. If it's in the wrong place we’ll happily move it on your behalf. | What is Early Access? The Early Access program allows Roon users to test the... =========================== (…) **Roon Early Access download links** **macOS** [Roon](https://download.roonlabs.net/builds/earlyaccess/Roon.dmg) **Windows** [Roon](https://download.roonlabs.net/builds/earlyaccess/RoonInstaller64.exe) **RoonOS** [Instruction File](https://workdrive.zoho.com/file/1j0sd0db74ea4d6d3454c8dc36ddf8c4f0086) _ **← this points to the wrong file** _ (…) ---
**Author:** ![Johnny\_Ooooops](https://community.roonlabs.com/user_avatar/community.roonlabs.com/johnny_ooooops/32/121403_2.png) [@Johnny\_Ooooops](https://community.roonlabs.com/u/Johnny_Ooooops)\ **Post date:** [October 14, 2026, 9:33pm UTC](https://community.roonlabs.com/t/roon-3-0-rock-access/326036/8 "2026-10-14T21:33:05Z")
> [@Leroy\_la\_Fontaine](#): > > I have no success on virtualized ROCK Hey @Leroy_la_Fontaine curious why virtualize as a ROCK vm? I have Roon running on a Debian lxc. Just wondering, thanks. ---
**Author:** ![Leroy\_la\_Fontaine](https://community.roonlabs.com/letter_avatar/leroy_la_fontaine/32/5_5575768a8748004e209b776fc1b2916d.png) [@Leroy\_la\_Fontaine](https://community.roonlabs.com/u/Leroy_la_Fontaine)\ **Post date:** [October 15, 2026, 12:56pm UTC](https://community.roonlabs.com/t/roon-3-0-rock-access/326036/10 "2026-10-15T12:56:21Z")
No Roon/music-related reason at all. I have a home server running various VMs and other services. I don’t see any reason to dedicate a separate device to Roon if I can simply spin up a VM for ROCK. 🙂 And as a benefit, I can back up the VM itself and the library to a second server. EDIT: In hindsight, you probably meant something else. ROCK was one of the first things I tried running on Proxmox, and PVE was my first experience with virtualization. VMs were simply the first thing I looked into, before I even considered containers. Once it worked, I never looked back. 😅