By the .1 update of any release, the OSes are fine to use. macOS Tahoe has been good since 26.1.Enough to justify transitioning away from Sequoia?
By the .1 update of any release, the OSes are fine to use. macOS Tahoe has been good since 26.1.Enough to justify transitioning away from Sequoia?
Updates are done on the weekends and at nights. I know it because I have a 12 hour shift tomorrow.This sucks for Enterprise. There is still a major bug with regards to FileVault. And releasing on a Friday? Going to throw my upgrade schedule out of whack and right in to the Christmas week.
i get this one
I’m not understanding how these two statements have anything to do with each other.Never forget how stupid Apple thinks you are.
What's the FileVault bug? Previously the .2 releases were Dec 11.This sucks for Enterprise. There is still a major bug with regards to FileVault. And releasing on a Friday? Going to throw my upgrade schedule out of whack and right in to the Christmas week.
Well, it is not really Apple, but the third world teenagers (I mean software developers) that Apple (I mean Cook) relies on to get the most profit possible by not spending on software development.Never forget how stupid Apple thinks you are.
if you want the 25C56 ipsw it is hereThe Build Number is very strange... RC 26.2 (25C56) Final is 26.2 (23C55)
The size is also very strange... 853,8 MB
View attachment 2587272
View attachment 2587273View attachment 2587276
i get this one
14.8.3: https://swcdn.apple.com/content/dow...l8rmaz7jicf3wmys68ptjwho/InstallAssistant.pkg
here is a way to test build numbers for links to InstallAssistant.pkg even before downloading it
replace the g with m at end of link to make link to InstallAssistant.pkm file
so applying this to your link we get this
now download the InstallAssistant.pkm file and open with textedit and we see this:
...version="25.2.56"...
how to read this is second number 0,1,2,... is A,B,C,...
so the 2 is C and build is 25C56
this is the MacOS Tahoe 26.2 NOT MacOS Sonoma 14.8.3
Or for those of us trying to keep the far too common "latest version of macOS" breakages at arm's length. 😜Sonoma 14.8.3 also exists for those keeping AI at arms distance.
exactly my thoughts.. Think I'm gonna keep on rocking Sequoia. Have 26.1 on a dual boot but find myself preferring Sequoia and don't really even boot into 26.1. Will wait and see how it turns out for others. Heck, I waited forever getting to Sequoia as I updated finally from Monterey!Enough to justify transitioning away from Sequoia?
So I will assume that you are one of those that swear that everything is absolutely ok with this mess of a release?You sir need to install Windows 11![]()
that's ok i can see that you fixed it in your original post. but it is a good lesson to test builds before downloading from links to InstallAssistant.pkgSorry I got confused with copy and paste. I even checked the pkm files before and the wrong list was somehow in the clipboard.
That may be the case for servers, but not workstations. Most workstations are not online during the weekend/overnights. At least not 1:1 devices. If the computer is not online, it does not get updated. Plus, in most cases, an Apple O/S updates requires the user to provide their password to complete the update. (The only exception is using DDM to push/enforce the update.)Updates are done on the weekends and at nights. I know it because I have a 12 hour shift tomorrow.
Updates are always installed when nobody's using the devices and it's usually at nights and on the weekends. Christmas isn't off either.
The IT company I work for has many customers too. We usually get an SLA to perform the update for example Sunday night between 02:00 - 03:00 a.m and if it's not successful within the SLA timeframe the company pays fine to a customer.
Maybe your company should also outsource their IT. I can't believe people are complaining about such things. Releasing an update on Friday is not an issue.
Just open a req / task ticket to your IT department and they'll do it. No problemo.
It really only affects Enterprises, but, if you enrollment process creates a user as a Standard user during setup, instead of Admin and you try and enforce FileVault during setup, FileVault will not be enabled. Screws up Zero Touch work flows.What's the FileVault bug? Previously the .2 releases were Dec 11.
No.Enough to justify transitioning away from Sequoia?
15.2 - December 11Previously the .2 releases were Dec 11.
So does that mean you can’t connect to AFP servers, either?
if you want the 25C56 ipsw it is here
i am suspicious of your 23C55 one. For Tahoe it's going to be a 25Csomething not a 23Csomething
This was true in the past, but not in the last few years, and especially with Tahoe. I have 28 unresolved cases in the feedback assistant, and there's probably more reported issues with this version than any before it. At this point, I honestly don't see Tahoe getting fully fix, not is there any compelling reason to use it relative to the potential issue.By the .1 update of any release, the OSes are fine to use. macOS Tahoe has been good since 26.1.