Roon 2 (Build 1223) can’t find audio devices (redux)

A couple days after having seemingly solved a previous issue (v. https://community.roonlabs.com/t/roon-2-build-1223-can-t-find-audio-devices/236048) it has repeated itself.

As per the earlier posting: ‘Since updating to the most recent build of Roon a couple days ago, the software is no longer able to find audio devices apart from the default ‘Roon Tested’ device, which is an AirPlay connexion to my AVR. (I normally run Roon using the ASIO4ALL driver.)

‘My Win 10 Home laptop is fully patched.

‘I have uninstalled and reinstalled Roon on several occasions, even rebooting between uninstall and reinstall, but with zero success.

‘The issue seems to be that RAAT Server isn’t running, and there seems to be no way in which to launch the process.’

I should point out that Roon finds the appropriate audio devices on a different laptop (or at least did when I checked it a couple days ago).

When I go to the Audio tab under Settings after having just reinstalled Roon, this is what I see:

Needless to say, this is frustrating and any assistance in finding a solution to the issue would be greatly appreciated.

As an aside, you should always name your devices.

To be clear, the Core and the output are the same device or are they two different PCs?

Softwares running on a Core can cause this symptom.

  1. Reaktek drivers

Verify that you have the latest version installed from Realtek

  1. PlayON Virtual Device try removing it

See this thread: Roon losing device drivers - #15 by steve_smith1

  1. Stop Roon. Rename the RaatServer folder to RaatServer_OLD and then restart Roon. This should rebuild the RAATserver device connections. If this works, stop/start Roon again and see if it holds.

My audio devices? The following is taken from my original thread (excluding the Roon Tested device):

Core and output are on the same laptop.

I’ve checked the Realtek driver and it’s up-to-date.

I’ve removed the PlayOn Virtual Device, to no avail.

I have removed \RAATServer on several occasions, also to no avail. \RAATServer Logs has several entries, the last of which reads (with ; the ‘ADDR’ rendered in boldface is proceeded and followed by ‘__’):

03/11 20:12:44 Info: Starting RAATServer v2.0 (build 1223) production on windows
03/11 20:12:44 Info: Local time is 2023-03-11 20:12:44, UTC time is 2023-03-12 03:12:44
03/11 20:12:45 Trace: [bits] myinfo: {“os”:“Windows 10”,“platform”:“windows”,“machineversion”:200001223,“branch”:“production”,“appmodifier”:“”,“appname”:“RAATServer”}
03/11 20:12:45 Warn: [easyhttp] [1] Post https://bits.roonlabs.net/1/q/roon.base.,roon.internet_discovery.,roon.raatserver. web exception without response: The request was aborted: Could not create SSL/TLS secure channel.
03/11 20:12:45 Warn: [bits] http request failed updating bits, status code: 999, message: <>
03/11 20:12:45 Info: [RAATServer] creating RAAT__manager
03/11 20:12:45 Info: [RAATServer] appdata_dir = C:\Users<username>\AppData\Local\RAATServer
03/11 20:12:45 Info: [RAATServer] unique_id = caa5b1e9-7301-4340-a045-64ddedbcd279
03/11 20:12:45 Info: [RAATServer] machine_id = e4648c2d-835b-fad4-1fb1-d648dffc4ecb
03/11 20:12:45 Info: [RAATServer] machine_name =
03/11 20:12:45 Info: [RAATServer] os_version = Windows 10
03/11 20:12:45 Info: [RAATServer] vendor =
03/11 20:12:45 Info: [RAATServer] model =
03/11 20:12:45 Info: [RAATServer] service_id = d7634b85-8190-470f-aa51-6cb5538dc1b9
03/11 20:12:45 Info: [RAATServer] is_dev = False
03/11 20:12:45 Trace: [raatmanager] starting
03/11 20:12:45 Trace: [raatmanager/windows] FOUND type=wasapi id={0.0.0.00000000}.{47e54c9e-aa23-44f2-89ed-a3d1f2df9ba9} usb_id=
03/11 20:12:45 Trace: [raatmanager/windows] name=Realtek(R) Audio output_name=Speakers
03/11 20:12:45 Trace: [raatmanager/windows] FOUND type=wasapi id={0.0.0.00000000}.{e0b643f5-5980-4c40-86a1-43f3f11599d2} usb_id=
03/11 20:12:45 Trace: [raatmanager/windows] name=Intel(R) Display Audio output_name=DENON-AVR
03/11 20:12:45 Trace: [raatmanager/windows] FOUND type=wasapi id={0.0.0.00000000}.{ff185a3b-e96b-4191-abac-3d48757b4951} usb_id=
03/11 20:12:45 Trace: [raatmanager/windows] name=Denon AVR-X3400H Stereo output_name=Speakers
03/11 20:12:45 Trace: [raatmanager/windows] FOUND type=asio id={232685C6-6548-49D8-846D-4141A3EF7560} usb_id=
03/11 20:12:45 Trace: [raatmanager/windows] name=ASIO4ALL v2 output_name=
03/11 20:12:45 Trace: [raatmanager/windows] FOUND type=asio id={A80362FF-CE76-4DD9-874A-704C57BF0D6A} usb_id=
03/11 20:12:45 Trace: [raatmanager/windows] name=Realtek ASIO output_name=
03/11 20:12:45 Trace: [raatmanager] initialized
03/11 20:12:45 Warn: [raatmanager] update_bits, json string: {}
03/11 20:12:45 Info: [RAATServer] running RAAT__manager
03/11 20:12:45 Trace: [raatmanager] starting discovery
03/11 20:12:45 Trace: [discovery] starting
03/11 20:12:45 Info: [discovery] [iface:Local Area Connection:100.127.255.253] multicast recv socket is bound to 192.168.1.66:9003
03/11 20:12:45 Info: [discovery] [iface:Local Area Connection:100.127.255.253] multicast send socket is bound to 192.168.1.66:51067
03/11 20:12:45 Info: [discovery] [iface:Ethernet:192.168.1.66] multicast recv socket is bound to 192.168.1.66:9003
03/11 20:12:45 Info: [discovery] [iface:Ethernet:192.168.1.66] multicast send socket is bound to 192.168.1.66:51068
03/11 20:12:45 Info: [discovery] [iface:Loopback Pseudo-Interface 1:127.0.0.1] multicast recv socket is bound to 192.168.1.66:9003
03/11 20:12:45 Info: [discovery] [iface:Loopback Pseudo-Interface 1:127.0.0.1] multicast send socket is bound to 192.168.1.66:51069
03/11 20:12:45 Info: [discovery] unicast socket is bound to 192.168.1.66:9003
03/11 20:12:45 Trace: [raatmanager] starting server
03/11 20:12:45 Info: [jsonserver] listening on port 9200
03/11 20:12:45 Trace: [raatmanager] announcing
03/11 20:12:45 Warn: [discovery] got send failure: address not available
03/11 20:12:45 Warn: [discovery] got send failure: address not available
03/11 20:12:45 Warn: [discovery] got send failure: address not available
03/11 20:12:45 Warn: [discovery] got send failure: address not available
03/11 20:12:45 Debug: [discovery] broadcast op is complete
03/11 20:12:46 Trace: [inetdiscovery] added device raatserver/caa5b1e9-7301-4340-a045-64ddedbcd279 in addr:ADDR
03/11 20:12:46 Trace: [inetdiscovery] added service com.roonlabs.raatserver.tcp for device raatserver/caa5b1e9-7301-4340-a045-64ddedbcd279
03/11 20:12:51 Trace: [ipaddresses] enumerating addresses
03/11 20:12:51 Trace: [ipaddresses] SKIPPED Local Area Connection 2: not up
03/11 20:12:51 Trace: [ipaddresses] FOUND Local Area Connection 100.127.255.253
03/11 20:12:51 Trace: [ipaddresses] FOUND Ethernet 192.168.1.66
03/11 20:12:51 Trace: [ipaddresses] SKIPPED Wi-Fi: not up
03/11 20:12:51 Trace: [ipaddresses] SKIPPED Local Area Connection* 1: not up
03/11 20:12:51 Trace: [ipaddresses] SKIPPED Local Area Connection* 2: not up
03/11 20:12:51 Trace: [ipaddresses] SKIPPED Bluetooth Network Connection: not up
03/11 20:12:51 Trace: [ipaddresses] FOUND Loopback Pseudo-Interface 1 127.0.0.1
03/11 20:12:51 Warn: [easyhttp] [2] Post https://discovery.roonlabs.net/1/register web exception without response: The request was aborted: Could not create SSL/TLS secure channel.
03/11 20:12:51 Warn: [inetdiscovery] failed to register: Result[Status=NetworkError]

I’m not entirely sure how to parse that, but suspect the reason RAATServer.exe doesn’t launch can be found there.

As per earlier postings (https://community.roonlabs.com/t/roon-2-build-1223-can-t-find-audio-devices/236048 and https://community.roonlabs.com/t/roon-2-build-1223-can-t-find-audio-devices-redux/236735), Roon remains unable to find audio devices other than the default AirPlay device on my main laptop.

It does find other devices, including ASIO, my preferred device, on a secondary laptop, which to some extent renders this question a bit moot, as I can stream audio to my AVR using a combination of Roon on my secondary laptop and Roon Remote on my mobile, but I would ideally like to be able to stream audio from my primary laptop.

At the very least, I’d like to be able to troubleshoot the problem to figure out what has gone awry.

As ever, any and all input is appreciated.

I’ve moved your last post into the existing open support thread. Let’s keep everything together, please.

Hi @Brian_Heinrich ,

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.

Hi, @noris:

Thank you for your response.

After what seems like far too much time trying to troubleshoot the issue, by process of elimination, I seem to have narrowed it down to . . . my VPN (Bitdefender)?!

What’s weird about this is that I already had split tunnelling set up so Roon.exe and RAATServer.exe by-passed the VPN and Bitdefender’s firewall indicated that both EXEs were able pass through.

I’ve not tried to see if the issue is specific to Bitdefender VPN by trying to see what happens if I use a different VPN (e.g., OpenVPN). I may try to troubleshoot this further over the next few days, but for the time being I’m just happy to be to stream music in my preferred fashion.

I hope my experience – and the solution – proves to be of benefit to others.

Pros’t!

1 Like

I have confirmed that Roon works as expected with OpenVPN using TCPv4, but have not attempted to see which protocols supported by Bitdefender VPN might work.

1 Like

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