Thank you for your message, and sorry to hear Roon Server didn’t come back after the update.
To help us figure out what’s happening, could you please send us the following:
Roon logs: please use the directions found here and send them over to our File Uploader.
Your operating system’s crash report: since this looks like Roon Server may be crashing on startup rather than simply not launching, we’d also like to see what your OS recorded at the time.
If you’re on a Mac, please open Console (Applications > Utilities > Console), select Crash Reports in the sidebar, find the most recent entry mentioning Roon or RoonServer from around when it failed to start, and export or copy that report.
Please include both the Roon logs and the crash report in the same upload, and let us know once it’s done so we can check the server for your files.
· After yesterday's Roon software update, Roon is not able to run or even find my Roon server which is running in this same Mac. I have spent 3 hours cleaning, checking and reloading the app but with no success. Then I saw your notification about the problem on your side. But how/when I will know that you have solved it?
Tell us about your home network
· Roon running on this same Mac (OS Ventura 13.7.8). No Firewall or VPN in use. Have been happy Roon user for long time, probably 10 years already.
Thank you for your message, and sorry to hear Roon Server didn’t come back after the update.
Before we proceed, have you tried clicking on the “Start Roon Server“ button highlighted in blue?
To help us figure out what’s happening, could you please send us the following:
Roon logs: please use the directions found here and send them over to our File Uploader.
Your operating system’s crash report: since this looks like Roon Server may be crashing on startup rather than simply not launching, we’d also like to see what your OS recorded at the time.
If you’re on a Mac, please open Console (Applications > Utilities > Console), select Crash Reports in the sidebar, find the most recent entry mentioning Roon or RoonServer from around when it failed to start, and export or copy that report.
Please include both the Roon logs and the crash report in the same upload, and let us know once it’s done so we can check the server for your files.
Thank you for your message, and sorry to hear Roon Server didn’t come back after the update.
To help us figure out what’s happening, could you please send us the following:
Roon logs: please use the directions found here and send them over to our File Uploader.
Your operating system’s crash report: since this looks like Roon Server may be crashing on startup rather than simply not launching, we’d also like to see what your OS recorded at the time.
If you’re on a Mac, please open Console (Applications > Utilities > Console), select Crash Reports in the sidebar, find the most recent entry mentioning Roon or RoonServer from around when it failed to start, and export or copy that report.
If you’re on Windows, please open Event Viewer, go to Windows Logs > Application, find the most recent Error-level entry mentioning Roon or RoonServer from around when it failed to start, and export that entry (or send a screenshot of it).
Please include both the Roon logs and the crash report in the same upload, and let us know once it’s done so we can check the server for your files.
Thank you for your message, and sorry to hear the Roon Server didn’t come back after the update.
Before moving forward, would you kindly clarify whether you have tried clicking on “Start Roon server on this Mac“?
To help us figure out what’s happening, could you please send us the following:
Roon logs: please use the directions found here and send them over to our File Uploader.
Your operating system’s crash report: since this looks like Roon Server may be crashing on startup rather than simply not launching, we’d also like to see what your OS recorded at the time.
If you’re on a Mac, please open Console (Applications > Utilities > Console), select Crash Reports in the sidebar, find the most recent entry mentioning Roon or RoonServer from around when it failed to start, and export or copy that report.
If you’re on Windows, please open Event Viewer, go to Windows Logs > Application, find the most recent Error-level entry mentioning Roon or RoonServer from around when it failed to start, and export that entry (or send a screenshot of it).
Please include both the Roon logs and the crash report in the same upload, and let us know once it’s done so we can check the server for your files.
Thank you for your message, and sorry to hear the Roon Server didn’t come back after the update.
Before moving forward, would you kindly clarify whether you have tried clicking on “Start Roon server on this Mac“?
To help us figure out what’s happening, could you please send us the following:
Roon logs: please use the directions found here and send them over to our File Uploader.
Your operating system’s crash report: since this looks like Roon Server may be crashing on startup rather than simply not launching, we’d also like to see what your OS recorded at the time.
If you’re on a Mac, please open Console (Applications > Utilities > Console), select Crash Reports in the sidebar, find the most recent entry mentioning Roon or RoonServer from around when it failed to start, and export or copy that report.
If you’re on Windows, please open Event Viewer, go to Windows Logs > Application, find the most recent Error-level entry mentioning Roon or RoonServer from around when it failed to start, and export that entry (or send a screenshot of it).
Please include both the Roon logs and the crash report in the same upload, and let us know once it’s done so we can check the server for your files.
Thank you for your message, and sorry to hear the Roon Server didn’t come back after the update.
Before moving forward, would you kindly clarify whether you have tried clicking on “Start Roon server on this Mac“?
To help us figure out what’s happening, could you please send us the following:
Roon logs: please use the directions found here and send them over to our File Uploader.
Your operating system’s crash report: since this looks like Roon Server may be crashing on startup rather than simply not launching, we’d also like to see what your OS recorded at the time.
If you’re on a Mac, please open Console (Applications > Utilities > Console), select Crash Reports in the sidebar, find the most recent entry mentioning Roon or RoonServer from around when it failed to start, and export or copy that report.
If you’re on Windows, please open Event Viewer, go to Windows Logs > Application, find the most recent Error-level entry mentioning Roon or RoonServer from around when it failed to start, and export that entry (or send a screenshot of it).
Please include both the Roon logs and the crash report in the same upload, and let us know once it’s done so we can check the server for your files.
Thank you for your message, and sorry to hear the Roon Server didn’t come back after the update.
Before moving forward, would you kindly clarify whether you have tried clicking on “Start Roon server on this Mac“?
To help us figure out what’s happening, could you please send us the following:
Roon logs: please use the directions found here and send them over to our File Uploader.
Your operating system’s crash report: since this looks like Roon Server may be crashing on startup rather than simply not launching, we’d also like to see what your OS recorded at the time.
If you’re on a Mac, please open Console (Applications > Utilities > Console), select Crash Reports in the sidebar, find the most recent entry mentioning Roon or RoonServer from around when it failed to start, and export or copy that report.
Please include both the Roon logs and the crash report in the same upload, and let us know once it’s done so we can check the server for your files.
Thanks for the update. We’re currently gathering the useful information for the R&D team, and it would help if you could upload the requested crash report and logs to the uploader link shared in my previous reply.
For Roon connectivity to work properly, both Roon Server and Roon Remote need to be turned on.
· I can't turn on Roon Server, I need help.
Describe the issue
RoonServer crashes immediately on every launch attempt following the update to 2.71 (build 1680). The crash is EXC_BAD_INSTRUCTION (SIGILL), consistently occurring in NSStatusBar _statusItemWithLength:withPriority: → NSCGSStatusItem when RoonServer tries to create its menu bar status item. This is fully reproducible — it has crashed on every single launch attempt (10+ attempts) regardless of:
Fresh reinstall of Roon.app (clean download from roonlabs.com) Screen Recording and Accessibility permissions granted to both com.roon.Roon and com.roon.RoonHeadlessManager Full system reboot (multiple times) Quitting third-party menu bar apps (Hidden Bar) before launch
System details:
Mac: iMac14,3 (2013), Intel Core i7-4770S @ 3.10GHz (Haswell, AVX2/BMI2 present) macOS: Ventura 13.7.8 (build 22H730) RoonServer bundle ID: com.roon.RoonHeadlessManager Last known working version: 2.70 (build 1671) — confirmed working via logs right up until the automatic update to 2.71
Reference: This matches a report from another user on similar Haswell-era hardware (Mac mini 2012, Macmini7,1) posted in your community forum: community.roonlabs.com/t/roonserver-2-71-crashing-on-startup-on-intel-haswell-mac-mini-ref-8fhuvx/323266 — same crash type, same trigger (2.71 update), same architecture generation.
Request: Could you please either (a) provide the 2.70 (build 1671) installer so I can roll back while this is fixed, or (b) let me know if there's already a fix in progress I should wait for? I have multiple full .ips crash reports available and happy to upload logs via Console per your usual process if useful.
Describe your network setup
RoonServer crashes immediately on every launch attempt following the update to 2.71 (build 1680). The crash is EXC_BAD_INSTRUCTION (SIGILL), consistently occurring in NSStatusBar _statusItemWithLength:withPriority: → NSCGSStatusItem when RoonServer tries to create its menu bar status item. This is fully reproducible — it has crashed on every single launch attempt (10+ attempts) regardless of: Fresh reinstall of Roon.app (clean download from roonlabs.com) Screen Recording and Accessibility permissions granted to both com.roon.Roon and com.roon.RoonHeadlessManager Full system reboot (multiple times) Quitting third-party menu bar apps (Hidden Bar) before launch System details: Mac: iMac14,3 (2013), Intel Core i7-4770S @ 3.10GHz (Haswell, AVX2/BMI2 present) macOS: Ventura 13.7.8 (build 22H730) RoonServer bundle ID: com.roon.RoonHeadlessManager Last known working version: 2.70 (build 1671) — confirmed working via logs right up until the automatic update to 2.71 Reference: This matches a report from another user on similar Haswell-era hardware (Mac mini 2012, Macmini7,1) posted in your community forum: community.roonlabs.com/t/roonserver-2-71-crashing-on-startup-on-intel-haswell-mac-mini-ref-8fhuvx/323266 — same crash type, same trigger (2.71 update), same architecture generation. Request: Could you please either (a) provide the 2.70 (build 1671) installer so I can roll back while this is fixed, or (b) let me know if there's already a fix in progress I should wait for? I have multiple full .ips crash reports available and happy to upload logs via Console per your usual process if useful.
Thank you for your message, and sorry to hear Roon Server didn’t come back after the update.
To help us figure out what’s happening, could you please send us the following:
Roon logs: please use the directions found here and send them over to our File Uploader.
Your operating system’s crash report: since this looks like Roon Server may be crashing on startup rather than simply not launching, we’d also like to see what your OS recorded at the time.
If you’re on a Mac, please open Console (Applications > Utilities > Console), select Crash Reports in the sidebar, find the most recent entry mentioning Roon or RoonServer from around when it failed to start, and export or copy that report.
Please include both the Roon logs and the crash report in the same upload, and let us know once it’s done so we can check the server for your files.
Thank you for your message, and sorry to hear Roon Server didn’t come back after the update.
To help us figure out what’s happening, could you please send us the following:
Roon logs: please use the directions found here and send them over to our File Uploader.
Your operating system’s crash report: since this looks like Roon Server may be crashing on startup rather than simply not launching, we’d also like to see what your OS recorded at the time.
If you’re on a Mac, please open Console (Applications > Utilities > Console), select Crash Reports in the sidebar, find the most recent entry mentioning Roon or RoonServer from around when it failed to start, and export or copy that report.
Please include both the Roon logs and the crash report in the same upload, and let us know once it’s done so we can check the server for your files.
· I'm have RoonServer on a 2012 MacMini which has been Opencore patched to run Monterey. Since the latest update RoonServer is not running.
The Roon app says "waiting for your Roon Server" with the option to "Start Roon Server" When I click on Start Roon Server it thinks for a while and then takes me back to the "waiting for your Roon Server" screen
my Roon Server does not start anymore after installing the 2.71 Update. I'm running my Roon Server on an Intel MacMini. In the process monitor I can verify that the Roon Server Process is not running / starting.
Please provide a fix. I cannot use Roon at all since yesterday.
Tell us about your home network
· Very stable 5Ghz WiFi network running via FRITZ!Box 6660 Cable. No extenders.
Hi Vadim, Yes, I tried multiple times to “start roon server on this Mac” before I ever submitted a support ticket. I have uploaded both the roon log and the crash report. For your reference, my iMac model is Retina 4K, 21.5-inch, Late 2015 with the 3.1 GHz quad-core Intel Core i%. I am running macOS Monterey 12.7.6.
