Authorization needed after every Apple macOS update

[poshook]

I have the same issue no matter what Live version I use. Currently Live 12 last beta
But I face this issue with some other vendors like Arturia or Ujam. It looks like there is something wrong with the machine ID properties

[COBOMOJO]

You cannot believe the hell I'm going through to get Ableton Support to unlock further authorizations on the same computer. Ableton refuses to acknowledge that there's a bug with the authorization process. Support claims that any changes to the MacBook or its OS may trigger an authorization reset and a need to re-authorize. If that is true, it would explain why I've had to submit five re-authorization requests over the last six months -- that is according to records provide to me by Ableton Support. Apple Computer routinely sends out updates to the MacOS which are automatically installed on the computer. Ableton Support also suggest that someone may have stolen my credentials. If that's true, there's really no way I, or any other user, can substantiate that claim since the authorization history in the user account file shows a different HW code for each authorization, even if the user knows for certain that the same computer had been used to make the authorization request. It's obvious from the authorization history that there's a bug in the process, perhaps associated with users on Mac M1 (AMD) platforms.

if this was a bug then there would likely be many users experiencing it (and yelling about it on the forum).

if you really think that your computer is somehow unexpectedly generating new hardware codes, you can try following the offline authorisation process the next time you are forced to authorise. that way you can see whether the hardware code has really changed or not:

https://help.ableton.com/hc/en-us/artic ... ware-code-

my guess though is that Ableton has evidence that your authorisation is somehow compromised...

Yo "fishmonkey" you sound like a jerk. Just look at how mean you come across with what you're saying. You're assuming that someone has abused Ableton's product registration when they are just describing an issue that still hasn't been fixed for somewhat older macs. You sound judgmental and closed-minded to any world other than your own. I'm happy for you that you haven't had this issue. And offline authorization wouldn't be a good suggestion based on what the OP described. Just don't say anything if you don't have anything nice to contribute.

[[jur]]

Yo "fishmonkey" you sound like a jerk. Just look at how mean you come across with what you're saying. You're assuming that someone has abused Ableton's product registration when they are just describing an issue that still hasn't been fixed for somewhat older macs. You sound judgmental and closed-minded to any world other than your own. I'm happy for you that you haven't had this issue. And offline authorization wouldn't be a good suggestion based on what the OP described. Just don't say anything if you don't have anything nice to contribute.

Yo, please go ahead and read the Community Guidelines, and stop insulting others. Next time you'll be warned.
thx

[gacki]

Just to add to this topic: I'm having the same problem with several computers (currently still on Live 11).

Usually after every (even minor) update the machine ID is slightly different. Add to this the "mixed messaging" and comparatively slow responses it is becoming a real pain.
"Mixed messaging" means getting after an unsuccessful authorization a mail like

Über Ihren Ableton-Account xxx wurde gerade ein Computer für Ableton Live freigeschaltet.

Plattform: MacOS
Uhrzeit: 29 December 2024 6:07 PM (GMT)

Obviously it wasn't "freigeschaltet" (authorized) - because I'm still getting the same screen that my copy isn't authorized - and I can't find the authorization in my account at all. And when I'm trying to authorize online I can see the message "Live erfolgreich autorisiert" in the web browser while Live 11 in the foreground says "no more authorizations left". What gives?

Of course I've applied for an additional authorization which is now 10 days ago.

As I said several machines are affected: another computer I own and a work machine which runs an educational license. Interestingly a second work machine does not show those symptoms and carries the authorization over even when upgrading the OS to a new base version (like lately from Monterey to Sonoma).

This process is obviously broken for certain macOS configurations and I think it's really time to get this sorted out.

[lovelight]

Im running Live 12 suite and the Beta version on Mac mini M1 latest iOS , and every time i changes running in rosetta mode (for testing some old Vsti 2) im been ask for Authorisation, no matter if it is the Beta or Original version im changing.

[gacki]

OK, I'm starting to get really annoyed.

It's January 16th 2025, I requested an additional authorization before New Year's Eve. I can't authorize Live with

Gute Nachrichten: Deine Anfrage wird bereits bearbeitet, und wir melden uns bald wieder bei dir.

(Good news - your request is in progress and we'll get back to you soon).

It's been over 2 weeks.

The problem clearly lies with the authorization progress. If this doesn't get resolved it is a dealbreaker. I'm teaching (among other things) recording basics and would hate to have to remove Ableton Live from the curriculum.

[gacki]

While I had (after several weeks) gotten another authorization I would like to point out that after updating macOS from 14.7.2 to 14.7.3 the hardware ID is AGAIN different.
Luckily I hadn't authorized Live 11 yet so this probably will work ok. But the next system software update/upgrade will probably break the authorization again. That's really a showstopper bug.

[Rivanni]

I wonder what causes this.
I've never encountered this issue in the past years. Not with small and large macOS updates. I just updated from 15.2 to 15.3, and Live 10, 11, and 12 are not asking me to authorize.

[gacki]

I have a theory (or more precisely a hunch) but I'll wait until the next update to verify this. My guess is that the "hardware" ID encompasses components that are actually set or changed by software.

[Teo7]

I have a theory (or more precisely a hunch) but I'll wait until the next update to verify this. My guess is that the "hardware" ID encompasses components that are actually set or changed by software.

I have exactly the same hunch!

This terminal command that outputs macOS update dates:

Code: Select all

 softwareupdate --history

I compared macOS update dates against my hardware code change dates on both of my laptops. The correlation is surely there.

I have this problem on both my old Intel mac and a newer M2 mac. This has been going on for years. I've issued couple of support tickets on this topic during the years. So I think Ableton is well aware of this issue.

But why this is affecting only a part of mac users? I've been thinking that if I'd set up my M2 as a clean install instead from the Intels' Time Machine Backup, would the problem be avoided on the M2? So far, the only solution to this seems to be rejecting all macOS updates if a fully working Live Suite 12 is critical for You. This is a bit bitter compromise.

Why I'm writing here? I've been waiting for new authorizations for a week now - sigh

[gacki]

Another system update (this time from 14.7.3 to 14.7.6), another lost authorization. Luckily I still had one authorization left this time so no downtime.

I saved a System Report before and after the update. As far as I can see the following things (variables) have been changed. I'm not sure whether that is normal or unusual.

Boot-UUID
the Volume-UUID of the hard drive (but not the one of the data portion of it)
the Domain-UUID for the three Thunderbolt ports

I don't know whether any of those are generally randomized during update or restart. But those are the major (hardware) variables that were different before and after.

[Teo7]

Here's little update:

Last time I got ONE more unlock in 2 weeks. I made also a service ticket and they admitted that there's no other solution but to request more unlocks and they are well aware of the problem.

Now I updated to OS 15.5. and I'm out of unlocks again. I requested more couple of minutes ago. Let's see how log does it take this time.

[Teo7]

Yes! I got more unlocks on 22nd of July so it took two days! Eventually I filed a support ticket and after that it took about 11 hours to get a response and unlocks.

[gacki]

And as expected after updating from 14.7.6 to 14.8 the authorization was gone again. Interestingly I had another one in my account.

But yes - it's definitely an issue.

[kitekrazy]

Is it possible not to update the Mac OS?
We update just to update even when there are no issues. This happens with all software