[release] macOS Tahoe 26.4.1

[MakAsrock]

1 hour ago, deeveedee said:

I should hope not.  You have a 12th gen i7 with 64GB 3200MHz RAM and an RX 5700XT.

There were some slowdowns in the previous version, but they were fixed using the method described above. 😉

[fspkwonx86]

does anyone think that installing 16gb of ram on a kabylake instead of the stock 8 is going to make the difference in speed stability and reliability and stop crashing because I seem to THINK it will/would...  its a 2017 iMac... Intel GPU so its suffering from having to share ram anyway.. it runs about the same as it does on Monterey with 8gb so in thinking that the reason is 8gb is sheerly my speculation..

Edited April 12 by fspkwonx86

[Max.1974]

@MakAsrock @Deeveedee and others ! 

 

Hello my dear friends, I had the impression that on the Lenovo 10th Gen Intel UHD 620, version 26.4.1 felt lighter than 26.3.x, but I didn’t really test it thoroughly. I noticed a small improvement, a lightness that makes it easier to tolerate the PC’s slowness, but it’s still not comparable to Ventura, which runs really well.

[deeveedee]

@Max.1974 On my 10th Gen HP EliteBook 850 G7 (i7-10610U, no dGPU, 15W->25W), performance in 26.4.1 and 26.5 feels perfectly normal a few minutes after boot.  On my 65W 8th and 9th Gen desktops (especially those with dGPU), the "lag" after boot/login is hardly noticeable.  This doesn't surprise me, because Geekbench 6 benchmarks of my 10th Gen laptop show that CPU and graphics performance is less than that of an 8th Gen i5-8600 Desktop.

 

Intel's attempt to make a low-watt (15-25W) CPU by "crippling" CPU performance makes for good battery life, but less than ideal performance.

 

EDIT: If I don't shutdown my laptop and instead just let it idle when not using it and I wake it to use it, I don't experience the lag in Tahoe 26.4.1 and 26.5.

Edited April 12 by deeveedee

[MakAsrock]

1 hour ago, fspkwonx86 said:

does anyone think that installing 16gb of ram on a kabylake instead of the stock 8 is going to make the difference in speed stability and reliability and stop crashing because I seem to THINK it will/would...  its a 2017 iMac... Intel GPU so its suffering from having to share ram anyway.. it runs about the same as it does on Monterey with 8gb so in thinking that the reason is 8gb is sheerly my speculation..

You are actually on the right track with your speculation, but only to a certain extent. On an iMac 2017 SMBIOS running modern macOS, 8GB is indeed the 'bottleneck' because the Intel HD 3000 iGPU has no dedicated VRAM. It 'steals' from your system RAM, leaving macOS with barely 6GB to breathe. This leads to constant swapping, UI lags, and application crashes.

Will 16GB make a difference?
For macOS Monterey, absolutely. It will significantly improve stability, stop those out-of-memory crashes, and give the iGPU enough headroom to function without choking the rest of the system.

However, for macOS 26.x Tahoe, RAM isn't your main enemy—architecture is.
Even with 16GB, your Dell Latitude E6520 hits two 'hard walls' in Tahoe:

Lack of AVX2: Your 2nd Gen Sandy Bridge CPU only supports AVX. Tahoe heavily relies on AVX2 (introduced in 4th Gen Haswell). The system isn't just crashing because it's out of memory; it's crashing because the CPU literally doesn't understand the instructions the OS is sending.

No Metal Support: Modern macOS requires a Metal-compatible GPU (like an AMD Radeon) for a stable UI. The HD 3000 is legacy hardware. No amount of RAM can compensate for the lack of hardware acceleration that Tahoe expects.

Verdict:
If you want a stable machine, upgrade to 16GB RAM and stay on macOS Monterey. It will feel like a new laptop. Trying to force Tahoe on Sandy Bridge is a recipe for disaster—it's simply too old to handle the AVX2 and Metal requirements, and the tools you need (like OCLP 2.4.1) aren't ready for Tahoe anyway.
Even if you use OCLP-Plus 3.1.9, it does not support legacy networking or non-Metal graphics cards. This means on Tahoe, you will be stuck with no Wi-Fi, no graphics acceleration, and constant kernel panics due to the missing AVX2 instructions.

[deeveedee]

@MakAsrock I thought they asked about Kabylake.

[fspkwonx86]

30 minutes ago, MakAsrock said:

You are actually on the right track with your speculation, but only to a certain extent. On an iMac 2017 SMBIOS running modern macOS, 8GB is indeed the 'bottleneck' because the Intel HD 3000 iGPU has no dedicated VRAM. It 'steals' from your system RAM, leaving macOS with barely 6GB to breathe. This leads to constant swapping, UI lags, and application crashes.

Will 16GB make a difference?
For macOS Monterey, absolutely. It will significantly improve stability, stop those out-of-memory crashes, and give the iGPU enough headroom to function without choking the rest of the system.

However, for macOS 26.x Tahoe, RAM isn't your main enemy—architecture is.
Even with 16GB, your Dell Latitude E6520 hits two 'hard walls' in Tahoe:

Lack of AVX2: Your 2nd Gen Sandy Bridge CPU only supports AVX. Tahoe heavily relies on AVX2 (introduced in 4th Gen Haswell). The system isn't just crashing because it's out of memory; it's crashing because the CPU literally doesn't understand the instructions the OS is sending.

No Metal Support: Modern macOS requires a Metal-compatible GPU (like an AMD Radeon) for a stable UI. The HD 3000 is legacy hardware. No amount of RAM can compensate for the lack of hardware acceleration that Tahoe expects.

Verdict:
If you want a stable machine, upgrade to 16GB RAM and stay on macOS Monterey. It will feel like a new laptop. Trying to force Tahoe on Sandy Bridge is a recipe for disaster—it's simply too old to handle the AVX2 and Metal requirements, and the tools you need (like OCLP 2.4.1) aren't ready for Tahoe anyway.
Even if you use OCLP-Plus 3.1.9, it does not support legacy networking or non-Metal graphics cards. This means on Tahoe, you will be stuck with no Wi-Fi, no graphics acceleration, and constant kernel panics due to the missing AVX2 instructions.

well you'll be happy to hear its the 2017 iMac iMac 18,1? specifically its the non-ati Intel Iris Plus 640 Kabylake Model which has support for Tahoe except for: SMBIOS-CPU_INFORMATION is using CPUFriendDataProvider.. , AppleHDA but isnt that everyones problem, and Wi-Fi which BCMWLCompanion Fixes.. and obviously no SMBIOS-Platform-Support which OpenCore fixes.. Still correct that the GPU is stealing Ram in fact its probably using MORE on Tahoe... leading to lets look at Memory Statistics -> if all cached memory is compressed then -> is Specifically what apps are OPEN so its compressing literally all of the memory its using.. Split Wired and App Memory is an indicator of how much memory cannot be swapped or cached... this means that I suspect the GPU is using 2GB of System Ram..  So on a normal machine this wouldn't be an issue... and also perhaps on a System with 2 Ram Chips it also might not be... This is the lucky Mac that can have 2 ram chips and is compatible with 16GB ... but I shot the chance and went to see if my laptop memory would work and no its too small.. or no the PINS are aligned differently.. but DID in fact uncover ram slots... and just used Fabric Glue to Reseat the LCD.... fabric glue that was next to a bottle of harpie motors touchup paint.. when you take the LCD off there's like wifi cables that if your not careful would snap right off like the genius they are... but no im not bashing the quality.. so I guess thats about it is the discovery that its compressing all of its app memory and that you can't shut that off on Tahoe...  I think at least I think 

Edited April 12 by fspkwonx86

[MaLd0n]

[MakAsrock]

56 minutes ago, fspkwonx86 said:

well you'll be happy to hear its the 2017 iMac iMac 18,1? specifically its the non-ati Intel Iris Plus 640 Kabylake Model which has support for Tahoe except for: SMBIOS-CPU_INFORMATION is using CPUFriendDataProvider.. , AppleHDA but isnt that everyones problem, and Wi-Fi which BCMWLCompanion Fixes.. and obviously no SMBIOS-Platform-Support which OpenCore fixes.. Still correct that the GPU is stealing Ram in fact its probably using MORE on Tahoe... leading to lets look at Memory Statistics -> if all cached memory is compressed then -> is Specifically what apps are OPEN so its compressing literally all of the memory its using.. Split Wired and App Memory is an indicator of how much memory cannot be swapped or cached... this means that I suspect the GPU is using 2GB of System Ram..  So on a normal machine this wouldn't be an issue... and also perhaps on a System with 2 Ram Chips it also might not be... This is the lucky Mac that can have 2 ram chips and is compatible with 16GB ... but I shot the chance and went to see if my laptop memory would work and no its too small.. or no the PINS are aligned differently.. but DID in fact uncover ram slots... and just used Fabric Glue to Reseat the LCD.... fabric glue that was next to a bottle of harpie motors touchup paint.. when you take the LCD off there's like wifi cables that if your not careful would snap right off like the genius they are... but no im not bashing the quality.. so I guess thats about it is the discovery that its compressing all of its app memory and that you can't shut that off on Tahoe...  I think at least I think 

OK, I don't mind. I just looked at the profile and decided that the specified hardware imposes certain limitations. 😉

[Max.1974]

2 hours ago, deeveedee said:

@Max.1974No meu HP EliteBook 850 G7 da 10a geração (i7-10610U, sem dGPU, 15W->25W), o desempenho em 26.4.1 e 26.5 parece perfeitamente normal alguns minutos após a inicialização. Nos meus desktops de 65W de 8a e 9a geração (especialmente aqueles com dGPU), o "atraso" após a inicialização/login é quase imperceptível. Isso não me surpreende, porque as benchmarks do Geekbench 6 do meu laptop de 10a geração mostram que o desempenho da CPU e dos gráficos é menor do que o de um Desktop i5-8600 de 8a geração.

 

A tentativa da Intel de fazer uma CPU de baixo watt (15-25W) "paralisando" o desempenho da CPU garante uma boa duração da bateria, mas um desempenho inferior ao ideal.

 

EDITAR: Se eu não desligar meu laptop e, em vez disso, deixá-lo ocioso quando não estiver usando e eu o acordar para usá-lo, não experimento o atraso em Tahoe 26.4.1 e 26.5.

 

Thanks @Deeveedee My oldest laptop, an E470 with Kaby Lake, is still better than 10th Gen in some aspects.

But I really appreciate your information and the time you took to explain it.

Thank you. The desktop is much more responsive.  

😀

Update all family too 😅

 

 

 

Edited April 12 by Max.1974

[deeveedee]

7 hours ago, fspkwonx86 said:

does anyone think that installing 16gb of ram on a kabylake instead of the stock 8 is going to make the difference in speed ...

 

My testing of Tahoe on Coffeelake (next gen after Kabylake) indicates that at least 16GB RAM is best.  On the platforms that I tested (which accepted two SODIMMs), it is best to install two equally sized RAM modules (e.g., 2 x 8GB).  See here.  My memory recommendation is specific to the platforms that I tested, so you'll need to test on your platform(s).

Edited April 13 by deeveedee

[MaLd0n]

The power is on! 

[kgp]

Update: KDK 26.4.1  naming issue

 

Following my recent feedback to Apple regarding the typo in the Kernel Debug Kit (“Kernal” instead of “Kernel”), I have received a response indicating that the issue should now be resolved.

 

Apple’s reply:

“The spelling error should now be resolved.”

 

The current listing shows:
Kernel Debug Kit 26.4.1 (build 25E253)
and the package filename also appears to be corrected.

 

 

I have not yet tested whether this has any impact on automated mirroring or KDK detection.

 

Thanks to @deeveedee for pointing out the typo.

 

Cheers,
KGP

 

Update:

The Dortania mirror currently lists Kernel Debug Kit 26.4 (build 25E5233c)

 

 

In contrast, OCLP-Mod 3.1.9 detects this KDK correctly, while OCLP 3.0.0 Nightly (amfipassbeta variant) does not and instead falls back to Kernel Debug Kit 26.4 (build 25E246) as the closest match.

 

As a workaround, downloading and manually installing the new Kernel Debug Kit 26.4.1 (build 25E253) of Apple and subsequently applying the root patches resolved the KDK issue.

Edited April 16 by kgp

[SavageAUS]

Has anyone else found a very very slow update experience with 26.4 and 26.4.1? I am updating to 26.4.1 now and it says 3 hours and 59 minutes remaining?

Spoiler

 

[SavageAUS]

Also just seen about this OCLP-Plus? Is that preferred over the 3.0.0 Dortania version?

Secondly on the repo for OCLP-Plus there is a screenshot for a nice looking about this hack? Where can i get this one?

Spoiler

 

Edited April 18 by SavageAUS

[MakAsrock]

4 hours ago, SavageAUS said:

Also just seen about this OCLP-Plus? Is that preferred over the 3.0.0 Dortania version?

Secondly on the repo for OCLP-Plus there is a screenshot for a nice looking about this hack? Where can i get this one?

  Reveal hidden contents

 

For an AMD Hackintosh, you'll need some very complex settings, but otherwise, it lives here. 🤗
About This Hack Migration to SwiftUI lives here. 😉
Sorry I didn't find the link right away!

Edited April 18 by MakAsrock

[kgp]

1 hour ago, SavageAUS said:

Also just seen about this OCLP-Plus? Is that preferred over the 3.0.0 Dortania version?

Secondly on the repo for OCLP-Plus there is a screenshot for a nice looking about this hack? Where can i get this one?

  Reveal hidden contents

 

 

And general setup guidelines for all OCLP variants, including OCLP 3.0.0 Nightly, OCLP 3.0.0 Nightly (amfipassbeta variant), OCLP-Plus and OCLP-mod can be found here:

 

You just have to adopt them to your particular hardware setup.

 

Hope it helps somehow. 

Edited April 18 by kgp

[SavageAUS]

OCLP-Plus seems to be working just fine. WiFi is working as that’s all I need to patch. 
My biggest concern is the 3 hour update that doesn’t move. 

[MacNB]

1 hour ago, SavageAUS said:

... there is a screenshot for a nice looking about this hack? Where can i get this one?

 

You mean this one ?

https://github.com/perez987/About-This-Hack

 

It was forked by our very own expert @miliuco

[MakAsrock]

3 hours ago, MacNB said:

 

You mean this one ?

https://github.com/perez987/About-This-Hack

 

It was forked by our very own expert @miliuco

Thanks for the link. That's it. 👍

[robi62]

Hi guys I just updated my yoga 720 13ikb from Sequoia to Tahoe 26.4.1 but now I don't have internet ????

Does any of you tech expert know why im having this problem ??

Itwlm  Kext is loaded but heliport says is not ???

Never seen this before I enclose my config.plist

config 2tahoeplist.zip

Edited April 19 by robi62
more info

[robi62]

Seems like the update from Sequioa to Tahoe didnt go well 
I even tried OCLP with intel wifi and I get the same result.

Luckily it was done on usb disk and not the main one.

[kgp]

1 hour ago, robi62 said:

Seems like the update from Sequioa to Tahoe didnt go well 
I even tried OCLP with intel wifi and I get the same result.

Luckily it was done on usb disk and not the main one.

Hi my friend, 

Did you follow my guidelines for OCLP under Tahoe for Intel?

Did you use my EFI-Folder distribution as baseline to start with?

I am just in a PM with @dogansan attempting to make his Intel WI-FI BE200 work with OCLP under Tahoe.

You can contact me via PM to receive some help, but I have to finish first his setup. Thus, likely later night or tomorrow morning I could work on your issue. 

I would need your EFI-Folder, IOREG and pcidevices.txt from Hackintool (preferably via WeTransfer).

Also it would be interesting, which Intel Wi-Fi chipset you are using. Intel 8265/8275? Would be another Intel Chipset yet to be testet with OCLP.

Cheers,

KGP

 

P.S: OCLP posts would be more adequate in the respective thread. 😉 

 

Edited April 19 by kgp

[robi62]

@kgp Hi thanks for reply.

Im trying to make itwlm work in Tahoe but it seems that after many years of hackintoshing Im losing it. 

I know that this in not the right thread for OCLP  I was merely stating that even that with my present config which I amended for that purpose is not working .

That is why I uploaded my config from my Sequioa build which is for me working very well😊

[kgp]

2 minutes ago, robi62 said:

@kgp Hi thanks for reply.

Im trying to make itwlm work in Tahoe but it seems that after many years of hackintoshing Im losing it. 

I know that this in not the right thread for OCLP  I was merely stating that even that with my present config which I amended for that purpose is not working .

That is why I uploaded my config from my Sequioa build which is for me working very well😊

 

You’re welcome to send me a PM with the details I asked for. I’ll be happy to help you get OCLP working properly on your system under Tahoe.

I can start working on it tomorrow around noon. However, if you prefer using itlwm + HeliPort, others in the forum might be better suited to help with that specific setup.

It’s 00:53 here now — good luck and good night 🤗