Hello @John_Tullis
Thanks for checking, and that’s a good, specific detail, only “Roon” showing under Local Network with no “Roon Server” entry at all points to the permission never being (re)registered for the server component under this beta.
Before we go further, could you please confirm you’ve completed the rest of the steps from our earlier reply: toggling the Local Network permission for Roon off and back on, fully quitting Roon Server from the menu bar, and rebooting the Mac? You mentioned what you found in System Settings, but not whether you did those remaining steps, so we want to make sure we’re not troubleshooting past something that might already resolve it.
Separately, and worth knowing since you’re already on a beta OS: this general issue (macOS silently dropping or failing to register an app’s Local Network permission after an update) is a known, longstanding bug on Apple’s side, not something Roon can detect or fix from our end, since that permission lives inside Apple’s own privacy framework. We’ve dealt with this exact pattern before and normally the toggle workaround is the only fix. That said, our latest Early Access build (2.71, build 1674) appears to trigger a fresh permission prompt on macOS, which may resolve the missing “Roon Server” entry you’re seeing. If the reboot and toggle steps above don’t fix it, you’re welcome to try that build: EarlyAccess: Roon 2.71 Build 1674 and ARC 1.81 Build 422 are Live!
Please let us know how it goes either way.