Unable to Enable USB Devices on Roon After Update (ref#HFDRCE)

Support
1

What best describes your playback issue?

· A connected audio device is not appearing in Roon

What type of Zone is affected by this problem?

· *Directly-connected Zones* are affected.

Is your RoonServer machine running MacOS 15 Sequoia or above?

· I still can't see my endpoints as available Zones.

Is the affected network Zone connected with Ethernet or WiFi?

· WiFi

Does the device show up at all in Roon Settings -> Audio?

· Yes, it shows up there, but it isn't Enabled

Does the "Enable" button unlock the Zone?

· I pressed Enable, but the Zone remains disabled

Does the device play audio from another source when using the same connection?

· The device has no problems with another audio source

Have you checked that Roon is whitelisted in any firewalls?

· I've checked the firewall and the issue remains

Since you are using a network connection to the device, please ensure that your RoonServer is on the same subnet as the device

· My devices are on a single subnet but is not visible to Roon

Do you have a complex network setup?

· I have a *mesh network* with devices connected to multiples points

Your local network might need some re-arranging to support Roon.

· None of the suggestions have helped me. I'd like to submit a support request.

Do you have an approximate timestamp of when the issue last occurred?

· After the latest windows update

What are the make and model of the affected audio device(s) and the connection type?

· All DAC's via USB to the Windows 11 PC

Describe the issue

Hey Folks,

Version 2.60 Build 1629

Not sure if this is the appropriate place, but I am a long-time Roon user with “zero” issues, and now I have one.

I have been using Roon to test our gear on a Windows 11 PC over the last week, but I am no longer able to enable USB-connected devices as I always have. It just hangs on enabling in the settings audio panel.

This is true of any USB-connected gear; even System output is a no-go. Windows Media, Audirvana, Qobuz ets. all work with no issue, but Roon will not.

I know this is a Roon issue, as I pulled out my laptop (Not used in over a month) and opened Roon, and it connected to my gear with no issue. Then I mistakenly had a Roon update pop up, and I clicked on it.

Now, no USB connections are usable.

Thanks for any help

Describe your network setup

TP Link Mesh network

2

Is your Roon Server an earlier build than version 2.60? If so, then your issue is being caused by an incompatibility between Roon clients version 2.60 and earlier versions of Roon Server. See:

Roon Bridge 2.60 (build 1501) Production with EA Roon Server - Early Access - Roon Labs Community

1 Like
3

Yes it appears so,

I have an intel NUC that’s been running for years; it seems there is no update, though.

image
image714×276 29.3 KB

Thanks

4

You can use the Web Administration Interface of your ROCK/NUC to Reinstall RoonOS - that should pull in the latest version of Roon Server. Reinstallation of RoonOS won’t reset your database and settings, but you might want to make a backup first just to be on the safe side…

1 Like
5

Thanks so much for the help,

Really appreciated!

6

Unfortunately it still lists 2.59

Screenshot 2026-02-23 125724
Screenshot 2026-02-23 125724574×164 12.6 KB

7

OK - let’s see what the Support Team have to say.

1 Like
8

Hello @Louis_Butwin

Thank you for the report.

Looking at your system diagnostics, we have identified the root cause: Software Version Mismatch.

Your ROCK Core is currently running on the Early Access branch, while your Windows PC is on the Production branch. Because these two builds are on different development tracks, they are unable to communicate correctly to initialize the local audio devices.

To resolve this: Please migrate your ROCK Core back to the Production build so that it matches your Windows remote. Once both the Core and the Remote are on the same track, your USB devices should enable correctly.

1 Like
9

Thank you for the instructions. This has resolved my issue.

My only question would be why I did not automatically get the update. I have been running early access the whole time and never had an issue until this last move from2.59 to 2.60

Thanks for your assistance

10

Because there is no update as yet for the Early Access version 2.59 build. That’s why @vadim recommended you move it to the Production Build, which is version 2.60.

Having a mix of Early Access and Production builds in your Roon ecosystem is not recommended because of the possibility of issues such as this arising.

1 Like
11

Understood,

Thanks again for your help

12

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.