Roon needing to be launched more than once after upgrade to Tahoe

For me multiple taps in rapid succession seems to work. However, that may be due to how my hardware seems to work. As an aside, I keep my Bluetooth trackpad and keyboard wired into USB slots.

1 Like

To Roon dev-team: look into gatekeeper and quarantine flags.

If the app (or one of its bundled helpers) has the com.apple.quarantine xattr set - especially when copied from a browser download, a network share, or an MDM -it may be blocked unpredictably. Roon ships helper tools (e.g., RAATServer); if any helper keeps a quarantine flag while the main app doesn’t, launches can be inconsistent.

Hope it helps
Regards
Stefan

2 Likes

Same same!

Wasn’t observe the issue when updated Tahoe but from yesterday started to see the Roon app hasn’t started first time.
I have latest updated version on MacAir M2. The Roon used only to remote RoonOnNAS so I haven’t observe missed zones or audio devices.

1 Like

I am having exactly the same issue with Rion client!

2 Likes

Same here! Starts only after 2-4 tries

2 Likes

Same issue here. My MacStudio also runs Roon Server. Not sure if related.

1 Like

experiencing the exact same thing with a Gustard U18

1 Like

Same here. M4 MacMini

1 Like

Same here.

Getting the issue (immediate crash on launch, will not crash on launch after a bunch of tries) as well.

FWIW, not having system output enabled in settings - audio seems to makes things better.

1 Like

Same here on Roon needing to be launched more than once after upgrade to Tahoe. Also getting intermittent notification that there is an “error loading page” with a note to “please check your network” and ''reload the page.," even though the network is fine and the page is loading fine.

1 Like

Great, we are close to one month since it cannot be started reliable (sometimes 6 starts are necessary). Using macOS Tahoe 26.0.1 (25A362) on a MacBook Pro 16" M2.

2 Likes

I think a problem with this thread is that this was going on even before Tahoe… It’s something deeper than the version of the operating system going on here.

1 Like

Am I wrong to read this as an indication that a fix is imminent?

2 Likes

I would say yes.

2 Likes

‘failed to initialize audio device’/ ‘roon lost control of audio device’ repeatedly each day since update to tahoe 26
familiar troubleshooting drill. no change in behaviour.
mac mini pro m2 16gb

1 Like

I still have the problem, sometimes it opens properly sometimes it takes 2 times sometimes 4 …it is always different but at least it always ultimately opens…I do hope for a fix soon

1 Like

I’m still experiencing it too. Sometimes it takes half a dozen attempts. Sometimes just one.

Nor can I discern any correlation between cold boot and running for hours.

Roon 2.55 (build 1559) on macOS 26.0.1.

(As @DDPS says, it is not the first time this has happened - although for me not to this degree. In five or more years, I think I have only had it shortly after things have been getting themselves sorted out after an update.)

2 Likes

@DDPS is correct. Roon on macOS has been partially broken since apple changed the network stack focusing on higher security standards in macOS Sequoia. Tahoe has just further exacerbated the issues between macOS and Roon and its desire for interactivity between the Roon Mothership and your Roon Server. Can’t see all the issues being resolved anytime soon, it is now over a year since I first started having issues on release of Sequoia. I did renew last year even though I had issues with losing endpoints after a restart but the further degradation in fundamental compatibility with Tahoe means I will not renew again. Instead I will continue to subscribe to an alternative player which does not suffer these issues and when faced with an integer mode problem with some USB DAC’s on Tahoe’s release, a patch was released in 2 days after reports came in and they had a production release fix in 4 days.

At the end of the day all I want to do is listen to music…..

My recommendation to anyone running Roon on a Mac is to downgrade to Sonoma (macOS 14) if the age of your Mac allows it. Sad but waiting for a fix which in my case started in September 2024 after the release of Sequoia can be an awfully long wait…….