I would expect your endpoints to disappear after a reboot of your iMac. after toggling off and on Roon access in system settings/privacy&security/local network, then just close Roon server and reopen it to force a refresh of your devices. They should then reappear. After a reboot of my mac I nearly always lose access to endpoints, once I have “done the toggle” and closed and reopen Roon the endpoints are normally restored until I next reboot the Mac when the issue will reoccur.
Another of the frustrating issues in macOS Sequoia. Again it is an issue some users of USB devices are experiencing (see link). Only thing I would try is if you are connecting via a dock, try a direct connection (and vice versa if you have a dock but are connecting it direct). Also try the other ports on your mac. Also try with another disk if you have one and try with different partition formats. For info macOS and USB bugs are not uncommon, I use Thunderbolt disks with my mac and have managed to avoid these frustrations which occurred also with Ventura on first release.
I know, Sequoia is not Apple’s finest hour. They are playing catch up on AI and are rushing new features without sufficient QA/QC. Unfortunately the end point disappearing issue due to a bug in the “Local network” new feature is not fixed in macOS 15.1 which should be released by Apple later today, I am running the release candidate 2 for 15.1 and the bug is still there. USB issues drove me (quite a few macOS versions ago, after Big Sur) to adopt an all Thunderbolt SSD/HD regime.
Thats correct, I use Audirvana Studio on my main machine. I only run Roon on a 2nd machine dedicated for part time testing/restore use. Audirvana has the same issues with Sequoia denying access to local network devices after startup. They issued an update which checks for local network access to devices and prompts the user to toggle off and on the local network entry for Audirvana, which when refreshing the network devices by using the toggle, or by restarting Audirvana restores devices.
I must admit to thinking about getting a windows machine either Core Ultra 2 or a Qualcomm Snap Dragon elite but with Microsofts history on updates occasionally bricking devices then I think better the devil I know rather than learning a new devil! I stopped using windows for work and play in 1999 and have used Mac’s ever since.
No, not experienced a crash, just endpoints disappearing when macOS decides to deny access to local network devices. But then again I don’t push Roon with multiroom, just play to one endpoint at a time, and my library is all local and is only 10k tracks, I only use Qobuz for discovery.
As stated, I still have the issue in the 15.1 release candidate 2 which, if Apple releases 15.1 today to the general public as rumoured will be the same software build (24B83), they seldom change the build from the final release candidate issued to testers so don’t get your hopes too high!
There is an old adage that you should not update macOS to a new version until it has reached the X.4 or X.5 iteration. This is extremely good advice, however a piece of advice I fail to heed every year and have several times over the years paid the penalty of increased frustration and angst.
It will, but with the focus on an incremental roll out of Apple Intelligence features in 15.1 to 15.4 it may take a little longer than usual…
That’s good news! Lets hope they get round to the network issue in the next point release 
Hey @David_Moore2,
Thanks so much for sharing your report - as you’ve likely noticed, I’ve separated your responses into their own thread for proper tracking and diagnosis.
For future issues, please create your own thread and post initially. Thanks for your understanding here!
Can you please navigate to macOS System Settings > Privacy & Security > Local Network , and make sure Roon is allowed? If it is already enabled, toggle it off and on again. Then reboot your Mac, and see if the same issue persists.
We’ll be on standby for your reply! 
1 Like
No worries, I stumbled on the temprary resolution for the “local network issue” since the release candidate of Sequoia in mid September and have been using it ever since. In my case it is only after startup of my Mac. Not a big issue for me. Hopefully it will be resolved by Apple soon.
2 Likes
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.