Windows PC Audio Devices not showing (ref#II7M9A)

[gweb (George W)]

What best describes your playback issue?

· My DAC, streamer, or speaker doesn't appear as a Zone in Roon

What type of Zone is affected by this problem?

· *Directly-connected Zones* are affected.

Is your device connected directly to the Roon Server via cable or over the network, or is it chained through another device (such as a streamer, Roon Bridge, or Roon Remote)?

· It is connected through a different device (e.g Rasberry Pi)

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?

· Both the device and RoonServer are connecting to a *single router*

Try to disable any additional networking interfaces on your RoonServer machine.

· Disabling network interfaces had no change in behavior

Check to make sure RoonReady mode is selected on the device.

· I've checked this and the issue remains

If the device has multiple output options, do the other options work as expected?

· Multiple output types are affected

Is the device using the latest firmware as per the manufacturer?

· Firmware is up-to-date but the issue remains

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

· 29/04/2025 12:34

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

· No audio device is showing at this PC (Windows 11 Default Audio, Realtek Audio, FiiO K7 DAC)

Describe the issue

Windows PC Audio Devices not showing

Describe your network setup

Roon Server runs on MiniPC, hardwired to the router (asus rt-ax86u pro). The affected Windows PC is also hardwired to the router (but I tried Wifi with the same problem)

Further Description

I've had device dropouts on this PC occasionally, but they were always resolved with a server reboot. Since 2.49 and 2.50, no audio device is showing on this PC at all, and no reboot of PC or Server helps.

I have reinstalled Roon on the PC, deactivated all other network devices, restarted the router, deactivated firewall, and nothing helped. All other PCs in the house connected to the same network work absolutely fine.

The RAATServer_log.txt finds the Audio devices:

04/29 12:47:06 Trace: [raatmanager/windows] FOUND type=wasapi id={0.0.0.00000000}.{98922e6a-5e9d-40c4-a723-ce2d49fdc00f} usb_id=2972:0047
04/29 12:47:06 Trace: [raatmanager/windows]       name=FiiO Q series                  output_name=Speakers                      
04/29 12:47:06 Trace: [raatmanager/windows] FOUND type=wasapi id={0.0.0.00000000}.{dcf31037-076b-4d1a-a8df-c77460674685} usb_id=047f:02e6
04/29 12:47:06 Trace: [raatmanager/windows]       name=Poly BT700                     output_name=Headset Earphone              
04/29 12:47:06 Trace: [raatmanager/windows] FOUND type=asio   id={6B3BA606-8664-4426-8994-0F1E6FE6199F} usb_id=
04/29 12:47:06 Trace: [raatmanager/windows]       name=FiiO ASIO Driver               output_name=                              
04/29 12:47:06 Trace: [raatmanager/windows] FOUND type=asio   id={A80362FF-CE76-4DD9-874A-704C57BF0D6A} usb_id=
04/29 12:47:06 Trace: [raatmanager/windows]       name=Realtek ASIO                   output_name=     

But further down in the log I get several instances of ‘destroying client’

04/29 12:47:08 Trace: [jsonserver] [192.168.1.6:37654] accepted connection
04/29 12:47:08 Trace: [jsonserver] [192.168.1.6:37654] read error: connection reset by peer
04/29 12:47:08 Trace: [jsonserver] [192.168.1.6:37654] destroying client
04/29 12:47:08 Trace: [jsonserver] [192.168.1.6:37676] read error: connection reset by peer
04/29 12:47:08 Trace: [jsonserver] [192.168.1.6:37676] destroying client
04/29 12:47:08 Trace: [jsonserver] [192.168.1.6:37666] read error: connection reset by peer
04/29 12:47:08 Trace: [jsonserver] [192.168.1.6:37666] destroying client

This looks similar to this thread, but now even a server/PC reboot does not help anymore.

[vadim]

Hello @gweb,

Thank you for reaching Roon support.

We’ve enabled diagnostics mode for your account. Your server IP is shown as:

192.168.1.6

However, our logs show your Roon Remote is on 192.168.192.4, which is a different subnet and may be causing the connection issue.

Could you please share the network configuration of both devices? On each PC:

1. Open Command Prompt (Win + R → type cmd → Enter).
2. Run:

   ipconfig /all
   

3. Copy the full output and paste it here.

This will help us verify that both the Core and Remote are on the same network. Thanks!

[gweb (George W)]

The Roon server LAN IP is 192.168.1.6. I have Zerotier installed on the Roon Server (which runs Linux), which gives it the IP 192.168.192.6 on the Zerotier Interface.

But Zerotier is not installed on the problematic Windows PC (I removed it during troubleshooting). Its IP is 192.168.1.222. 192.168.192.4 is a completely different PC (which works fine, by the way).

Other PCs that are connected to the local subnet (192.168.1.0) also don’t have Zerotier installed and work fine. It is just this one PC (192.168.1.222) that is problematic.

[noris]

Hello @gweb ,

Since you are using a Windows PC, I would verify that both Roon.exe and RAATServer.exe have been added as exceptions to your Windows firewall.

You can use these instructions to add the exceptions and the executables themselves would be located in your Database Location/Application folder path.

I would also add these exceptions to any Antivirus or other Firewall blocking applications you may have and ensure that you connected to your network via a Private network, not a Public one, see this guide for more information.

[gweb (George W)]

I am familiar with the instructions that you have linked and have added roon and raatserver to the exceptions. I have also deactivated the firewall completely. None of this helped. I do not have any other Antivirus/Firewall installed but the Win11 included ones.

[gweb (George W)]

A quick update: overnight I installed a Roon backup on a different server to rule out any database issues (as that version worked fine), but the issue is still there. Since 2.50 I cannot get this PC (192.168.1.222) to show any audio devices. All other endpoints work fine.

[daniel]

Hi @gweb,
Thanks for letting us know about the test with the database. Can we try a fresh database to see if that’s the problem? You can use these steps.

• Create a Backup of your current database
• Exit out of Roon + RoonServer (from taskbar area)
• Navigate to your Roon Database Location
• Find the folder that says “Roon Server” and “Roon”
• Rename the “RoonServer” folder to “RoonServer_old” and “Roon” to “Roon_old”
• Reinstall the Roon App from our Downloads Page to generate a new Roon folder
• Verify if the issue persists on a fresh database before restoring the backup

Here is the process outlined from a Windows machine:

If the problem persists after we can be pretty sure the issue is the audio devices’ connection to the rest of the local network.

[gweb (George W)]

Just to be clear, I should do this on the problematic Windows PC (which is a Roon endpoint)? And not on the Linux Roon Server?

[connor]

Hi @gweb,

Since we’ve migrated the database to a new machine and the issue persisted, my colleague was suggested to try on a completely fresh install (on an entirely new database). Unless you delete the RoonServer folder itself, Roon will continue to reference elements of the existing database - it’s for this reason you have to go in and delete the database deeply. You can perform this test on either machine, but you’ll want to ensure you have a Backup of RoonServer to retain your original database if you do this on the RoonServer machine.

Please reach out if you have any questions. Thanks!

[gweb (George W)]

I have tried a completely new roon server installation as you suggested, but that also did not solve the problem. As you said, this points to a Roon client network issue, and I have since solved it with a number of standard Windows ‘repair’ commands.

I am documenting the steps I took here in case it helps someone else. I don’t know which step worked, but after running these and a reboot it works again!

Repair System Files with SFC
sfc /scannow

Repair the Windows Image with DISM
DISM /Online /Cleanup-Image /RestoreHealth

Check & Repair the File System (CHKDSK)
chkdsk C: /f /r /x

Reset Network Stack

netsh int ip reset
netsh winsock reset

[daniel]

Hi @gwebm,
We’re glad to hear you were able to fix the network issue! Thanks for sharing the steps you took — that kind of detail is really helpful for others who might run into the same problem. Let us know if you need anything else.