Intermittent audio device recognition in Windows 11 (ref#X6WP85)

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?

· No, it does not show up there

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?

· Worked just now at 11.27am (local time); didn't work on my previous login, maybe fifteen minutes ago

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

· Topping DX3 Pro DAC USB-C

Describe the issue

Windows 11 audio devices appearing only intermittently. Sometimes they work. Often they don't. When they appear, they sit in "enabling" for a long time. Then they disappear. Sometimes they reappear when I open the program. Sometimes not. What an adventure.

Describe your network setup

Wifi on Windows 11 laptop; ethernet and wifi connection on server PC, connected to Google Home mesh

Hello @bjg
Thank you for reaching Roon support.

I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.

However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.

First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.

1 Like

Hi @bjg,

Thank you for your patience. We’ve examined diagnostic logs that reached our servers from your RoonServer instance. We don’t see any obvious dropouts or sample loss, but we do see socket disposal errors with networked endpoints across RAAT and Airplay.

Are the Zones to which you’re trying to connect using WiFi?

Roon is trying to communicate with the networked Zones through network sockets that have already been closed. This usually means the router is reassigning devices between mesh nodes or WiFi bands (2.4GHz vs 5.0GHz) in an effort to optimize throughput and bandwidth.

Try disabling “Fast Roaming” and “Band Steering” in the Google Mesh settings.

If you’re having issues with the System Output disappearing, then please ensure RAATServer.exe is safelisted in the Windows Defender firewall.

We’ll watch for a response. Thank you!

1 Like

This thread is now closing due to lack of response/inactivity. If you require further assistance, please reach out in a new technical support request and the team will promptly respond. Thank you!

Please also visit these references: