Downloaded a fresh copy of Roon 2.71 from the Roon website and reinstalled.
Verified the application is properly code-signed.
Confirmed the binary is a universal (x86_64 / arm64) build.
Confirmed the Mac is running natively as x86_64.
Renamed the entire ~/Library/RoonServer folder to force Roon to create a brand-new database.
The problem persists even with an empty database.
ps -ax | grep -i roon shows only the Roon and RAATServer processes; RoonServer never remains running.
Additional Information
This Mac mini has been my dedicated Roon Core for quite some time and was working normally before installing Roon 2.71. No hardware or macOS changes were made—only the Roon update.
I can provide the macOS crash report (RoonServer-*.ips) if that would be helpful.
This is a known bug and it is already fixed. Your diagnosis was correct and saved us a lot of time, so no further logs are needed.
Roon 2.71 build 1680 contained a bug that prevented Roon Server from starting on macOS 12 and 13. Macs on macOS 14 and later were unaffected. Your Monterey 12.7.6 Mac mini hit it exactly, illegal instruction and all. We released a hotfix yesterday, 2.71 build 1683:
One important step before you install it. You renamed ~/Library/RoonServer to force a fresh database. Please rename that folder back to RoonServer before launching the new build, otherwise you will start with an empty library. If a new empty RoonServer folder has since been created, move it aside first, then restore your original.
Then download from
and install over the existing copy in Applications.
Once it is up, please confirm under Settings, then About, that you are on build 1683 and that your library is back as it was.