· I keep getting the message "There was an error checking for an update" on my MackBook (endpoint). My core (Mac Mini M2) updates without a problem but my two MacBooks - one running Sonoma and the other Tahoe won't update. I quit Roon and reopened it. I deleted Roon and reinstalled Roon. I restarted the MacBooks after reopening and restarting. I temporarily deactivated the firewall. Is there anything else I can try. Thanks Bill
Tell us about your home network
· My Mac Mini, and Node 2i are ethernet connected to my TP-Link AX55. No VPN. I have a Netgear switch but no extenders.
Thanks for letting us know. I’ve activated diagnostics mode for your account, when you have a chance can you please let us know after you’ve used the affected remote for a few minutes? We will check to see if a log package came in after we hear back from you, thanks!
Alex: Yes. With a fresh download the Roon app opened with the “latest version” on the MacBook. Do I need to do this every time I get: “There was an error checking for an update”? Is there a more permanent fix? Thanks for the help Bill
Thanks for letting us know the fresh download worked. We still have not seen any logs come in to our server yet. Are you able to manually access your Roon logs from the affected device using these instructions, upload them to the link below, and let us know once uploaded?
Also, are you by any chance using Comcast? We have seen a setting called Comcast Constant Guard cause similar blockages in the past, as well as other firewall tools (Norton/Kaspersky/etc).
Yes. As far as I know. I’m the only one on the network and there are no guest accounts on any of my my remotes. I think Roon, Qobuz, and Bluesound have full access to the file system.
You can verify this by accessing your macOS Privacy & Security settings > Full Disk Access > Ensure Roon is enabled. If it isn’t, you can add it to the list using the ‘+’ button.
We don’t have any immediate next steps or additional information to share at this time, and since redownloading the latest version of Roon helped you - the best next steps would be to resurface the issue if you experience it again.
It may be worth asking Comcast directly if you’re able to adjust the settings @noris mentioned above.