macOS 26.0.1
Juli Clover (release notes, security, enterprise, no developer, full installer, IPSW):
According to Apple’s release notes, macOS Tahoe 26.0.1 addresses a bug that was preventing Mac Studio machines with an M3 Ultra chip from being upgraded to macOS Tahoe. A failed hardware check was causing macOS Tahoe installation attempts to be aborted, with Mac Studio users ultimately stuck on macOS Sequoia.
Previously:
- Tahoe’s Mac App Store
- Tahoe FileVault: iCloud Keychain and SSH
- Tahoe’s New Recovery Assistant
- Tahoe AppleScript Timeouts
- macOS Tahoe 26
Update (2025-09-30): Laurent Giroud:
This is just incredible. That this bug had to be fixed in a new release means they never tested it on that Ultra configuration.
That or they knew it prevented installation and chose to kept users of that setup to bang their heads against the wall when trying to upgrade.
Today’s update to macOS Tahoe (26.0.1) resolves an issue in apps where AutoFill for Mac apps could make apps slow down over time due to improper handling of event taps, causing them to accumulate over time. People particularly noticed this in Chromium-based web browsers and Electron apps. If your app or framework decided to work around this issue by using an internal AppKit defaults key to turn off AutoFill, I recommend you re-test on macOS 26.0.1, then limit that workaround only to macOS 26.0.0, and remove it for macOS 26.0.1 and above.
Previously:
Update (2025-10-01): Ric Ford:
Another MacInTouch reader emailed us about a tricky Tahoe change to music file handling that continues in the 26.0.1 release.
Dragging songs from the Music library window to the Desktop (or presumably anywhere outside the app) in MacOS 26 moves the file from its iTunes Music location. In prior versions, dragging would copy the file. Note this isn’t true for the TV app – it still copies the file.
I’m traveling and discovered this while away from backups. I deleted the song that I’d moved and will have to wait until I get to backups to restore.
Update (2025-10-07): Andrew Orr:
A handful of Mac owners say they can’t add Outlook accounts to Apple Mail after recent macOS updates, but the scope and cause of the problem remain murky.
The reports in the Apple forums describe failed authentication when trying to add Outlook.com, Hotmail, or Live accounts to Mail. Errors range from “Authentication Failed” to “Unable to verify account name or password.”
ednl:
One (other) very annoying thing Safari 26.0.1 does is flash a white page when navigating to any new site, despite MacOS using dark mode and regardless of the website’s background colour. That didn’t happen in previous versions.
I now developed a habit of closing my eyes before clicking a link to a new website to avoid the bright flash :-/
Update (2025-10-20): Warner Crocker:
Since the release of macOS Tahoe 26.0.1 I’ve seen strange memory leaks increasing for what I think are odd reasons. For example, a process known as IconServicesAgent increases the longer I go between rebooting sessions. According to documentation I’ve found online, one of the causes of this can be an overly large or corrupted icon cache, or specific icon causing the problem. A solution is to clear the icon cache, which I’ve done, but the problem reoccurs.
[…]
There’s another memory leak that I see less frequently and seems a bit more random. You can see in the image above the amount of memory NotifcationsCenter is consuming.
[…]
Prior to macOS 26 Tahoe I had long ago turned off Apple Intelligence’s Notification Summaries on macOS Sequoia. I turned them back on with this new release to see if things improved. They did not. In my experience they are just as bad and just as useless as they were previously.
I have a customer reporting that something changed and one of his .sparsebundle disk images won’t mount on Tahoe even though the same file works on other macOS versions.
5 Comments RSS · Twitter · Mastodon
This and the Electron bug, I think it's time to give up on Apple. They *really* don't care. Like, to a malicious degree. Like a slap in the face. I can't believe how bad they've gotten. We should all invest our energy into making Linux as good as Mac OS X used to be
This is crazy. I’m trying to imagine what kind of testing procedure would exclude testing on one of Apple’s own new chips for the entire life cycle thus far, up to and including release. They only have a few computers and chips. If they didn’t test on the M3 Ultra, what DID they test on?
This is a very basic QA thing. We’re not talking about testing on Intel Macs here. This is a chip many people could plausibly be actively using right now. And if you have it you’re almost certainly a professional meaning it should have received extra priority in my opinion but maybe I’m wrong.
@What Yeah, it’s not some obscure configuration. It’s the current top-of-the-line Mac (since the Mac Pro still has the M2…).
Companies like Apple and Microsoft used to have QA. I don't think they really do that anymore. That would also explain the Electron issues.
Both Apple and Microsoft have different release channels, so their approach now seems to be to have a self-selecting group of users who will test their software for them. In Microsoft's case, this seems to work reasonably well. Windows releases on the regular release channel have been relatively stable, with no significant regressions affecting a large percentage of Windows users. That is clearly not the case with Apple.
I suspect that bugs that don't cause crashes (and are thus not automatically reported to Apple) are essentially invisible to them.
Safari getting more laggy over time is all over Reddit
https://www.reddit.com/r/MacOS/comments/1o3lt2w/lags_after_updating_to_macos_26/
https://www.reddit.com/r/MacOSBeta/comments/1lukimp/macos26_tahoe_safari_becomes_unusable_after_a/
Requires kill loginwindow or reboot to fix
