Roon client on Windows 10 doesn't see connected audio devices intermittently (ref#TVLJUH)

ISkIN · May 13, 2026, 1:11pm

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· There is a Roon Server installed on a PC with Windows 10 and a Roon client installed on another PC with Windows 10 (connected via Ethernet through a router).
The client does not see any connected audio devices/zones.
Only one audio output is available directly on the Roon Server, and all the others connected to the current computer are not (the PC with the Roon client has a standard system audio output and a USB DAC).
After rebooting the PC, this is most often fixed, but then it occurs again. Perhaps this is a problem with the RAATServer.

Tell us about your home network

· Roon Server -> Ethernet -> router Tplink Archer C6 -> Ethernet -> Roon client PC

benjamin · May 14, 2026, 11:19pm

Hi @ISkIN,

This looks like Roon Remote on the Windows 10 client is intermittently losing sight of the local audio endpoints on that machine, rather than a problem with the audio devices themselves.

To narrow it down, there are two things I’d like to check first:

Does the Windows client still show the same audio devices in Device Manager and in Windows sound settings when Roon stops seeing them?
Are the client PC and the Roon Server both connected by Ethernet only, or is either machine also using WiFi, powerline, or a switch in between?

In the meantime, please try this on the client PC when the zones disappear: open Roon Settings > Audio, leave it open for a moment, and then restart the Roon Server service on the server machine. If the devices come back after that, it points us toward a discovery or RAAT service issue rather than a hardware fault.

If you can, also let us know whether the USB DAC is powered on and connected before Roon starts, or if it is being plugged in after the fact. That detail matters here.

Send back what you find, and we’ll take the next step from there.

ISkIN · May 17, 2026, 6:38pm

Yes, the same audio devices are always available in the device manager and play audio through other programs
Ethernet only via router

It doesn’t matter when the USB DAC was connected - in both cases, if a problem occurs, it is not displayed.
There are only two options: either there is a problem and all local audio devices (including Windows default system output, DAC, etc) are not displayed on the client Roon Remote from the very start, or there is no problem and all are displayed. The problem can also occur without a DAC connection.

At the moment, I have not been able to reproduce the problem again to check the case with the Roon Server restart, but as soon as it occurs again, I will provide the missing information. But, if I remember correctly, the problem persisted when Roon Server was restarted.

Also, if you need the logs, I can send them as soon as the problem occurs again.

noris · May 20, 2026, 11:21pm

Hello @ISkIN ,

Yes, please let us know the exact local time + date when the problem reoccurs, and we’ll enable diagnostics for your account. Did you by any chance clone one of the Windows PCs into the other one or were they set up as fresh installs? I have sometimes seen VPNs and firewalls also cause this behavior.

ISkIN · May 27, 2026, 8:27am

The problem has occurred again, so I can now provide the necessary information. Today, at about 10:00 AM, I woke the computer up from sleep mode and launched Roon Remote. The problem with the missing audio devices occurred again.

Roon suggested updating the client and the server, and after restarting both, the problem persisted. As for the installation, the latest versions of Windows were installed on the server and the client; there was no cloning. Although initially Roon Server was installed on the client computer, and then I moved it to another one (I don’t remember if I moved the database at that time).

As for firewalls/VPN, the firewall is disabled, and exceptions are specified in the VPN, so it is unlikely to cause problems. I also tried turning off all VPNs and network filtering applications, but that didn’t help, so I don’t think that’s the problem (especially since, in most cases, everything works well).

Screenshot Roon Remote

Below, I have attached a section of the Roon and RAATServer log from the moment I click “Refresh” in the list of audio devices in Roon.

Roon log

05/27 10:39:33 Info: [raatserver] [runner] Start or Connect...
05/27 10:39:33 Info: [raatserver] [runner] Start or Connect... C:\Users\ISkIN\AppData\Local\Roon\Application\RAATServer.exe
05/27 10:39:33 Info: ConnectOrStartAndWaitForExit RAATServer, path: C:\Users\ISkIN\AppData\Local\Roon\Application\RAATServer.exe
05/27 10:39:33 Info: ConnectOrStartAndWaitForExit RAATServer: Try to connect to existing raatserver
05/27 10:39:34 Warn: AddTopLevel: dimlayer(314)
05/27 10:39:34 Warn: AddTopLevel: dimlayer(314)
05/27 10:39:34 Warn: AddTopLevel: capturelayer(324)
05/27 10:39:34 Warn: AddTopLevel: capturelayer(324)
05/27 10:39:34 Warn: AddTopLevel: win_spinner(4132)
05/27 10:39:34 Warn: AddTopLevel: win_spinner(4132)
05/27 10:39:35 Info: ConnectOrStartAndWaitForExit RAATServer: Failed to connect to existing raatserver, let's start one
05/27 10:39:35 Info: [raatserver] [runner] Status: Started
05/27 10:39:43 Info: [stats] 2234490mb Virtual, 380mb Physical, 56mb Managed, 324mb estimated Unmanaged, 1127 Handles, 36 Threads, 0.09% of runtime in GC pauses, 1ms last GC pause duration
05/27 10:39:43 Debug: threshold_minutes: 10080
05/27 10:39:44 Warn: exception starting raatserver: System.Net.Sockets.SocketException (10061): No connection could be made because the target machine actively refused it. [::ffff:127.0.0.1]:9004
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
at Sooloos.RAATServer.ConnectOrStartAndWaitForExit(String path, String args, Action`1 status, ChildProcess& p)
05/27 10:39:45 Info: [raatserver] [runner] Start or Connect...
05/27 10:39:45 Info: [raatserver] [runner] Start or Connect... C:\Users\ISkIN\AppData\Local\Roon\Application\RAATServer.exe
05/27 10:39:45 Info: ConnectOrStartAndWaitForExit RAATServer, path: C:\Users\ISkIN\AppData\Local\Roon\Application\RAATServer.exe
05/27 10:39:45 Info: ConnectOrStartAndWaitForExit RAATServer: Try to connect to existing raatserver
05/27 10:39:47 Info: ConnectOrStartAndWaitForExit RAATServer: Failed to connect to existing raatserver, let's start one
05/27 10:39:47 Info: [raatserver] [runner] Status: Started
05/27 10:39:55 Warn: exception starting raatserver: System.Net.Sockets.SocketException (10061): No connection could be made because the target machine actively refused it. [::ffff:127.0.0.1]:9004
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
at Sooloos.RAATServer.ConnectOrStartAndWaitForExit(String path, String args, Action`1 status, ChildProcess& p)

RAATServer log

05/27 10:39:36 Info: Starting RAATServer v2.67 (build 1662) earlyaccess on windows
05/27 10:39:36 Info: Local time is 27-May-26 10:39:36 AM, UTC time is 27-May-26 7:39:36 AM
05/27 10:39:36 Trace: [bits] myinfo: {“os”:“Windows 10”,“platform”:“windows”,“machineversion”:206701662,“branch”:“earlyaccess”,“appmodifier”:“”,“appname”:“RAATServer”}
05/27 10:39:36 Debug: [easyhttp] [1] POST to ``https://bits.roonlabs.net/1/q/roon.base.,roon.internet_discovery.,roon.raatserver``. returned after 655 ms, status code: 200, request body size: 130 B
05/27 10:39:36 Trace: [bits] updated bits, in 677ms
05/27 10:39:36 Info: [RAATServer] creating RAAT__manager
05/27 10:39:36 Info: [RAATServer] appdata_dir = C:\Users\ISkIN\AppData\Local\RAATServer
05/27 10:39:36 Info: [RAATServer] unique_id = 35b05d98-aa4f-48ae-a3d1-e5bd7cad005a
05/27 10:39:36 Info: [RAATServer] machine_id = 07488255-4586-e728-9d3e-29b7b697ae61
05/27 10:39:36 Info: [RAATServer] machine_name = SUPERCOMPLUKTER
05/27 10:39:36 Info: [RAATServer] os_version = Windows 10
05/27 10:39:36 Info: [RAATServer] vendor =
05/27 10:39:36 Info: [RAATServer] model =
05/27 10:39:36 Info: [RAATServer] service_id = d7634b85-8190-470f-aa51-6cb5538dc1b9
05/27 10:39:36 Info: [RAATServer] is_dev = False
05/27 10:39:36 Trace: [raatmanager] starting
05/27 10:39:36 Info: [raatmanager] added codesigning key keypair_name=Roon public_key=9bb28e4e9e34ed4ff75c6a35339497cbdd3420713c941f5468571afc03555bf7
05/27 10:39:36 Trace: [raatmanager] [System Output] loaded config from C:\Users\ISkIN\AppData\Local\RAATServer\Settings\device_9b961fc2035f3dd343e04f8f136e7682.json
05/27 10:39:36 Trace: [raatmanager/windows] FOUND type=wasapi id={0.0.0.00000000}.{b70b23a7-c33d-4b81-b68e-a69458f14434} usb_id=
05/27 10:39:36 Trace: [raatmanager/windows] name=High Definition Audio Device output_name=Наушники
05/27 10:39:36 Trace: [raatmanager/windows] FOUND type=asio id={40F4F7C8-786F-49EB-8521-23CC5358D70E} usb_id=
05/27 10:39:36 Trace: [raatmanager/windows] name=TUSBAudio ASIO Driver output_name=
05/27 10:39:36 Trace: [raatmanager/windows] FOUND type=asio id={64083085-BD64-42AA-ADA3-73F51E17CAD7} usb_id=
05/27 10:39:36 Trace: [raatmanager/windows] name=XMOS USB Audio 2.0 ST 3085 output_name=
05/27 10:39:36 Trace: [raatmanager] [TUSBAudio ASIO Driver] loaded config from C:\Users\ISkIN\AppData\Local\RAATServer\Settings\device_c970e1eea47893c3cf8c1e31c8a5f514.json
05/27 10:39:36 Trace: [raatmanager] [XMOS USB Audio 2.0 ST 3085] loaded config from C:\Users\ISkIN\AppData\Local\RAATServer\Settings\device_5e315854e47d084264cd8195f66e7223.json
05/27 10:39:36 Trace: [raatmanager] initialized
05/27 10:39:37 Info: [RAATServer] running RAAT__manager
05/27 10:39:37 Warn: [raatmanager] update_bits, json string: {}
05/27 10:39:37 Trace: [raatmanager] starting discovery
05/27 10:39:37 Trace: [discovery] starting
05/27 10:39:37 Info: [discovery] [iface:VPN Work 2FA:172.30.254.43] multicast recv socket is bound to 0.0.0.0:9003
05/27 10:39:37 Info: [discovery] [iface:VPN Work 2FA:172.30.254.43] multicast send socket is bound to 0.0.0.0:61624
05/27 10:39:37 Info: [discovery] [iface:vEthernet (Ethernet):172.26.64.1] multicast recv socket is bound to 0.0.0.0:9003
05/27 10:39:37 Info: [discovery] [iface:vEthernet (Ethernet):172.26.64.1] multicast send socket is bound to 0.0.0.0:61625
05/27 10:39:37 Info: [discovery] [iface:vEthernet (Default Switch):172.27.224.1] multicast recv socket is bound to 0.0.0.0:9003
05/27 10:39:37 Info: [discovery] [iface:vEthernet (Default Switch):172.27.224.1] multicast send socket is bound to 0.0.0.0:61626
05/27 10:39:37 Info: [discovery] [iface:Ethernet:192.168.1.100] multicast recv socket is bound to 0.0.0.0:9003
05/27 10:39:37 Info: [discovery] [iface:Ethernet:192.168.1.100] multicast send socket is bound to 0.0.0.0:61627
05/27 10:39:37 Info: [discovery] [iface:Loopback Pseudo-Interface 1:127.0.0.1] multicast recv socket is bound to 0.0.0.0:9003
05/27 10:39:37 Info: [discovery] [iface:Loopback Pseudo-Interface 1:127.0.0.1] multicast send socket is bound to 0.0.0.0:61628
05/27 10:39:37 Info: [discovery] [iface:vEthernet (VPN Work 2FA):192.168.144.1] multicast recv socket is bound to 0.0.0.0:9003
05/27 10:39:37 Info: [discovery] [iface:vEthernet (VPN Work 2FA):192.168.144.1] multicast send socket is bound to 0.0.0.0:61629
05/27 10:39:37 Info: [discovery] unicast socket is bound to 0.0.0.0:9003
05/27 10:39:37 Trace: [raatmanager] starting server
05/27 10:39:37 Error: [jsonserver] uv_tcp_bind or uv_listen failed: permission denied
05/27 10:39:37 Error: [raatmanager] while starting json server: RNET__JSON_SERVER_STATUS_NETWORK_ERROR

vadim · June 2, 2026, 12:45pm

Hi @ISkIN,

Thank you for the logs — they point directly to the cause.

RAATServer is failing to bind to port 9004 on your machine with a permission denied error:

[jsonserver] uv_tcp_bind or uv_listen failed: permission denied
[raatmanager] while starting json server: RNET__JSON_SERVER_STATUS_NETWORK_ERROR

This means something on your Windows machine is blocking RAATServer from opening that port after waking from sleep. The most likely culprit is another process that has already claimed port 9004, or a network policy introduced by one of your VPN adapters.

We can also see several virtual network interfaces active at the same time (VPN Work 2FA, vEthernet Default Switch, vEthernet Ethernet), which can interfere with RAATServer’s ability to bind correctly on wake.

Please try the following:

Check what is holding port 9004 — open Command Prompt as Administrator and run:
```
netstat -ano | findstr :9004
```
Share the output here so we can see what process is occupying the port when the issue occurs.
Disconnect your VPN before waking from sleep and see if the problem still occurs — this will help us confirm whether the VPN adapters are the trigger.
Verify your .NET 10 installation — since Roon 2.65 migrated to .NET 10, please confirm it is correctly installed on your machine. Open Command Prompt and run:
```
dotnet --list-runtimes
```
and share the output. If .NET 10 is missing or corrupted, it can prevent RAATServer from starting properly. You can download the latest .NET 10 runtime from here.

Let us know what both commands show!