macOS Tahoe 26 on Unsupported Macs Discussion

[oldmacs]

This may be a dumb question, apologies in advance.

I've installed OCLP for a couple of friends and family members - I had advised them not to install macOS 26, but one has accidentally - so I'm going to have to erase and reinstall Sequoia I suppose.

How do I totally block Tahoe from installing? I turn automatic updates totally off on Macs I do OCLP on but this doesn't prevent them from getting confused when doing point updates for Sonoma or Sequoia.

 

[TOM1211]

This may be a dumb question, apologies in advance.

I've installed OCLP for a couple of friends and family members - I had advised them not to install macOS 26, but one has accidentally - so I'm going to have to erase and reinstall Sequoia I suppose.

How do I totally block Tahoe from installing? I turn automatic updates totally off on Macs I do OCLP on but this doesn't prevent them from getting confused when doing point updates for Sonoma or Sequoia.

I think best one is as posted above is just to put it on Beta updates for Sequoia then it doesn’t see Tahoe at all as I quick fix if you can or not block Apple updates with a firewall has always been debatable without interfering with other things.

 

[imacker2011]

There is also this script, which is designed to prevent Tahoe updates appearing for 90 days. I use it on several different machines with Sequoia 15.7. Quite easy to install also.

It is some kind of MDM policy management accessible through system settings.

 

[TOM1211]

Purely for just trying it I managed to install 26.1 beta on my mid 2014 MacBook Pro

Obviously no use , installer got stuck loads of times , stuck loading desktop (or was just very very slow or I was impatient) so turn off and on several times but it made it updated OTA from Sequoia OCLP 3.0 nightly.

 

[Oxygen-X1]

@TOM1211 So, now you've installed it, and your NVidia graphics card isn't working with full graphics support? It's definitely not working... so you can forget about it, just like on my late 2013 iMac (27-inch) with an NVidia graphics card.

 

[TOM1211]

@TOM1211 So, now you've installed it, and your NVidia graphics card isn't working with full graphics support? It's definitely not working... so you can forget about it, just like on my late 2013 iMac (27-inch) with an NVidia graphics card.

again did state obviously no use lol am aware of no graphics support but it’s on a fifth test partition and should patches ever be released 6 months / 12 months from now or never I know I have a running installation of Tahoe which could mean nothing or be a good starting point either way it’s all good.

 

[Oxygen-X1]

again did state obviously no use lol am aware of no graphics support but it’s on a fifth test partition and should patches ever be released 6 months / 12 months from now or never I know I have a running installation of Tahoe which could mean nothing or be a good starting point either way it’s all good.

Yes, my dear friend, I do the same thing on my late 2013 iMac. I also have this Tahoe Final Build
26.0 on a test partition where everything works except for graphics and Wi-Fi (which I don't need).

Everything works perfectly on Sequoia 15.7, and I'll continue working with that if graphics are
never supported in Tahoe.

I still have my 2019 MacBook Pro (Intel) with a 16-inch display, and Tahoe still works
perfectly on it; it's still supported by Apple.

 

[ronton3]

"Yes, my dear friend, I do the same thing on my late 2013 iMac. I also have this Tahoe Final Build
26.0 on a test partition where everything works except for graphics and Wi-Fi (which I don't need)."

I also have an experimental, deletable, volume T26/3.0.0n, sleep does not work, does it on yours?

 

[Oxygen-X1]

"Yes, my dear friend, I do the same thing on my late 2013 iMac. I also have this Tahoe Final Build
26.0 on a test partition where everything works except for graphics and Wi-Fi (which I don't need)."

I also have an experimental, deletable, volume T26/3.0.0n, sleep does not work, does it on yours?

I don't need sleep mode and/or anything similar; I've NEVER used it in all my 15 years of using a Mac.

 

[deeveedee]

I also have an experimental, deletable, volume T26/3.0.0n, sleep does not work, does it on yours?

I hadn't tested, because I'm not testing much until I can apply post-install patches, but I just tested sleep to satisfy my curiosity... Sleep does not work on my MBP6,2 with Tahoe 26.1 Beta. I'm not expecting much of it until 3.0.0 is available and I can apply post-install patches.

Sleep / wake works fine with Tahoe 26.0.1 and 26.1 Beta on my other systems that do not require post-install patches (even systems that are using Open Core to force Tahoe compatibility), so I suspect the sleep functionality will be restored when OCLP post-install patches officially support Tahoe.

 

[Ghosthengst77]

Don't get your hopes up for this year's OCLP for Tahoe. Unfortunately, since only two people are working on it, and they have their own lives, it won't be finished this year. Not to mention that they're having significant problems getting the T2 and T1 chips to work in OCLP. Unfortunately, the best man, Mykola Grymalyuk (khronokernel), has moved to Apple. And these two now have to fill the gap and take over his work on OCLP. If you can't wait for Tahoe, you'd better buy a new Mac that officially supports Tahoe.

 

[Neon Ball]

Don't get your hopes up for this year's OCLP for Tahoe. Unfortunately, since only two people are working on it, and they have their own lives, it won't be finished this year. Not to mention that they're having significant problems getting the T2 and T1 chips to work in OCLP. Unfortunately, the best man, Mykola Grymalyuk (khronokernel), has moved to Apple. And these two now have to fill the gap and take over his work on OCLP. If you can't wait for Tahoe, you'd better buy a new Mac that officially supports Tahoe.

"These two" have been the main people behind root patches from the start of the project, one of them (at least) was there already for dosdude1 patchers. As I already said before Mykola was mainly maintaining the Python side of things in the recent couple of years since he was busy and didn't have much time.

There is way more to do this year than any of the years prior, it's the most significant change to macOS since Big Sur and also T2 machines are proving to be very difficult.

Just don't talk about matters you seemingly don't know anything about.

 

[Sven G]

Tahoe can wait, especially for our old unsupported Macs: I’d say that instead it might be much more important to maintain a good support for Sequoia (and Sonoma). BTW, now that the last IPSW for Sequoia is fixed at 15.6.1, will there be potential problems for the MetallibSupportPkg package (which is based on the IPSW)…? Mr Macintosh hinted at this, in his latest video: but maybe the final IPSW will be sufficient, for all future patches - let’s hope that there won’t be big problems…

 

[Sven G]

Apple Silicon M1/M2/M3/M4 macOS IPSW Firmware Restore Files Database

Apple Silicon Mac Direct ISPW Download Links Database. This database includes ISPW file sizes, Is the OS Still Signed? Release Dates & More!

mrmacintosh.com

 

[Ghosthengst77]

"These two" have been the main people behind root patches from the start of the project, one of them (at least) was there already for dosdude1 patchers. As I already said before Mykola was mainly maintaining the Python side of things in the recent couple of years since he was busy and didn't have much time.

There is way more to do this year than any of the years prior, it's the most significant change to macOS since Big Sur and also T2 machines are proving to be very difficult.

Just don't talk about matters you seemingly don't know anything about.

"These two" were—the emphasis here is probably on were. If they had achieved further success here, even if only a small one, we would have seen something. Instead, nothing has happened with OCLP "macos-next" for three months.
This suggests that it's more difficult for them to find a solution or get OCLP working this year! If at all, probably next year!

 

[Neon Ball]

"These two" were—the emphasis here is probably on were. If they had achieved further success here, even if only a small one, we would have seen something. Instead, nothing has happened with OCLP "macos-next" for three months.
This suggests that it's more difficult for them to find a solution or get OCLP working this year! If at all, probably next year!

That is because the patches are developed in private and won't be published until they're ready across the board. There are reasons for why it's done this way now and I won't go further into it. I can say that constant progress is being made.

Again, don't talk of things you don't know about. It makes you look like a fool.

 

[sinbad21]

That is because the patches are developed in private and won't be published until they're ready across the board. There are reasons for why it's done this way now and I won't go further into it. I can say that constant progress is being made.

Again, don't talk of things you don't know about. It makes you look like a fool.

I don't see valuable reason to suspend publication on macOS-next. Why ? It is only sources, no release of any package, you have to compile it yourself.

I rather think that nobody has worked on Tahoe since 3 months, reserving the efforts to Sequoia which is regularly updated.

 

[educovas]

I don't see valuable reason to suspend publication on macOS-next. Why ? It is only sources, no release of any package, you have to compile it yourself.

I rather think that nobody has worked on Tahoe since 3 months, reserving the efforts to Sequoia which is regularly updated.

Yes, we are working on Tahoe since the first beta. We are also working on Sequoia. People have no idea how long it takes to fix a single bug and these patches have many. Each major release introduces new problems because we're using old drivers and frameworks which only gets more and more problems with time.

Why would we release something to the public, even as nightly when it can't even be used properly? Why not just fix the current know problems and release when we think it's stable enough? Just to remember, there are a LOT of patches that needs work and they all have many problems for a small group to resolve. More problems than any previous macOS version.

 

[deeveedee]

Very nice to see Tahoe with NVidia graphics!

 

[Heindijs]

View attachment 2562672

Yes, we are working on Tahoe since the first beta. We are also working on Sequoia. People have no idea how long it takes to fix a single bug and these patches have many. Each major release introduces new problems because we're using old drivers and frameworks which only gets more and more problems with time.

Why would we release something to the public, even as nightly when it can't even be used properly? Why not just fix the current know problems and release when we think it's stable enough? Just to remember, there are a LOT of patches that needs work and they all have many problems for a small group to resolve. More problems than any previous macOS version.

That's all we've needed to hear. Some people seemingly just don't have the patience. That said, the lack of communication and updates to the repo have (I hope understandably?) raised some eyebrows for some. I totally get that it's annoying to have people try to build an unstable beta version of the patcher which then doesn't work so they file bug reports for things the team is most likely already aware of, but this is a new one for us.

 

[sinbad21]

View attachment 2562672

Yes, we are working on Tahoe since the first beta. We are also working on Sequoia. People have no idea how long it takes to fix a single bug and these patches have many. Each major release introduces new problems because we're using old drivers and frameworks which only gets more and more problems with time.

Why would we release something to the public, even as nightly when it can't even be used properly? Why not just fix the current know problems and release when we think it's stable enough? Just to remember, there are a LOT of patches that needs work and they all have many problems for a small group to resolve. More problems than any previous macOS version.

Ok, pleased to know that. It’s important to communicate from time to time.

 

[MacMorrison]

I'm glad the developers are proceeding carefully.

macOS 26 Tahoe probably has a lot of bugs along with all the hardware support Apple took out of the operating system. It's hard to imagine who needs Tahoe right away unless you're a professional beta tester or software developer.

Howard Oakley over at The Eclectic Light Company blog tested whether apps open faster in Tahoe... not really:

https://eclecticlight.co/2025/09/30/do-apps-launch-faster-in-macos-tahoe/

 

[peppolone]

I don't see valuable reason to suspend publication on macOS-next. Why ? It is only sources, no release of any package, you have to compile it yourself.

I rather think that nobody has worked on Tahoe since 3 months, reserving the efforts to Sequoia which is regularly updated.

Actually, on the macOS-next branch there is practically nothing...honestly, I think it won't be updated again until the release of version 3...I think they're just working without releasing incomplete or unstable versions

 

[OKonnel]

Very nice to see Tahoe with NVidia graphics!

As far as I know, within the OCLP team, @educovas deserves a special recognition for always allowing us to successfully use nNvidia graphics cards.
Praise and glory to this small but great hero who, with his skill and generosity, also honors his country!
If we really want to collaborate with the Team, let's remember to give a little financial help, from time to time, via the link on the official OCLP pages, and not just download OCLP and give a few easy "likes"

 

[mpbb]

I haven't used my my MacRumors account in a long time but i have to say something.

I'm one of the only two working on root patches for OCLP. Only two have to add suport for dozens of macs and fix patches full of bugs. We have a life, we have problems and we're not taking money from this, it's a voluntary work. Sometimes i feel like some people can't understand that we're also humans and that things takes time to get ready.

Valeu, está valendo e valerá por muito tempo. Muito obrigado.