I’m doing some testing of MacOS Sonoma on one of my systems. After updating to Beta 4, and then again to Beta 5, I’m getting some weird errors from one particular file stored deep in the core system folder "System Events.app. When rebooting, this terminal app goes into an infinite loop and generates errors until I finally kill the task. When I look at the specific file, it looks like a harmless, and basically useless script, but backtracking through all of the log files generated and inspecting them using the Console App suggests that this file is somehow associated with Roon, and further with a Microsoft 32 bit dll. I’ve prevented the file from opening at login and it seems to have no effect on Roon, and so far with nothing else that I can see. I just installed the early access of Roon to see what happens. It also works, but I haven’t had a chance to reboot to see if the problem reoccurs. Up to this point, whenever I’ve rebooted, despite telling “Login Items” not to load this particular item, it persists on loading until I kill it. This does not occur in Ventura (13.5), and at this point I’m not 100% certain that Roon is the culprit.
Dump a lot more info, and maybe we can help… Note that most (but not all) beta MacOS versions usually break Roon. Apple usually resolves these issues before a release with zero work from us. We tend to look at the beta’s quite late in the process as to not waste effort chasing Apple’s incompatibilities.
Catalina was a significant exception to this because they added a new security model for accessing folders.
I don’t have any evidence that Roon is, in fact, broken. My question was primarily an inquiry about whether or not Roon uses Microsoft 32 bit dlls for its Mac version. That’s where the trace leads. I’m happy to send whatever information you need.
I’m not sure the problem is really Roon. I uninstalled it, but the problem persists. I’m sure there is detritus left behind after an uninstall, but the various logs lead off in a different direction. I reinstalled it with no difficulty. For now, I’m not going to perseverate about it. It isn’t a priority, and it isn’t my main system.