[pre-release] macOS Tahoe 26.5

[kgp]

44 minutes ago, kaoskinkae said:

Thanks for the clarification. That's why my profile shows the three computers: New, Old1, and Old2 with the Wireless 3165. Therefore, I now know it's impossible and I'll continue using Heliport, which works perfectly. I'm closing this thread and have learned from your explanation.

 

I would not call it impossible.

We have seen cases where an Intel 7260 can be brought up with Broadcom BCM94360 spoofing under OCLP. In such setups, what really matters is the correct Broadcom spoofing rather than the original Intel chipset itself. In addition, you need to use AirportItlwm.kext 2.3.0 for Ventura as part of the setup.  You can give my guidelines a try and see how far you get. 😉

 

 

Take my Intel EFI folder distribution as a baseline and simply follow the respective guidelines.

 

Once you have everything properly set up, feel free to share your EFI folder — I’ll be happy to review it.

 

Further discussions should preferably take place in the Experimental Fork thread, not here in the 26.5 beta thread.

 

Edited April 14 by kgp

[kaoskinkae]

43 minutes ago, kgp said:

 

I would not call it impossible.

We have seen cases where an Intel 7260 can be brought up with Broadcom BCM94360 spoofing under OCLP. In such setups, what really matters is the correct Broadcom spoofing rather than the original Intel chipset itself. In addition, you need to use AirportItlwm.kext 2.3.0 for Ventura as part of the setup.  You can give my guidelines a try and see how far you get. 😉

 

 

Take my Intel EFI folder distribution as a baseline and simply follow the respective guidelines.

 

Once you have everything properly set up, feel free to share your EFI folder — I’ll be happy to review it.

 

Further discussions should preferably take place in the Experimental Fork thread, not here in the 26.5 beta thread.

 

If you can move the thread to its corresponding location, I'll send you the config.plist file for this OLD2 device. Thank you for your time.

 

 

config.plist

Edited April 14 by kaoskinkae

[kgp]

3 minutes ago, kaoskinkae said:

If you can move the thread to its corresponding location, I'll send you the config.plist file for this OLD2 device. Thank you for your time.

 

 

config.plist 31.56 kB · 0 downloads

 

Your config.plist is not set up correctly. You have neither implemented proper Broadcom spoofing nor the required AML for your Intel Wi-Fi.

If you like, we can continue this discussion via PM — I’ll be happy to help you get this sorted.

[kaoskinkae]

1 hour ago, kgp said:

 

Your config.plist is not set up correctly. You have neither implemented proper Broadcom spoofing nor the required AML for your Intel Wi-Fi.

If you like, we can continue this discussion via PM — I’ll be happy to help you get this sorted.

Thanks for your guide. With patience and by following the guide to the letter, I managed to get it activated.

[kgp]

On 4/14/2026 at 2:37 PM, kaoskinkae said:

Thanks for your guide. With patience and by following the guide to the letter, I managed to get it activated.

 

Happy that it worked out. 👍

I’ve reviewed your EFI and made some adjustments (attached below). I also added all kexts for Intel Bluetooth. 

I also removed your SMBIOS credentials so the EFI can be safely shared publicly.

Feel free to test it and let me know how it works on your system. 👍

 

 

For everybody with Intel W-Fi chipsets: Explanation of the SSDT and DeviceProperties setup

In this setup, it is important to clearly distinguish between the roles of DeviceProperties and the SSDT.

The actual “conversion” to a Broadcom-compatible device is performed via DeviceProperties (Broadcom spoofing). This is the key mechanism that allows macOS to properly attach and initialize the Wi-Fi stack.

The SSDT serves a different purpose. It injects an ARPT device at the correct ACPI path of the Wi-Fi controller and provides macOS-specific properties via _DSM (such as built-in, AAPL,slot-name, device_type, model, and name). This ensures that the device is properly represented within ACPI and IORegistry.

In summary:

-> DeviceProperties → performs the Broadcom spoofing (functional requirement)

-> SSDT → injects ARPT and ensures proper integration and representation (structural requirement)

Both components are required for a clean and working setup.

It is also important to note:

-> The ACPI path is not universal and must be adapted to the individual system (IOREGExplorer)

-> The PCI DeviceProperties path is also not universal and must match the actual hardware layout (Hackintool/PCI)

If either path is incorrect, the setup will not work as expected.

 

 

EFI-final.zip

Edited April 15 by kgp
Adding final EFI

[Alpha22]

[ANTIKO]

It's alright

Spoiler

 

Edited April 14 by ANTIKO

[deeveedee]

Fast and easy incremental update from Tahoe 26.5 Beta 1 -> Beta 2. I'm using VoodooHDA.kext 3.3.4 with SIP csr-active-config = <01000000> for audio and itlwm/Heliport for Intel Wi-Fi, so no root patches and nothing to uninstall/re-install.

 

[deeveedee]

12 hours ago, hiphopboy said:

the 26.5 beta 2 fixed grey screen and slow loading desktop on last build

Time from login to desktop is MUCH faster on my HackBookPro16,2.  Pleased to see that macOS Tahoe is still getting better for Intel platforms.

[deeveedee]

@Max.1974 Isn't that 26.5 Beta 1?

 

Edited April 15 by deeveedee

[Max.1974]

57 minutes ago, deeveedee said:

@Max.1974 Isn't that 26.5 Beta 1?

 

Yes, you’re right — sorry about that. I was referring to Beta 1, and the installer hasn’t been fully released yet.

 

 

 

Now I will update beta 2 

 

 

 

 

Sorry, my mistake 

Edited April 15 by Max.1974

[Max.1974]

Now is good 🤣

 

[Zevgoli]

Very good update.  Smoother than normal.  I thought I'd provide proof for once.  🙂

 

Cheers, Howard

 

EDIT.  I'm very very very annoyed.  After working fine since the update I got this morning the...Your update to Tahoe has been completed...click continue rubbish.  Unable to move past or get rid of these screens.  I had to reinstall the drive with my USB stick which now seems to work but I am back to 26.4.1.

 

Here I will stay.  ARRRRGH!

 

 

 

Edited April 16 by Zevgoli

[hiphopboy]

On 4/15/2026 at 3:58 AM, deeveedee said:

Time from login to desktop is MUCH faster on my HackBookPro16,2.  Pleased to see that macOS Tahoe is still getting better for Intel platforms.

 

yup, intel is the best :v 

[deeveedee]

1 hour ago, hiphopboy said:

 

yup, intel is the best :v 

I wouldn't go as far as to say Intel is the best 🤣, but definitely good enough for now.  Intel really screwed up by repeated delays that allowed TSMC to take the lead.  The Intel "upgrades" from 8th gen -> 9th -> 10th really weren't upgrades at all and Apple was smart to move on with their own ARM-based architecture.  I'm glad that Intel got us this far and I am looking forward to my first Apple silicon Mac.

[kgp]

Update: KDK behaviour on macOS 26.5 beta 2

 

After further testing, both OCLP 3.0.0 Nightly and OCLP-Mod 3.1.9 show identical behavior regarding KDK selection on macOS 26.5 beta 2 (build 25F5053d).

 

Even with the following KDKs installed:

Kernel Debug Kit 26.5.1 beta 1 (25F5042g)

Kernel Debug Kit 26.4.1 (25E253)

Kernel Debug Kit 26.4 (25E246)

 

both patchers consistently fall back to:

-> Kernel Debug Kit 26.4 (build 25E246)

 

Removing 25E246 results in it being re-downloaded automatically, rather than switching to a newer available or installed KDK.

 

Conclusion:
This behaviour appears to be consistent across different OCLP implementations and suggests that 25E246 is currently the preferred or enforced fallback KDK for macOS 26.5 beta 2.

 

Despite this, root patching works as expected with this KDK.

 

Cheers,
KGP

 

Note: Feedback has been submitted to Apple regarding the KDK versioning inconsistency on macOS 26.5.

Edited April 16 by kgp
Adding Note

[dogansan]

Hi to all,

I was away from the recent updates for a while. I had made my last update on Tahoe 26.4 and stationed for some time as I had focused on Linux. Yesterday , I decided update to 26.5 beta 2 , I usually prefer partial OTA updates but as my Whatevergreen kext was active and update offered me full  and I decided to make it off to receive partial. While playing with beta update button and switiching between beta and developer option , the options totally dissappeared and it now only shows off. I am beta and developer regiistered. But whatever I tried these options never came back.  Does anybody knows how to bring back these beta update options via command line or any tricky method ?  Any idea is appreciated.

[Matgen84]

4 hours ago, dogansan said:

Hi to all,

I was away from the recent updates for a while. I had made my last update on Tahoe 26.4 and stationed for some time as I had focused on Linux. Yesterday , I decided update to 26.5 beta 2 , I usually prefer partial OTA updates but as my Whatevergreen kext was active and update offered me full  and I decided to make it off to receive partial. While playing with beta update button and switiching between beta and developer option , the options totally dissappeared and it now only shows off. I am beta and developer regiistered. But whatever I tried these options never came back.  Does anybody knows how to bring back these beta update options via command line or any tricky method ?  Any idea is appreciated.

 

Do you try this: Your Mac must be signed in with the Apple Account you use to sign into to the Apple Developer website in order to access the beta software. (source Apple).

[dogansan]

5 hours ago, Matgen84 said:

 

Do you try this: Your Mac must be signed in with the Apple Account you use to sign into to the Apple Developer website in order to access the beta software. (source Apple).

Thanks for the comment. I have already tried it, I had registered to both beta and developer websites and this time I tried signing into both sides but it did not change the situation.

[turko35408]

👍

 

[HyperX7]

[dogansan]

On 4/17/2026 at 9:38 AM, dogansan said:

Hi to all,

I was away from the recent updates for a while. I had made my last update on Tahoe 26.4 and stationed for some time as I had focused on Linux. Yesterday , I decided update to 26.5 beta 2 , I usually prefer partial OTA updates but as my Whatevergreen kext was active and update offered me full  and I decided to make it off to receive partial. While playing with beta update button and switiching between beta and developer option , the options totally dissappeared and it now only shows off. I am beta and developer regiistered. But whatever I tried these options never came back.  Does anybody knows how to bring back these beta update options via command line or any tricky method ?  Any idea is appreciated.

Update :  I found the solution by switching from iMacpro1.1 to iMac7.1 . The beta updates are now shown and I did incremental update to 26.5 beta 2.

Edited April 19 by dogansan

[strangeron]

 

Edited April 20 by strangeron

[kgp]

Fast and painless sequential OTA update (3,7 GB) from macOS 26.5 beta 2 to macOS 26.5 beta 3 (25F5058e) 

 

 

 

 

There is no KDK for macOS 26.5 beta 3 (25F5058e) yet.

 

Again, having manually installed on my system:  

KDK_26.4_25E246.kdk, 

KDK_26.4.1_25E253.kdk and

KDK_26.5_25F5042g.kdk,

OCLP chooses KDK_26.4_25E246.kdk as the closest match.

 

 

AppleHDA, Wi-Fi and AWDL continue working flawlessly

 

 

 

Edited April 20 by kgp

[deeveedee]

Very easy update from Tahoe 26.5 Beta 2 -> Beta 3.  Since I have BluetoolFixup.kext disabled, the unattended, incremental update was uneventful and fast.  With VoodooHDA.kext 3.3.4 for audio and itlwm/Heliport for Intel Wi-Fi, there are no additional steps and everything appears to be working perfectly.

 

Incremental Update

Spoiler

 

Edited April 20 by deeveedee