Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Did you see the green OK check mark at the end of this installation?
Please show a picture of the Tahoe installer within the Applications folder.
Absolute! I saw the green OK check mark at the end of installation.
Screenshot 2025-07-14 at 19.17.22.png
 
  • Like
Reactions: LuckyOldMan
It appears that Tahoe has dropped Fusion Drive support.
The installer does not recognize the Fusion volumes and Disk Utility displays the Fusion drive as split SDD and HDD disks. Disk Utility terminal no longer has the resetFusion command.
It seems logical from Apple perspective, since none of the Mac models supported by Tahoe has a Fusion drive. However, a pity for us with old Macs and likes the Fusion drive flexibility.
The issue is not mentioned in the issues list:
So either the devs has not discovered the missing feature, or have no plans to fix it, if even possible.
So now the options are:
1. Skip Tahoe altogether
2. Install Tahoe on a HDD partition not belonging to the Fusion drive
3. Split the Fusion Drive and install Tahoe on the SDD
 
  • Like
Reactions: HippoInWindow20
1. Skip Tahoe altogether
2. Install Tahoe on a HDD partition not belonging to the Fusion drive
3. Split the Fusion Drive and install Tahoe on the SDD
4. Replace the Apple-Blade-SSD within the FD by a M.2-NVMe-SSD incl. adapter, install macOS Tahoe onto the M.2-NVMe-SSD and keep the HDD for storage.
I suspect it's about a FD in an iMac
 
The signal to noise ratio of this thread has gone down significantly with many new participants seeming to want to hijack it and/or demonstrate their breathtaking depth of knowledge.

I don't need your advice, we've been doing this for years at this point.

And @LuckyOldMan, you should go see a dentist, your avatar makes me feel queasy.
 
I can appreciate everyone working here diligently and trying to get macOS Tahoe on Intel Macs. I am big lover of OCLP and I have used OCLP on all my unsupported Macs.

However, with recently experience with Tahoe on 16" MacBook Pro 2019, I feel like we probably should't install Tahoe on any unsupported Intel Macs anymore. Even the 16" 2019 MacBook Pro is slow and the whole unit runs very hot. At this stage, it maybe related with Tahoe being on beta, but I do think the whole Liquid Glass thing takes is very GPU heavy. Older Mac might not run well.

Sequoia on other hand, runs quite well on machines from 2015 and after.
 
Yes and no: anyone who has worked intensively with the two tools knows the differences.

I've been using OpenCore since the beginning – until then, Clover was the right tool.
The same applies to OpenCore Legacy Patcher – here, the difference is already evident in the naming: OpenCore is a bootloader for Hackintoshes, whereas OpenCore Legacy Patcher has a slightly different objective: it enables unsupported Macs to continue to be used beyond their macOS limitations.

When I read OC 1.5.1, I know it's about a Hackintosh, OCLP 2.4.0 or OCLP 3.0.0 are about real, but unsupported Macs.



There's a good reason why I'm explicitly talking about pure Open Core and OCLP in this thread, and you shouldn't have missed it.

Because it wasn't me who wrote in connection with an unsupported Mac..."In my experience, you do NOT need OCLP (Dortania) 3.0.0n, nor do you need OCLP Mod 2.4.0... All based on my original iMac late 2013. ...but @Oxygen-X1 (see #351).

To avoid any confusion, I discussed it with him beforehand in a private message and later here in the thread.

To better emphasize the differences between OpenCore & OCLP, I added the aforementioned attributes 'pure OC'.

It turned out that he meant OCLP 2.4.0/3.0.0 when he spoke of OC 1.5.0.

By the way: we wouldn't even need to have this discussion about "pure OC" & "OCLP" here if it would only be about unsupported Macs and no Hackintoshes, as the thread title "macOS Tahoe 26 on Unsupported Macs Discussion" suggests.

In my opinion, this confusion has arisen because both Hackintosh and real Mac problems have been discussed here in one thread. The topics should be divided.
The causes and recommendations for solving the problem can be different. What works for a Hackintosh may not work for a real Mac, and vice versa.

As I said before: How is a less experienced forum user supposed to differentiate between the two?
Thank you Lucky have you verry god write.
 
  • Like
Reactions: LuckyOldMan
I can appreciate everyone working here diligently and trying to get macOS Tahoe on Intel Macs. I am big lover of OCLP and I have used OCLP on all my unsupported Macs.

However, with recently experience with Tahoe on 16" MacBook Pro 2019, I feel like we probably should't install Tahoe on any unsupported Intel Macs anymore. Even the 16" 2019 MacBook Pro is slow and the whole unit runs very hot. At this stage, it maybe related with Tahoe being on beta, but I do think the whole Liquid Glass thing takes is very GPU heavy. Older Mac might not run well.

Sequoia on other hand, runs quite well on machines from 2015 and after.
I can't confirm that, see my signature; I have the same MB Pro 2019 (16 inches).

Tahoe Beta3 actually runs quite well, and I don't have any heat issues; it's
always around 56 degrees Celsius, even when browsing normally with Google Chrome, etc.

CPU usage is also completely normal, just like with the Sequoia 15.6 Beta2.
 
@mikezang

I recreated the Tahoe installer stick as you tried to create with OCLP 3.0.0n (see also your pic in #400).

First, I downloaded macOS 26 Tahoe with OCLP, then specified the 32GB stick as the target, and after validation, which didn't produce any errors, I finally received a Tahoe installer stick.

Maybe something went wrong when you did the same. Did you try a second time?
 
Last edited:
I can't confirm that, see my signature; I have the same MB Pro 2019 (16 inches).

Tahoe Beta3 actually runs quite well, and I don't have any heat issues; it's
always around 56 degrees Celsius, even when browsing normally with Google Chrome, etc.

CPU usage is also completely normal, just like with the Sequoia 15.6 Beta2.

I didn’t not do clean install. But I did the factory reset on Sequoia and updated from clean Sequoia installation.

For me, the lag is very visible, things take seconds to happen. 56C is kind hot TBH, anything over 40C will make your hands uncomfortable. There is no question that Tahoe runs better on Apple Silicon than Intel.

I will do clean installation on 16” once final release is available, but for now, I think Intel Mac should stop on Sequoia
 
  • Like
Reactions: Oxygen-X1
@mikezang

I recreated the Tahoe installer stick as you tried to create with OCLP 3.0.0n (see also your pic in #400).

First, I downloaded macOS 26 Tahoe with OCLP, then specified the 32GB stick as the target, and after validation, which didn't produce any errors, I finally received a Tahoe installer stick.

Maybe something went wrong when you did the same. Did you try a second time?
I tried several ttime, all in the same results...:(
 
Last edited:
  • Like
Reactions: LuckyOldMan
I didn’t not do clean install. But I did the factory reset on Sequoia and updated from clean Sequoia installation.

For me, the lag is very visible, things take seconds to happen. 56C is kind hot TBH, anything over 40C will make your hands uncomfortable. There is no question that Tahoe runs better on Apple Silicon than Intel.

I will do clean installation on 16” once final release is available, but for now, I think Intel Mac should stop on Sequoia
My MB Pro 2019 runs in desktop mode, i.e., connected to an external 4K 28-inch monitor with a suitable dock.

My MB Pro also has small feet on the back to improve cooling.
What have you for a CPU i7 or i9
 
Last edited:
I tried several ttime, all in the same results..
Downloading via Mr. Macintosh and then creating the flash drive via Terminal & createinstall... or downloading via OCLP and then using OCLP to create the flash drive are both methods I've used successfully.

Have you tried initiating the installation from a running macOS (Ventura, Sonoma, Sequoia) using the Tahoe installation app in the Applications folder?
Of course, OCLP 3.0.0n must also be present (on a small flash drive, as I usually do).
 
  • Like
Reactions: olad and ronton3
On the OCLP Source landing page, the Devs have asked us not to share direct links to OCLP binaries.


Screenshot 2025-07-15 at 8.07.13 AM.png



I get that we're sharing direct links, because we have OCLP users who don't know GitHub. I would suggest that those who can't find OCLP 3.0.0 "nightlies" should take some time to learn GitHub - the repository where OCLP is stored.

EDIT: For those who don't want to take the time to learn the basics of GitHub and you want to continue to rely on others to share links with you, understand that the links shared (like the one in the previous post) become outdated as soon as the Devs publish changes to OCLP. You're not doing yourself any favors by following old links to OCLP binaries - especially this early in the development of OCLP 3.0.0.
 
Last edited:
Updated my MBP5,2 to 26.0b3 from b1. Running as expected now.

Using OCLP 3.0.0n branch macos-next from source. The last commit from 14 July is relevant because it is a USB1.1 machine. The generated EFI could‘t boot Tahoe b1 or the b3 installer. Commenting out the last commit fixed it. - All OK on MBP11,1 as it should when looking at the source.

No patching attempted yet on the 5,2. Partial patching (camera only) fine on 11,1.

As always, big thank you developers!
 
Quick question: Is handoff/airplay suppose to be working with OCLP 2.4.0? If so, what settings do I need to enable? I am on a 9,2. Any tips are welcome, thanks!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.