Upon upgrading to B1228, I first got the issue where the app wouldn’t start. I re-installed the early access installer as suggested in those threads. However, upon doing that I still don’t have any local audio devices to select, or even enable in the Audio view. I do have my Sonos speakers visible though.
I’m not completely sure if RAATServer is involved, but when launching RAATServer.exe directly, I get this error in the command line if it helps. Upon closer inspection it’s because the Roon client app was running, so maybe I just don’t need to do this:
I’m just shooting from the hip here, but the last couple few updates in esrly access in Windows I had a popup occur to allow Roon firewall access. Just for laughs maybe check Windows firewall settings and make sure Roon is properly configured?
For anyone who is having the same issue, this is what I did.
In Windows, search for “Windows Firewall” and select “Windows Defender Firewall with Advanced Security”
Select “Inbound Rules” in the left panel
Find “raatserver.exe” and “roon.exe” entries. If any of them have a red stop/cancel symbol next to them, double click those entries, then at the bottom change from “Block the connection” to “Allow the connection” and click OK. It should change to a green check symbol.
As soon as I did this for raatserver.exe my output immediately showed up in Roon, and I can play music again!
Would be nice if there was a way for the Roon app to be able to alert/troubleshoot this on my behalf. But glad it’s something that is relatively straight forward to resolve.