[pre-release] macOS Tahoe 26.5

[Pc Bacabal]

13 minutes ago, jlrycm said:

Refer to this guide which provides some guidance on how to use this OpenCore fork

 

https://github.com/5T33Z0/OC-Little-Translated/blob/main/Content/O_OC_NO_ACPI/README.md

Thanks!

[kgp]

21 hours ago, deeveedee said:

EDIT2: I'm leaving the post below, but the video stream just froze on remote TV.  Some video works and some is frozen.  I wonder if this has anything to do with DRM?  ... This is definitely a content-specific issue.  Some streaming content that I watch works perfectly.

 

=========================================================

 

Sorry for what is probably a remedial post, but I just experienced a pleasant surprise on my HackBookPro16,2 running Tahoe 26.5 (25F71) with Intel Wi-Fi (itlwm).  Screen mirroring to Apple TV works perfectly.  That may seem trivial to some, but I had never tried it.  No root patches - just Intel Wi-Fi with Open Wireless itlwm and Screen Mirroring works perfectly.

 

In this case, I'm streaming live TV in Firefox from my hack to Apple TV with excellent video / audio quality.

 

 

EDIT: A couple of observations (probably remedial to someone who has experience with Screen Mirroring):

• The picture on the remote TV is more vibrant than the picture on my laptop internal display
• Audio on the remote TV is controllable via the Volume slider in my hack's menu bar

 

Note that I am using VoodooHDA.kext 3.3.4 for Tahoe audio on my hack (to eliminate the need for root patches), but this has no impact on the audio cast via Screen Mirroring.

 

Interesting observation that Screen Mirroring works with itlwm and HeliPort under Tahoe, although I use native AirPlay for video and audio streaming between my hack and other devices.

Edited May 7 by kgp

[kgp]

11 hours ago, MaLd0n said:

This OC is from https://github.com/daliansky/OpenCore_Patch_Build

This version don't inject nothing on Windows or Linux 

 

[kgp]

On 5/5/2026 at 7:41 PM, dogansan said:

@deeveedee , yess , it was the I just made SetApfsTrimTimeout = 0 in my original EFI as it is in @MaLd0n's second EFI  and it now boots in 12 seconds and surely I kept functionality of my Intel BE200 wifi. It is fascinating while I don't know the funtion of this . Thank you

I checked from AI it says this disables the trim function during boot to speed up the boot, so it recommends to chnage it to -1 once a month. Funny

 

SetApfsTrimTimeout = 0 also significantly reduces boot time on my production systems using Samsung EVO 960 and EVO 970 NVMe SSDs - by roughly 30 seconds in my case.

 

Especially the short stalls around the AMFI/dyld “simulator status...” phase during boot are practically gone now. However, I am still investigating the trade-off between boot speed and long-term system stability.

 

Edit: With SetApfsTrimTimeout = 0, the long-term stability of my systems however has noticeably decreased compared to the rock-solid behaviour I had over several months before.

 

Within only 24 hours of testing, I experienced one crash immediately upon login after boot and another one after wake from sleep.

 

Back to SetApfsTrimTimeout = -1 for now. 

Edited May 7 by kgp

[dogansan]

4 hours ago, kgp said:

 

SetApfsTrimTimeout = 0 also significantly reduces boot time on my production systems using Samsung EVO 960 and EVO 970 NVMe SSDs.

 

Especially the short stalls around the AMFI/dyld “simulator status...” phase during boot are practically gone now. However, I am still investigating the trade-off between boot speed and long-term system stability.

 

Edit: With SetApfsTrimTimeout = 0, the long-term stability of my systems has noticeably decreased compared to the rock-solid behaviour I had over several months before.

 

Within only 24 hours of testing, I experienced one crash immediately upon login after boot and another one after wake from sleep.

 

Back to SetApfsTrimTimeout = -1 for now. 

I had also observed this  short stalls around the AMFI/dyld “simulator status with SetApfsTrimTimeout = -1 ,  but I wasn't sure if it is relevant or not . I will share my experience with 0 if anything bad happens 😕

[MaLd0n]

10 hours ago, Pc Bacabal said:

How to use this OC?

1- Enable DEV in Edit menu on OCAuxiliaryTools

2- Go to Updates

3- Add this adress there https://github.com/daliansky/OpenCore_Patch_Build

4- Get OpenCore

5- Start Sync

7 hours ago, kgp said:

 

???

[Vasya Katanyan]

On 5/5/2026 at 1:18 PM, kgp said:

 

May I ask which Intel Wi-Fi chipset you are using? Just to see if I can add another one to the list of supported devices.. 

I assume you are using OCLP 3.0.0 Nightly (amfipassbeta variant) + AirportItlwm.kext (Ventura) + Broadcom spoofing..

You're absolutely right.

[kgp]

38 minutes ago, Vasya Katanyan said:

You're absolutely right.

 

May I ask again which Intel Wi-Fi chipset you are using? 😉

 

So far we had success with the Intel 7260, Intel AX210, Intel 3165 and Intel BE200.

 

Thanks in advance for the small additional info!

Edited May 7 by kgp

[kgp]

7 hours ago, MaLd0n said:

???

 

My screenshot (question) was actually related to the highlighted upstream OpenCorePkg commit for OC 1.0.8:

 

“fix: add Windows-friendly macrecovery invocation”

 

I was simply wondering whether this change is conceptually similar to the Windows/Linux handling already present in the daliansky/OpenCore_Patch_Build version you referenced — i.e. avoiding unnecessary injection or interference with non-macOS systems.

 

Sorry for not being more explicit earlier. 😉

 

Edited May 7 by kgp