I wasn’t effected by the previous update and this thread (where ‘System Tray’ should read ‘Menu Bar’, BTW: not a carp!) suggests not to install the hot fix.
Yet my Roon installation advises me that there is an update and invites me to install it?
Should I, please?
Got the same message Mark. My system since I resubscribed after a 6 week break after indications that things were on the improve is working correctly for the first time in 2 years +.
So I’m not touching the update when the Hotfix states it is only for MacOS 10/11. Will wait for confirmation of either yes/no and if yes then give it another couple of days to see if the Threads start to mount up again.
Thanks, Fergus!
What build do you have installed now? Asking because the thread title mentions the “Build 1442 update”, and this was the original update with the new features that had the bug. The hotfix is 1445.
Hey @Suedkiez I’m already on 1442 and my System is Macbook Air M2 OS 14.5 so technically it should not be asking to install the update because it is my understanding that the hotfix does not apply to my system, only OS 10 & 11.
I see; wasn’t clear to me if this was the case.
I’m not sure but it seems to me that the release notes are ambiguous. They do state this:
I would guess that everyone auto-updates but that those who experience the bug must install the hotfix manually, following the instructions in the release notes, because once the issue occurs it is not possible to auto-update anymore (because Roon crashes).
If the update only applied to the affected older macOS versions, then there would be two different production builds in the wild, which would be weird, too.
Cheers… 
This is my case too - although with macOS 13.6.7, which (if I’m understanding the post in question correctly), should not trigger this latest apparent update because I haven’t experienced the crashes which those on 10.10 and 10.11 have experienced.
So still confused …
I’d suggest the above should read more like this …
This issue specifically affects MacOS 10.* and 11.* users, if you’re running MacOS 12 or higher please consider this update as optional. Non MacOS operating systems are not impacted and do not require an update.
CC @vova
I’m running OS 10 on one of my computers and I got the notification and I installed it as usual automatically and it fixed the issue I was having since yesterday exporting albums from my library to my desktop for importation into my DAP. Is this how it’s supposed to work?
They may already have had a fix for the export issue in the code and didn’t remove it before compiling for the hotfix. Or the two issues were related in the first place.
Thanks, @Carl; that certainly helps!
But is there any actual harm in applying this update?
For instance, a risk that it might eliminate the removal of the regression which the hotfix itself was released to fix yesterday?
Is the update we’re talking about actually one and the same as that hotfix, please?
Any ideas, please, also @vova?
Couldn’t figure out what was wrong yesterday on iMac but not on laptop or on PC. Woke up today to see the hotfix notice and couldn’t really figure out what it meant. Then today got the update notice that we usually get and installed it. Everything working now [in fact exports are faster with no delay on the iMac]. So: Not complaining!
Yeah, the release note was less than ideal.
Based on the explanation in the note, the issue that was fixed by the hotfix was a bug that had been introduced by their updated build environment/compiler, which affected only the old macOSes.
As such, the autoupdate with the hotfix to solve such a highly specific bug should be fine for everyone.
Thanks, Mario!
That’s how I have been reading it. But I want to be sure.
So another way to clarify the situation now for those running Roon on macOS 12 and above would be to amend this post with wording to the effect that everyone using macOS should apply either the hotfix (2.0.39) and/or last night’s regular update but that the former will only do anything to help those on macOS 10, 11 whose systems experienced the bug discussed? Yes?
The previous update 2.0.38 (that introduced this bug on MacOS 10 and 11) was 5 days ago, not last night. Today (20 hours ago) hotfix 2.0.38 was released to address the specific issue.
Please checkout the Software Release Notes and look at the post’s timestamp.
Summary
If you’re running MacOS 10 or 11 the hotfix should be installed as it fixes the identified issue, if on a later MacOS it is optional (as there was no issue) thus there is no benefit, equally there is no harm. either. (Caveat, any software change carries a degree of risk.)
Time to move on, for me at least, and enjoy the music.
Hey all, I can confirm both @Suedkiez , @Carl suggestions that it is safe to update to #1445 even for those unaffected by this issue.
Much appreciated, @vova; will do 
.
