Bug Prevents M3 Ultra Mac Studios From Installing macOS Tahoe

[KaliYoni]

Especially for a 3 trillion dollar company.

Market capitalization ≠ Revenues
Market capitalization ≠ Profit
Market capitalization ≠ Cash available to spend
Market capitalization changes every time there is a trade of AAPL

 

[JeffPerrin]

I wish Apple would do a tick-tock cycle for OS updates. ie. One year of new features followed by the next year with a "Snow Leopard" maintenance release. It's gotten to the point where I truly dread updating MacOS...

 

[BitBLT]

Apple creates confusion when they push out a new version of the old OS and the new OS on the same day. I have definitely wondered whether I should upgrade to the new old OS first.

 

[bmustaf]

The M3 Ultra has no M4 equal, not even close. It's a beast.

that's what you get for buying an m3 in the age of m4

 

[Robert.Walter]

Maybe it is rebelling against that which is called Liquid Glass.

 

[xgman]

no such problem here either, but I did first get the RC beta several days ago. Then another update came through today for Tahoe and I installed that again with no issue which was 25A354.

 

[yaddam205]

The 1st general release is just beta with millions of more testers. Give it a few months to bake.

 

[MrGimper]

It's just showing you you should have bought the M4

 

[ArrayDecay]

Unacceptable.

 

[neuropsychguy]

List the top 3 bugs that are impacting your usage.

That is usually my question for people who post comments like this. I have got a reply a couple times with bugs listed out, but most of the time people just ignore my reply.

 

[con2apple]

So, uh, the Beta and RC didn't catch this bug?!??!? What is even the point of doing betas and RCs if these kinds of bugs persists to release? LOL...

To have news for the media. Stay in the conversation.

 

[con2apple]

Awww man, lucky! My M1 “upgraded” without issue 😡

Deactivate the button "Automatically download and install Mac OS updates"

I have just a red notification bubble at the settings icon. But can live with that.

 

[MDTyKe]

So, uh, the Beta and RC didn't catch this bug?!??!? What is even the point of doing betas and RCs if these kinds of bugs persists to release? LOL...

Honestly, I don't think Apple fixed *any* of the bugs in *any* of the betas or the RC, based on what I'm seeing. We're talking very obvious bugs too. Despite Apple being a trillion $ company, it appears they're down to 2 or 3 developers for the entire macOS team.

 

[apparatchik]

No professional should be installing a new .0 OS upgrade regardless of author (Apple, MS, etc)

Also, it sounds like Apple checks on installation are done very well, as it fails gracefully.

 

[tyranne201]

its not a bug, its a feature.

 

[tyranne201]

They read beta feedback. They just take forever to get to it. I’ve had a couple bugs I’ve submitted that were addressed before. They need to do a better job looking at bug reports in a timely manner though.

the bigger the company, the more problems and bus their software have.

 

[platinumaqua]

What in the what?? How was that not tested. I'm glad that I have a M4 Max Mac Studio that I was able to install Tahoe on but I created a separate volume to test it out before I decide to upgrade the main system since it's my production video editing machine. Needless to say, I'll be waiting until at least 26.0.3 or 26.1 until they iron out things. Plus I can't seem to connect to my Promise Pegasus2 R8 (TB2>TB3) but I haven't tried installing their DEXT driver yet so that may be the culprit. Staying on 15.4.1 for now.

Well since Sequoia is still getting security updates for two more years, it's safe to wait until, say June of next year, to upgrade, if stability is important to you

 

[Corpuscle]

Awww man, lucky! My M1 “upgraded” without issue 😡

There were no reported issues upgrading the M1 studio. So, what exactly are you saying?

 

[ElvisThePelvis]

I didn't run into this bug but I upgraded from the Developer Beta of 26 to the Release Version of 26.

 

[MacATDBB]

This definitely did not affect RC and probably does not affect ALL M3 Ultra Mac Studio's like the article claims.

I did not run any betas, and I upgraded to RC on Friday, then disabled betas and upgraded to the final on Monday. RC and final did not have the same build number, I ran into this on my iOS devices as well, they all were on RC and when I disabled beta updates I was prompted to upgrade. I was up to date on Sequoia before updating to 26 Tahoe.

If you click the Tahoe 26.0 in the about dialog box does it definitely change to 26.0 25A354?

I'm just wondering if the update from RC 25A353 to to 25A354 failed silently.

 

[monstro]

I've been testing the betas all summer; Tahoe since June and 15.7 since it's first RC in August. Never encountered something like this, but I never would have because:

Catching this bug would have required a tester to first install the 15.7 RC, then install the Tahoe beta on top of it. On the specific model M3 Ultra Mac Studio. And that's assuming the bug wasn't introduced in the 26.0 RC, which would have tightened the testing window to less than a week.​

How to prevent an issue like this from ever affecting you:

• Never install the *.0 release of any software on a production machine
• Always read the release notes and question if any of those changes are even needed
• And never install a new version of software everywhere at once
• None of these rules apply to web browsers
  • Because they update faster than they can be tested
  • They access standardized information (web pages) and are easy to replace or swap with identically-functional alternatives

 

[willybk3]

2025 M3 Ultra updated no problem 15.6.1 -> 26. Only problem was jumpy curser (Bartender 5), removed, all is well.

 

[lotones]

List the top 3 bugs that are impacting your usage.

I'm not who you were asking, but I've had to shut down and restart my iPad mini 7 several times to get internet video to play. I've checked this on several sites. Seems to work for several hours until I need to do it again.

Not that big a deal to me considering it's an .0 release. Hopefully it will be addressed soon.

 

[BingWho]

#DevelopmentGoals

 

[Biro]

I won’t consider “upgrading” until 26.2 at the very least.