[Release] macOS Tahoe 26.5

[obus]

Update fast and smooth. No hiccups and fast as on my MacMini M4

[taranta babu]

10 hours ago, Matgen84 said:

 

Hi @taranta babu Could you put details of your hardware in your signature, please. Actually, users who can help doesn't know what are your CPU, mobo, wireless, ethernet, graphic card, etc...

 

Did it , thank you 🙏

[Matgen84]

15 hours ago, taranta babu said:

Did it , thank you 🙏

 

Thank to you. Can you precise your onboard wifi chipset and ethernet, please. 😊

[taranta babu]

24 minutes ago, Matgen84 said:

 

Thank to you. Can you precise your onboard wifi chipset and ethernet, please. 😊

I've updated my signature. I didn't have this problem when using Sequoia, and when I switched to Tahoe, I updated the EFI accordingly and didn't try using Ethernet. For a while, I continued using OCLP with Fenvi 919, but I completely abandoned it because it interfered with some programs. Afterwards, I started using Heliport and itlwm. There are no problems with that; it works normally. A situation arose that required me to use Ethernet, and although there were no problems with the connection or speed, random resets started. I revised the DMAR.aml file and did some testing; it seems more stable now, but I'm monitoring it. In Kernel Quirks, when DisableIoMapper is true, the internet works, but when it's set to false, neither Ethernet nor heliport works. In this case, vtd is visible; if disableIoMapper is false, vtd is never visible in IORegistryExplorer.

[deeveedee]

@taranta babu In macOS Tahoe, I need "Kernel > Quirks > DisableIoMapper = True" when using itlwm/heliport.  

 

Network behavior did change in macOS Tahoe, so what was working for you in Sequoia may not work the same way in Tahoe.  It is possible that with Tahoe on your motherboard, you will not be able to have Wi-Fi and Ethernet working simultaneously.

[Max.1974]

On 5/15/2026 at 12:36 PM, taranta babu said:

I have a problem; I've been using ITLWM and Heliport for a long time. When I try to use Ethernet, It  randomized restarts. I've tried many things but haven't found a solution. My motherboard is an Asus Tuf Gaming Z790 Wi-Fi D4. I'm attaching the EFI folder here. Does anyone know the solution? @MaLd0n

 @Max.1974

 

https://www.mediafire.com/file/x4b8qh3isc3bllh/EFI.zip/file

 

I need you to report or put into a report the error that occurs, your motherboard BIOS, and your configuration. It does not seem to be an error with your EFI, at least not regarding this HeliPort issue not working. Are you using OpenCore Legacy Patcher? Any Wi-Fi card different from 6E? Is your wireless card listed on the  IntelOpenWireless page? 

[Max.1974]

@taranta babu try this Kext

 

https://www.mediafire.com/file/ht9xx84zw046r1h/itlwm.kext.zip/file 

[Max.1974]

And im tested your Kext, no errors, all fine here...

 

 

 

 

 

[taranta babu]

2 hours ago, Max.1974 said:

@taranta babu try this Kext

 

https://www.mediafire.com/file/ht9xx84zw046r1h/itlwm.kext.zip/file 

Thank you @Max.1974 @deeveedee @Matgen84. The main problem was random resets. I recompiled the Dmar.Aml file and set DisableIoMapper = True, and now both the Heliport and Ethernet are working and haven't reset yet. The problematic issue wasn't showing up in VTD IORegistryExplorer, but I thought it was a common problem, and now if it doesn't reset, we can say the issue is resolved.🙏

[Max.1974]

Nice  

[deeveedee]

@taranta babu Glad it's working for you.  Do you still need to replace the DMAR table with DisableIOMapper=True?  I didn't think DMAR table replacement was necessary with DisableIOMapper=True / VTD Disabled.  It's not my area of expertise, so anything you or anyone else can share to help learn is appreciated.

[AlfredoM]

On my newly built Hackintosh featuring the GA Z390 Designare (my first damn Gigabyte board!!), there is only *one* internal USB header—and at this price point, no less.

Another downside compared to the MSI motherboards I’ve used for decades is the presence of those stupid USB hubs built directly onto the board; this prevents you from

individually mapping the ports using Hackintool-USB—a process that worked flawlessly on all my previous MSI boards.

 

I bought this piece-of-junk Gigabyte board solely for the onboard Thunderbolt 3 support. That feature didn't work quite right on my previous MSI Z370 A Pro setup,

which used an external PCIe GC Alpine Ridge card; on that system, only one of the two Thunderbolt ports on the PCIe card was functional.

 

Okay, so on this lousy Gigabyte board, I can at least utilize both Thunderbolt 3 ports—that is literally the *only* positive thing about this Gigabyte board.

I haven't encountered any issues with Bluetooth, Wi-Fi, or audio (Apple HDA); everything works flawlessly using the OCLP-Mod 3.9.1 by laobamac.

 

In contrast, when using Dortania 2.4.1—or even OCLP 3.2.2 Plus—I could only restore audio functionality, but not Wi-Fi via the Airportitlwm.kext driver.

And as for that stupid itlwm.kext—which doesn't provide "true" Wi-Fi and works *only* when paired with an Ethernet connection—I refuse to use it.

 

I wanted a standalone Wi-Fi solution that works independently of Ethernet, and now, finally, I have it.

[HurricaneX]

 

 

[deeveedee]

I've mentioned this before, so I'm repeating test findings based on recent testing:  If you are finding that your Radeon Polaris graphics performance is less than expected in macOS Tahoe 26.5 and you haven't performed a clean installation of Tahoe for a while, you may want to try installing Tahoe 26.5 in a new APFS volume.  

 

I have multiple Tahoe volumes on my hack with Radeon RX 560x.  In one of the volumes, I have been performing incremental updates since Tahoe was first released.  GeekBench 6 Metal benchmarks in this incrementally-updated volume are consistently around 18K.

 

I have two other APFS volumes (on the same NVMe SSD) that I installed as follows: one is a clean installation of Tahoe 26.4 and incrementally upgraded to 26.5 and the other is a clean installation of 26.5.  GeekBench 6 metal benchmarks in these two Tahoe volumes is consistently ~24K - a 33% metal performance improvement over the Tahoe volume that has been incrementally updated from Tahoe's first release.

 

I am booting all three of these test volumes with the same EFI and they are all located in a container on the same NVMe SSD.

 

EDIT: All tests are performed with the same version of GeekBench 6 (6.7.1)
 

Spoiler

 

Edited May 20 by deeveedee

[arsradu]

Just wanted to share my experience with 26.5 update from Sequoia. Unintentional update, but that's beside the point.

 

By the way, is there really no way to make MacOS give you ONLY updates for current OS (Sequoia in this case) instead of pushing Tahoe upon you and installing it on next reboot like Windows does? What the hell! Maybe I just want to stay on Sequoia forever! Cause I just find it better, more responsive, and, arguably, more esthetically pleasing than Tahoe! Why is there no option to just say: DON'T install updates for newer operating systems but DO give me incremental updates for the current one? Why is it so hard to do?!

 

Anyway, I just wanted to say that, despite the forced update, for the first time since testing Tahoe, I was also forced to activate FieVault. Again, WHY is there no option to just say NO from the very beginning?! I thought that, if FileVault was turned off on Sequoia, it will continue to be off after that upgrade. But nooo. Apple decided to activate it for me, with no option to disable it until I'm into the OS.

 

Luckily no issues with that. Surprisingly enough for me, FileVault is apparently working flawlessly on my machine. Even on Tahoe. But it was still frustrating that I had to first wait for it to finish encrypting (no way to stop it apparently, and probably not recommended either), just to disable it.

 

Other than that, and the fact that, due to new implementations in Tahoe, some menus are significantly slower to load, all good with this update.

[Thebes Knossos]

I've put this setting, so no unwanted updates. Sorry capture is in french language. 

 

[Slice]

5 hours ago, arsradu said:

Just wanted to share my experience with 26.5 update from Sequoia. Unintentional update, but that's beside the point.

 

By the way, is there really no way to make MacOS give you ONLY updates for current OS (Sequoia in this case) instead of pushing Tahoe upon you and installing it on next reboot like Windows does? What the hell! Maybe I just want to stay on Sequoia forever! Cause I just find it better, more responsive, and, arguably, more esthetically pleasing than Tahoe! Why is there no option to just say: DON'T install updates for newer operating systems but DO give me incremental updates for the current one? Why is it so hard to do?!

 

Anyway, I just wanted to say that, despite the forced update, for the first time since testing Tahoe, I was also forced to activate FieVault. Again, WHY is there no option to just say NO from the very beginning?! I thought that, if FileVault was turned off on Sequoia, it will continue to be off after that upgrade. But nooo. Apple decided to activate it for me, with no option to disable it until I'm into the OS.

 

Luckily no issues with that. Surprisingly enough for me, FileVault is apparently working flawlessly on my machine. Even on Tahoe. But it was still frustrating that I had to first wait for it to finish encrypting (no way to stop it apparently, and probably not recommended either), just to disable it.

 

Other than that, and the fact that, due to new implementations in Tahoe, some menus are significantly slower to load, all good with this update.

It is not hard to do. Set SMBIOS iMac19,1 and you will get updates for Sequoia and never for Tahoe.

[arsradu]

9 minutes ago, Slice said:

It is not hard to do. Set SMBIOS iMac19,1 and you will get updates for Sequoia and never for Tahoe.

Ah, so basically downgrade the SMBIOS to something that has max OS version: Sequoia. Yeah, that makes sense. I don't know why it didn't cross my mind. :)) Easy fix.

 

Well, in this case, it did help, cause I could see what happens when you upgrade from Sequoia to Tahoe (even if it was unintentional). :)) And I could also see that FileVault was working fine. But yeah, good to know.

 

Thank you!

4 hours ago, Thebes Knossos said:

I've put this setting, so no unwanted updates. Sorry capture is in french language. 

 

 

Yeah, but I think this will not show you any updates... So not only the ones for newer OS, but even for current one. Which is not what I'm looking for. I do want updates for Sequoia. I just don't want to be prompted to upgrade to Tahoe.

 

For that, looks like the solution is to downgrade the SMBIOS to one that only has Sequoia as max available version.

Edited May 21 by arsradu

[vrondena]

Greetings to everyone, I'm not sure it's relevant in this topic, but also in general, the question is if I update from Sequoia to Tahoe my serial, mlb, uuid and rom are updated to the higher version or not, I wouldn't want to miss the message and face time services. I'm referring to a Mac Apple and another Hack pc. Thank you for your answer

[deeveedee]

@vrondena Without knowing anything about your hack, this is just an uneducated suggestion: Before you change your SMBIOS, see this.  You should be able to boot Tahoe with an unsupported SMBIOS if you add boot-arg -no_compat_check or the "Skip Board ID" booter patch.

Edited May 21 by deeveedee

[arsradu]

52 minutes ago, vrondena said:

Greetings to everyone, I'm not sure it's relevant in this topic, but also in general, the question is if I update from Sequoia to Tahoe my serial, mlb, uuid and rom are updated to the higher version or not, I wouldn't want to miss the message and face time services. I'm referring to a Mac Apple and another Hack pc. Thank you for your answer

No. Those are not updated with the newer OS. But yeah, you should check to see if the SMBIOS you're currently using is also supported by Tahoe.

 

If it is, you can just start the update (I would install it on a separate partition though). At least for testing. Just to make sure everything still works after the upgrade. If it does, then you can also upgrade your main partition. Aaaand, i would also recommend creating a Time Machine backup of the Sequoia data before upgrading. Just in case you might want to go back.

If it's not, you have two options:
1. upgrade SMBIOS to a compatible one (make sure you keep MLB, ROM, UUID intact if you do decide to go this route)
2. as deeveedee said above, use -no_compat_check boot arg, which should allow you to boot without changing the SMBIOS.

Edited May 21 by arsradu

[vrondena]

Thanks for the answers, I'll do some tests with your suggestions and I'll update you. If you're interested in the result

[arsradu]

@vrondenaIf you're attempting to do it on the XPS 13 in your signature, definitely don't do it on the main partition. I'm not 100% sure what's the current status of development, but I think you might need OCLP with graphics patches if you want to get video acceleration, which, as far as I know, is not available yet (for Tahoe). So....definitely don't install it on your main partition.

At least until you can confirm everything’s working and especially if it’s actually working.

Edited May 21 by arsradu

[strangeron]

If the same EFI is used for Sequoia and Tahoe (MacPro 7.1); and macOS Sequoia Developer beta is selected for Sequoia Beta updates, you will only receive Sequoia updates.

[vrondena]

Update, it doesn't work ... at least it starts but they need the right data not migration for the services