· After update to 2.60 build 1649 on Windows, Roon no longer recognizes my local audio zones (on my PC). Trying to enable these zones (local System Output and my USB connected DAC via WASAPI (Schiit)) just gets stuck on "enabling". No firewall or other changes have been made and these zones have been working for years since. Other zones in the local network still function fine and play music. Truly baffling
Tell us about your home network
· VPNs have been disconnected and turned off. The zone previously worked with VPNs anyways.
I will add that my PC and roon server are on the same network and both wired into my router directly. There are no firewall rules prohibiting connection between them. I can connect to the server just fine and play to other network devices.
I would love to see if an older version of Roon will fix the problem. Can someone point me to a place where I can download an earlier build?
@forgz - Is your Roon Server an earlier build than version 2.60? If so, then your issue is being caused by an incompatibility between Roon clients version 2.60 and earlier versions of Roon Server. See:
Either update your Roon Server to version 2.60 (Production) or, if you are running Early Access builds of Roon Server, wait until Roon Labs release a new Early Access version. Roon Labs had hoped to release a new Early Access version last Friday, but it didn’t get through their QA testing apparently.
We wanted to check in with you since it’s been some time since your last reply, are you still seeing this issue on your end? Is there any change in behavior if you perform a full reboot of the Roon Server? You can try to perform a RAATServer refresh, this can sometimes help.
You can generate a new RAATServer instance on your device by following these instructions, but please be aware that this will reset your Roon Settings -> Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have: