This worked fine, but I’m still unable to launch Roon controller from my Mac. Is this related or a new issue?
Sorry, I should’ve specified that I am running Windows 10. I’m not sure about MacOS or other OSes.
I suppose searching in RoonServer and its subdirectories might be a good general way to find the file.
Realized that “bits” lived elsewhere, too - once I removed them all, this fix worked…
The workaround FAQ has information / instructions for each different OS.
Noris - I appreciate that those of us who are regular forum members are being told about this fix and a pending new release. But there’s just 65K registered Forum users. What about the other 200K Roon users who don’t use the Forum? Shouldn’t Roon Corp be sending out an email to all users explaining about the issue? Especially important are those users who take updates automatically.
Mac info fixed it for my iMac too. All back to normal now.
Hello,
well, the comparison is not reliable. But I don’t want to take away your perspective either.
It is not the user’s responsibility to point out a faulty update. Users should have been informed.
The so-called HotFix is the work of those who can access their system and who dare to do so.
Why should I pay Roon for this? An update from the manufacturer is not chargeable, even for my car. In addition, the update was the trigger.
As already described, mistakes happen, just dealing with them is bad at this point.
No, that’s the workaround. The Hotfix is the update that Roon is working on as we speak, and users will get it as soon as it’s available and updates are reenabled.
Hi
No start roon server!
Yes. See further up in this thread for an immediate workaround, or wait a little bit until Roon releases the update that will fix it.
Hello,
thanks for the correction. That was important.
Hey all, we’ve released a hotfix build that should address this problem.
OK great. How do I access this fix?
Doing the workaround allows roon to start again, however my core can no longer be seen. Even from the same machine.
Same for me
Hello All,
We have just released Roon Build 1169 to address this issue and have edited the pinned post:
If your Core is not updated yet, please update it at your earliest convenience. We will be splitting users who are still impacted into their own threads momentarily so that we can address any remaining issues.
If you are unable to take the update or have any issues getting out of this state, please let us know here or open a new Support post and our support team will work one-on-one with you to resolve any remaining issues.
Thank you for your patience here while we worked to correct this update issue.
You might want to edit the path instructions in the KB Article referred to in the “banner post” on the forum.
The path in text does not match the real path or the screen shots from neither Win nor Mac.
A post was merged into an existing topic: Can’t find Roon Core after update
A post was merged into an existing topic: Can’t find Roon Core after update
A post was merged into an existing topic: Nucleus update issue, removed bits already