· None of the above quite fits
· None of these quite match
· roon doesnt recognize audio devices everyday i have to restart my pc multiple times so i gets recognized
· its not a vpn or internet problem
If you’re not using the Realtek interfaces with the PC, try uninstalling the Realtek drivers as these can cause issues with Roon.
Hi @victor_cardenas,
Please additionally double-check that you’ve safelisted RAATServer.exe in the Microsoft Defender firewall or any other network security you have installed.
Which Zones in particular fail to appear on startup? Do you have any issues with network devices?
We’ll watch for your reply.
Raatserver was already on safelist, i just use roon with my dacs topping dx1 or hiby or fiio products, and its connected through usb c to usb c, sometimes it recognize it and other times it doesnt no matter what i do, the only thing that work is rebooting my pc until it does, ill try to uninstall realtek drivers, but i use some cheap speakers when i dont want to listen music, i dont use roon with them.
ok i uninstalled realtek drivers, reset computer and it was working, but after another cicle of turn off and turn on the pc again is not recognizing my topping dx1 ii dac , both wasapi and asio topping are stuck in enabling.
Hi @victor_cardenas,
Thanks for trying the Realtek uninstall. The fact that both WASAPI and ASIO show “enabling” points to another application grabbing the Topping DX1 II in exclusive mode before Roon gets to it.
A few things to check:
Yeah tried all of those options and more guises by an ai since the responses here are so slow days even I’m not able to use roon, the only thing that got it almost working is the second suggestion to uncheck that option but still i have to close and open roon múltiple times so it recognize the dacs , the problem is something about raat or networking issue since i use Tailscale, but i tried without Tailscale and sometimes roon recognized the dacs on my pc and sometimes only the server outputs.
like i said ive uninstalled every app or driver that involves audio and still got the same problem, i reinstalled everything incluing realtek and now sometimes work.
Already checked all firewall and windows defender solutions and nothing.
It’s so annoying to restart the pc everytime or close and reopen roon múltiple times so I Can get it working,
I payed this app to not have problems or search for solution for my music system but so far is being a terrible decision, and I can’t even find where to apply for a refund or partial refund since i made the mistake of buying a year …
Hi @victor_cardenas,
I am sorry that these steps haven’t resolved the issue and that you’re feeling frustrated with the experience. It is clear that the intermittent nature of this detection issue - specifically with the Topping DAC - points to something deeper than simple driver conflicts or “exclusive mode” settings.
Since you mentioned that you are using Tailscale, it is possible that there is a network interface conflict occurring during startup where Roon’s RAAT (the protocol that handles audio device communication) is trying to bind to the virtual Tailscale adapter instead of your local hardware.
To move this forward, we would like to look at the exact moment this happens:
Please let us know how you would like to proceed and provide the timestamp if you are willing to give us one more opportunity to identify the source of the conflict.
It’s something to do with Tailscale and raat from roon, I had to buy a Ethernet cable and connect that way to my pc outside of Tailscale and that way roon recognize all my dacs, but doing this my other devices don’t see those dacs because no Tailscale is being use and defeats the purpose of having roon at all. I recently acquire a fiio dap roon ready and is not getting recognized but this time I don’t want to even bother finding a solution , i shouldn’t have to fix this kind of problems that’s the reason roon exist to avoid this problems. I would like a refund please .
It looks like Windows is routing DNS through Tailscale rather than the local machine, which is preventing discovery.
What are the subsets for the Windows machine and Tailscale? You may want to try disabling (uncheck) Use Tailscale subnets.
If you don’t use Roon ARC you don’t need Tailscale.
Hey @victor_cardenas,
Thanks for all the additional information! We can certainly ping the Accounts team to get the right people in touch to discuss account requests.
In the meantime though, I did want to mention some important findings from a recent Roon Server diagnostic report :
The machine is heavily multi-homed. On every boot, the Roon Server (running on DESKTOP-JFV06SQ) enumerates and binds SOOD (Roon’s discovery protocol) to a large, shifting set of IP addresses on different subnets, e.g.:
Adding User IP 169.254.83.107 ← Tailscale, but APIPA/link-local (Tailscale NOT up yet)
Adding User IP 172.19.128.1 ← Hyper-V vEthernet (Default Switch)
Adding User IP 192.168.15.4 ← your real LAN
Adding User IP 100.68.58.34 ← Tailscale CGNAT
Adding User IP 10.5.0.2 ← another VPN/virtual subnet
Adding User IP 192.168.31.184 ← a *different* LAN subnetRoon is being asked to do device discovery across six-plus interfaces including virtual ones, and it doesn’t reliably know which one your DACs and endpoints live on.
The root cause is interface/discovery contention from the VPN + virtualization stack, with a Tailscale-not-ready-at-boot race.
With this, I think the following next steps will likely resolve you of your issues:
100.x address. Set RoonServer service to Automatic (Delayed Start) in services.msc. This alone should stop "restart until it works."
vEthernet (Default Switch) and the extra 10.5.0.2 / 192.168.31.x adapters aren't needed, disable them, every extra "up" interface is one more place SOOD wastes its discovery window.
192.168.15.x and 192.168.31.x suggest two routers / a double-NAT or mesh setup. RAAT needs everything on one flat subnet.
Hi, i need to use Tailscale because my isp handles only public dns so roon arc doesn’t work without it, i need to leave the roon arc port at 0 , i use roon arc on my iPhone and android, i tried on my fiio m33 but it doesn’t work bit perfect there, so I try the other way with fiio roon and it doesn’t discover my device i stopped investigating more about it because frankly im quite tired of trying to find information about it.
I have to use 2 routers in my home and they have few ports 2.5gbps so I prioritize my main pcs , I have 2.5gbps internet speeds and not changing to 1gbps ports just to use roon.
When I was trying to fix it the llm guide me to do all the things possible because I don’t know how to do it all but I remember trying to fix the start of Tailscale delaying it , I think I killed raat and then proceed to open roon with no luck , sometimes stopping raat and reopening roon in administrator or normal mode worked but it was not consistent.
I just want to hear my music without hassle and problems.
Right now i had to prioritize only my main device and connected the server and my main pc to the same router to use roon, but had to disconnect my other devices.
And just to add to my rant I had to sell my new dac Hiby fc5 which was working great with everything but roon arc the audio got distorted when I was trying to play in bit perfect mode on my android.
i would like you to start the refund please im done trying to fix things.
Unfortunately, an LLM is unreliable, and can easily break things when used to diagnose technical problems.
Currently, your Roon experience is poor because your network is broken and deviates significantly from a standard supported setup which uses a single subnet and either port forwarding or Tailscale for ARC. Remote Roon client’s whilst possible, are not supported.
Typically, users with complex networking requirements post in Tinkering and rely on experienced community members and networking specialists rather than an LLM.
I believe you have a choice. Either simplify your networking so Roon may work as intended by following the steps in @benjamin’s post. Or, this thread is closed, and you seek community support in Tinkering.
Hello @victor_cardenas,
We completely understand your frustration, and we are sorry the experience has been this difficult.
Regarding the refund request, I have flagged this for our @accounts team, and someone will be in touch with you directly to assist.
Well the account team refused a full refund, I asked for a partial refund they refused it, and sent me a generic networking guide.
I do not advise to get roon to anyone that thinks these will solve or make an easier connection between his devices, technical support is based on forums with answers that take days and a account team that refuses any kind of refund, you are on your own.
And don’t make my mistake of buying a year in advanced because they won’t give you a full or partial refund under any circumstance.
I leave this completely disappointed with roon because social media says it’s good but paying a subscription with this lack of support and a lot of problems that the client has to resolve on his own is just not worth it.
Hey @victor_cardenas,
I want to step back from the troubleshooting for a moment and just say: I hear you. You bought Roon to enjoy your music without friction, and instead you’ve spent weeks fighting your setup, selling off a DAC, rearranging your hardware, and still not landing somewhere that feels good. That’s genuinely frustrating, and I’m sorry the experience has cost you this much time and goodwill.
I also want to be honest with you, because I think you deserve straight talk rather than another wall of steps. The detection problems you’re seeing aren’t really Roon misbehaving on its own, they trace back to how your network is built. RAAT (the protocol that streams audio to your DACs) is designed to find devices on a single, flat local network. Your setup has Tailscale, two routers on different subnets, and some virtual adapters all active at once, and on every boot Roon has to guess which of those many interfaces your DACs actually live on. That guessing is what produces the “have to restart until it works” behavior. It’s a real constraint of how RAAT was designed, not a sign you did anything wrong, your network is just more complex than the setup Roon is built around.
If you’d ever want to give it one more try, the single highest-impact change would be getting your Roon Server and your DACs onto one router / one subnet, with Tailscale reserved only for ARC (remote listening) rather than for local playback. That alone resolves the large majority of cases like yours. I’m happy to walk it through with you at whatever pace works, no pressure.
Whatever you decide, I’m sorry it played out this way, and I do wish you good listening ahead, with Roon or without it.