Alpha Centauri
macrumors 68000
What are you talking about?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases macOS Tahoe 26.6
- Thread starter MacRumors
- Start date
- Sort by reaction score
johnsawyercjs
macrumors 68000
The general explanation for these staggered rollouts is that they're intended to reduce server overload, since they can't handle the number of simultaneous downloads (hundreds of millions) that would otherwise be requested by users worldwide as soon as a release is announced.
But also, once Apple publishes an OS update, the update package has to replicate across thousands of servers around the world, and that can take a little time. Servers in major data hubs update their manifests quickly, while secondary or regional edge servers can lag behind by a few minutes or hours. Your Apple device queries whichever server your ISP routes you to. If your local server hasn't updated its manifest yet, your device will report "Your software is up to date."
Staggering the rollout is also an intentional safety mechanism. If an update contains a critical bug, releasing it to everyone simultaneously could be catastrophic. As soon as people begin installing an update, Apple’s crash analytics monitor the first few million installs for spikes in system panics or network failures, so that if a gross error is detected in the first couple of hours or so, Apple can temporarily pull the update off their servers before it reaches the majority of their user base.
johnsawyercjs
macrumors 68000
I was going to suggest that people just leap ahead and install the public beta for macOS 27, but I'm seeing a few too many annoying little glitches with it of the sort that usually get fixed in a final release version, like the menu bar sometimes disappearing and reappearing, clicks not registering until I click a second or third time, etc.
Howard2k
macrumors 604
The previous poster, who I replied to, suggested that the M4 was being dropped in this update. My comment was (perhaps not obviously enough) facetious.
AeroUK
macrumors 6502
Installed on 2001 MacBook Air M1. Running like a charm. Smooth, fast and stable. Liquidy delicious.
Immediately after an upgrade, the computer is very busy rebuilding the Spotlight index. Check your Activity Monitor to see what could be sucking the resources away. Once that process is done, things should be better again. Just a guess.
ArrayDecay
macrumors 6502
I finally got around to updating my Neo to 26.5.2 this morning and the 26.6 update showed up right after the Neo rebooted from the 26.5.2 update. I am updated to 26.6 with no issues.
E__F__
macrumors newbie
I had a the same monitor handshake issue after update that others mentioned. I have an LG 4k OLED that goes up to 165hz and after update locked me at 120hz at 1440 or I could jump to 4k (small text) and it would give me 144hz. Reboot didn't do anything but taking the HDMI cable out and plugging it back in did the trick. Now all is happy at the weird resolution apple gives me of 3008x1692 (the only option that matches my MacBook Pro text size) at a clean 165hz.
zen42
macrumors newbie
n-evo
macrumors 68020
Alpha Centauri
macrumors 68000
Updated my M1 macbook pro and the touch bar is completely dead after the 26.6 update. Anyone else having the same? The options in keyboard system settings has disappeared.
Alpha Centauri
macrumors 68000
Every since updating to 26.6 I can no longer VNC into my Macs from Windows or iOS apps (e.g. RealVNC).
RealVNC throws the error "Protocol error: key length too large".
macOS-based Screen Sharing between macs works fine, but it seems something changed with the built-in VNC server.
RealVNC throws the error "Protocol error: key length too large".
macOS-based Screen Sharing between macs works fine, but it seems something changed with the built-in VNC server.
AeroUK
macrumors 6502
edubfromktown
macrumors 65816
Slammed it on ~22 hours ago on Pro M3 14" MBP and Studio. No issues so far and I'm thrilled that it did not "break"/AKA reenable 40+ services that I've disabled to eke the most performance out of my Studio that is running a local Gemma4 LLM.
Did anything else change? Are you still plugging it directly into your Mac? No USB hub?
I've been geting a lot of weird error messages in programs lately. Today my Mac told me that it couldn't open any of my old Word documents because they were from an "unidentified developer". Just to be clear Word opened fine. Word could open the file fine. I just couldn't double click on the Word document in Finder (while Excel and PPT documents also worked). Using Open With and Always open with.. didn't take. Resetting the file association through Get Info seemed to fix it but how does a data file get blocked by gatekeeper or whatever?
I think we're on the verge of learning where all the multiple single points of failure in our ecosystems are...