Roon Core Crashes on Windows 11

Support
1

Roon Core Machine

Core i7-4790K
32GB Ram
Windows 11 Pro 10.0.22000 Build 22000

Networking Gear & Setup Details

Wired connection to a Ubiquiti Dream Machine. All devices on one subnet (192.168.1.xxx)

Connected Audio Devices

Attempting to stream to a Trinnov Alititude 16 but the issue occurs regardless of audio device selected

Number of Tracks in Library

29,000 tracks

Description of Issue

When I launch Roon Core on either of my windows 11 machines the app loads and then, after a couple of minutes, crashes.

The log file from a clean start is below. It’s clearly something to do with TLS supported versions. I’ve been in to edge and enabled all TLS versions, is there another fix?

12/03 16:35:40 Info: Starting RAATServer v1.8 (build 831) stable on windows
12/03 16:35:40 Warn: [easyhttp] [1] Post https://bits.roonlabs.net/1/q/roon.base.,roon.internet_discovery. web exception without response: The request was aborted: Could not create SSL/TLS secure channel. 
12/03 16:35:40 Warn: [bits] http request failed updating bits, status code: 999, message: <<NULL>>
12/03 16:35:40 Info: [RAATServer] creating RAAT__manager
12/03 16:35:40 Info: [RAATServer]     appdata_dir  = C:\Users\conra\AppData\Local\RAATServer
12/03 16:35:40 Info: [RAATServer]     unique_id    = e145fdcc-e654-41c5-8133-0cd79d2eff04
12/03 16:35:40 Info: [RAATServer]     machine_id   = 2fe5de39-45d1-cc9f-6dad-9fe7ab4cb6a9
12/03 16:35:40 Info: [RAATServer]     machine_name = BEAST
12/03 16:35:40 Info: [RAATServer]     os_version   = Windows 10
12/03 16:35:40 Info: [RAATServer]     vendor       = 
12/03 16:35:40 Info: [RAATServer]     model        = 
12/03 16:35:40 Info: [RAATServer]     service_id   = d7634b85-8190-470f-aa51-6cb5538dc1b9
12/03 16:35:40 Info: [RAATServer]     is_dev       = False
12/03 16:35:40 Trace: [raatmanager] starting
12/03 16:35:40 Trace: [raatmanager] [System Output] loaded config from C:\Users\conra\AppData\Local\RAATServer\Settings\device_9b961fc2035f3dd343e04f8f136e7682.json
12/03 16:35:40 Trace: [raatmanager/windows] FOUND type=wasapi id={0.0.0.00000000}.{97c468b3-9d6a-43b2-bfb7-b1c6af58e15a} usb_id=
12/03 16:35:40 Trace: [raatmanager/windows]       name=High Definition Audio Device   output_name=Digital Audio (S/PDIF)        
12/03 16:35:41 Trace: [raatmanager/windows] FOUND type=asio   id={C89A373F-2880-410E-B6BA-2E15796C5950} usb_id=
12/03 16:35:41 Trace: [raatmanager/windows]       name=DJM-750MK2 ASIO                output_name=                              
12/03 16:35:41 Trace: [raatmanager/windows] FOUND type=asio   id={462F2ABF-5278-436A-95B6-72CBF65482AE} usb_id=
12/03 16:35:41 Trace: [raatmanager/windows]       name=FlexASIO                       output_name=                              
12/03 16:35:41 Trace: [raatmanager/windows] FOUND type=asio   id={FBD8E51C-6638-4867-A3C9-D0C099CC51E0} usb_id=
12/03 16:35:41 Trace: [raatmanager/windows]       name=JRiver Media Center 27         output_name=                              
12/03 16:35:41 Trace: [raatmanager/windows] FOUND type=asio   id={FD9BFA25-27CB-4AA9-9A0C-7104787E5EF3} usb_id=
12/03 16:35:41 Trace: [raatmanager/windows]       name=Pioneer CDJXDJ ASIO            output_name=                              
12/03 16:35:41 Trace: [raatmanager] initialized
12/03 16:35:41 Info: [RAATServer] running RAAT__manager
12/03 16:35:41 Trace: [raatmanager] starting discovery
12/03 16:35:41 Trace: [discovery] starting
12/03 16:35:41 Info: [discovery] [iface:Ethernet:192.168.1.180] multicast recv socket is bound to 0.0.0.0:9003
12/03 16:35:41 Info: [discovery] [iface:Ethernet:192.168.1.180] multicast send socket is bound to 0.0.0.0:63654
12/03 16:35:41 Info: [discovery] [iface:Loopback Pseudo-Interface 1:127.0.0.1] multicast recv socket is bound to 0.0.0.0:9003
12/03 16:35:41 Info: [discovery] [iface:Loopback Pseudo-Interface 1:127.0.0.1] multicast send socket is bound to 0.0.0.0:63655
12/03 16:35:41 Info: [discovery] unicast socket is bound to 0.0.0.0:9003
12/03 16:35:41 Trace: [raatmanager] starting server
12/03 16:35:41 Info: [jsonserver] listening on port 9200
12/03 16:35:41 Trace: [raatmanager] announcing
12/03 16:35:41 Debug: [discovery] broadcast op is complete
12/03 16:35:41 Trace: [inetdiscovery] added device raatserver/e145fdcc-e654-41c5-8133-0cd79d2eff04 in addr:__ADDR__
12/03 16:35:41 Trace: [inetdiscovery] added service com.roonlabs.raatserver.tcp for device raatserver/e145fdcc-e654-41c5-8133-0cd79d2eff04
12/03 16:35:46 Trace: [ipaddresses] enumerating addresses
12/03 16:35:46 Trace: [ipaddresses]    FOUND   Ethernet 192.168.1.180
12/03 16:35:46 Trace: [ipaddresses]    SKIPPED Local Area Connection: not up
12/03 16:35:46 Trace: [ipaddresses]    SKIPPED Local Area Connection 2: not up
12/03 16:35:46 Trace: [ipaddresses]    FOUND   Loopback Pseudo-Interface 1 127.0.0.1
12/03 16:35:47 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. 
12/03 16:35:47 Warn: [inetdiscovery] failed to register: Result[Status=NetworkError]
12/03 16:35:51 Trace: [RAATServer] refreshing @ 10s
12/03 16:35:51 Trace: [raatmanager] announcing
12/03 16:35:52 Debug: [discovery] broadcast op is complete
12/03 16:35:53 Trace: [jsonserver] [127.0.0.1:62822] accepted connection
12/03 16:35:53 Trace: [jsonserver] [127.0.0.1:62822] GOT[LL] [1] {"request":"enumerate_devices","subscription_id":"0"}
12/03 16:35:53 Trace: [jsonserver] [127.0.0.1:62822] SENT [1] [nonfinal] {"status": "Success", "devices": [{"device_id": "default", "type": "wasapi", "config": {"unique_id": "a3dd5022-7e84-1670-a0db-830816a1a26c", "output": {"type": "wasapi", "device": "default", "name": "Syst
12/03 16:41:10 Trace: [jsonserver] [127.0.0.1:62822] read error: connection reset by peer
12/03 16:41:10 Trace: [jsonserver] [127.0.0.1:62822] destroying client

Any help would be appreciated.

I should also add that not running anything specific in terms of firewalls, just windows defender. I’ve tried turning that off and the issue persists.

2

Hey @Conrad_Nash,

Thanks for getting in touch to let us know of the behavior you’re experiencing. We’re so sorry about the trouble… :pensive:

I couldn’t help but notice that you said:

When I launch Roon Core on either of my windows 11 machines

Does the crashing happen on two different Windows 11 machines? Do you use one as a Core and one as a remote? Are you running the Roon Software or RoonServer (running Roon headless)?

What TLS version are your machines running?

3

Hi, thanks for getting back to me.

When the issue presented on the first machine, I installed Core on a second machine to see if it was machine specific. Both machines are running core, but never at the same time. They both read from the same source. They’re both windows 11 machines. I can get the version of the second machine if that will help.

They both crash in the same way.

I went into the internet security options of edge and enabled all TLS options, so all are checked. Is there a different place that Roon needs TLS enabling?

4

Hey @beka, any update on this? Anything else I can try?

5

I don’t have the same symptoms as you, but I found the same TLS warning message in the RAAT log on my Windows11 machine: Remote audio devices not discovered
I’d like to hear about other Windows11 users, if they have the same warning message but a fully functioning Roon system

6

I’ve just upgraded to Windows 11 and Roon won’t play on my PC / Roon Core - when I try to play through the system output Roon simply shuts down. It was able to play on my Cambridge CXN though so the network seems to function but I’m not able to play direct on the Core.
Any suggestions?

7

Hey @Conrad_Nash,

I want to apologize for only replying today — I just returned to the office after the holidays.

I was wondering if two weeks later you are seeing the same crashes you did before? What TLS version is active on your Windows machine?

8

Hey @Paul_Evans,

Before diving into troubleshooting, I wanted to check in with you and see if Roon is still shutting down for you?

9

Hi Rebeka,

Happy New Year. I thought you would be closed for the holidays which is why I didn’t chase.
I installed the update and now Roon seems to behave itself. I’m still seeing the same error in the logs, but it’s not shutting down now. I think this ticket can be closed.

Thanks

1 Like
10

Hi Rebeka, thanks for getting in touch. I was still having the problem, but with the help of the fabulous Ashley in your support team we seem to have just this minute resolved it. It seems the update had changed the default output to 5.1 rather than stereo - all working again now.

1 Like
11

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