As of macOS 27, Apple will drop support for Apple Filing Protocol, so Apple Time Capsules and many third party devices will lose support for Time Machine backups over a network.
As far as I know, the extended SMB method will continue to be supported for networked Time Machine backups by macOS 27 and later.
Not all third party NAS devices support the necessary SMB version and extensions, but I expect that many of the major NAS manufacturers will provide updates to at least some of their devices to allow it. If you have a third party NAS, check with the manufacturer for more information.
I am in the “cautious users” group, and have been a member of that group for just about every time a new version of theMac OS appears. I certainly plan on waiting until at least V26.2 of Tahoe arrives. But with Sequoia, I waited until V15.3 appeared, as there were still some bugs in V15.2. Again, there was nothing earth shattering that I needed in Sequoia, and it’s the same with Tahoe.
Additionally, given that I use third party software on both of my Macs, it is imperative that I insure ALL of them are compatible with the new version of the Mac OS. Fortunately that typically involves having 2 or 3 programs updated.
I don’t normally ‘live on the edge’ but now I’m retired I can afford to be a bit more relaxed about upgrades. Two things I’ve noticed immediately after the update. Software Update was changed to “Install all updates” rather than Security Updates Only, and Filevault was turned on despite me having it turned off.
I’m not interested in getting into a debate of the value of these features, but it REALLY annoys me when Apple decides to ignore my previous choices and does whatever it wants.
Arrrghh, I wonder how many other things have been changed without my permission. Not happy!
Since nobody knows. Apple will not tell us. It is down to what you believe.
I believe it is the new parts of the OS that introduce security issues that Apple fixes. I am probably more secure on 18.7. I will, however, upgrade in about ten days. Then I will know no major bug has surfaced.
I’ve upgraded my phone, iPad, and watch (I’d been running the public beta on my iPad so had a sense there were no show-stopping bugs) and so far, so good. My Mac is mission-critical so I’ll wait a week or so to see if there’s anything bad that comes out in wide release and then take the plunge.
Although it implies that there are 41 bugs in 15.7 that Apple hasn’t bothered to fix, that isn’t necessarily true. It could also be that:
Some of those bugs were previously fixed in an earlier release (e.g. 15.6.x)
Some of those bugs may be fixed in an upcoming release (15.7.1?)
Some of those bugs may not actually affect macOS users. Apple routinely triages upstream bugs to decide what they want to include.
They may be in 26 because they’ve integrated the latest upstream code for some open source components, but have decided that the bug is not serious enough to require a back-port to older releases.
The bug may also only exist in the latest version of an upstream code-base. The older version found in an older macOS release might not have the bug.
Or Apple really is just sitting on 41 critical security bugs because they don’t care about version 15 anymore. I’m just saying that there are multiple explanations for the different bug counts.
. This is the second time Apple has pulled that stunt. I wonder if they’re next going to do something where the cancel button triggers an upgrade, like they did for the Sonoma release.
Once is a bug. Twice is incompetence. Three times is a conspiracy.
I assume this is due to local snapshots holding pre-upgrade content on your Data volume. Please check to see if this remains the case 24 hours later, after those snapshots expire.
I did an EA install on AppleOS IOSPhone IOSPad, because i need to be ready for when my customers call me -surprised -at login questions and changes, (I used to be bleeding edge- but i have my own production workflow needs these days) - so far so good. - Revealed a couple multiple message threads (family group) that hopefully is resolved. My midi keyboard seems to be getting messages over usb. I may install on my 2018 Mini (that’s collecting dust) just to see how it deals with Tahoe. Caveat Downloadtor!
I loaded Sequoia 15.7 on my M1 Max Pro, my primary laptop. No problems.
This morning, I loaded Tahoe on my M4 Air. Logging initially into the admin account had no problems (after I got through the ‘new OS introductory’ gunk.) HOWEVER, then logging into my normal user account has generated the spinning technicolor beachball in the “Setup Assistant” application. Other stuff is running in the background (I got a notification about a PT appointment in a couple minutes…) But I can’t Command-tab to switch away from that app. I’ll let that run another hour or so, and then if it’s still there, force-reboot. Fortunately, there’s nothing critical on that machine I’d lose if I have to delete and restore my everyday account.
One more note: There’s a new version of Music.app, it’ll be interesting to see if this solves the chronic problems I’ve had with previous versions.
This is because you didn’t click on the little “i” icon next to the Sequoia option, where Apple conveniently preselected Tahoe instead. It was surprising to see that mistake, but not really. Apple has done this before.
Usually fall into the Cautious User category & wait at least a week or more before upgrades. Started having problems w/my iPhone a few days ago; it wasn’t “ringing” for incoming calls, calls were going straight to voice mail but no voice mail notification. Calls weren’t even showing on Recent Call screen, only knew I’d missed the calls as my daughter texted me; no alerts shown anywhere.
Also, iPhone wasn’t “ringing” for texts either; they were showing up in Messages but no “noise” when they came in. Even my Apple watch, which is set to Silent but vibrate for incoming calls & texts, wasn’t responding.
Was dreading a tech support call to Apple so I went ahead & updated both iPhone OS & Watch OS, phone is again ringing for calls/texts & watch is vibrating. Guess sometimes it might be necessary to update the OS quickly. YMMV.
I’m not deploying Mac upgrades for a while. The Music app is one thing that gets little coverage, moving the controls to the bottom reminds me of Apple’s attempted forcing of the Safari URL and controls to the bottom. Unlike Safari, I have my doubts Apple will ever give users a choice in Music. They’ve done other things to ruin Music, like eliminating the status bar.
Reducing Transparency will help, but not solve the Liquid Glass visual problems. I support a number of users with imperfect vision and I know they will not do as well with Tahoe. Left justifying text in dialogue boxes is ugly too.
I’ve usually been an “early adopter” or an “enthusiastic user”, but OS 26 feels too unpolished and poorly considered. I’ve decided to be a “cautious user”, perhaps even a “reluctant upgrader”, for the first time since the Lion / Mountain Lion era. I will be staying on 15.x/18.x for me for the foreseeable future.
I noticed that there are security updates for devices that can’t be upgraded to the latest OS versions. Updates to fix a vulnerability in iOS/iPadOS 15.x and 16.x were released. The iOS/iPadOS 17.x update that addressed this particular vulnerability already was released already a few weeks ago.
OK, when I came back from PT, the Setup Assistant was still running with spinning beachball. I force-rebooted the laptop, logged onto the admin account, ran Disk Utility → Disk First Aid. That reported and repaired damage. I was then able to log onto the normal user account, which launched as expected.
It looks like the old advice “Run Disk Utility → First Aid Before installing an update” is still good advice.
Yes! I saw that too. I figured it was only because I clicked the “I” to see what other update was hiding (it was Safari). Based on this I’m glad I did.
It’s not a “mistake”, but it is VERY DISAPPOINTING behavior by Apple. This is the kind of effluent we expect from Microsoft. Same thing applies to the setup assistant pre-selecting “automatically install updates,” overriding by default my previous “notify and download, but let me decide when to install” preference.
I’m looking at Software Update. It offers “macOS Tahoe 26” up top and then “Other Updates” below. If you click on the the little i next to it, that reveals that “Other Updates” consists of: macOS Tahoe …………… 26 macOS Sequoia …………… 15.7 Safari …………… 26
So “Other Updates” ends up preselecting the same as the top-offered choice. Meanwhile, macOS Sequoia 15.7 remains unchecked despite the specific “Other Updates” section it’s listed in.
I really hope this was an individual screw-up as opposed to Apple essentially admitting they have such little faith in the benefits of their upgrade that they believe it’s trickery that will achieve their desired result. As @shamino points out above, this is not the first time we’ve seen such a stunt.
I did an upgrade to OS 15.7 on both of my Macs last night, and no hitches at all.
A new version of Onyx will soon be available for Tahoe, which is typical. In looking at the Shirt Pocket Software blog about SuperDuper!, David Nanian is encountering some “weird” things, but I am confident he will get through all them.
But even if all the third party software works with Tahoe, I will still wait until at least V26.2 arrives.
When I selcted Software Update, Tahoe was listed first, but the one for Sequoia OS 15.7 was clearly listed next. No problemo selecting it. Update went smoothly on both of my Macs.
. This is the second time Apple has pulled that stunt. I wonder if they’re next going to do something where the cancel button triggers an upgrade, 
macOS Tahoe …………… 26
macOS Sequoia …………… 15.7