[Release] macOS Tahoe 26

[tlac]

8 hours ago, jlrycm said:

@tlac my new plan is to try the new Broadcom kext developed by @Austere.J using a BCM943602CS card which is supposed to be compatible. Hopefully this will allow me to have both wifi and Ethernet since this new kext and I-225V would co-exist with Apple VT-D enabled.

 

I have no space to install any additional cards and I probably can’t change the Wi-Fi chip either since it uses the CNVi protocol (Gigabyte Z490i).

I can live without Apple VT-d because I can to set up both Intel Wi-Fi and i225-V without it. Also, I’ve tried running an older macOS using free VMware Fusion and it's working.

 

Spoiler

 

Edited October 5, 2025 by tlac

[Thebes Knossos]

Le 05/10/2025 à 02:11, AlfredoM a dit :

Ne vous plaignez pas, je sais que c'est hors sujet.

 

J'ai un problème avec l'application « Télécharger le programme d'installation complet ».

 

Un téléchargement de 15.7.1 s'est arrêté à 16 Go, et maintenant ma partition macOS n'affiche que 26 Go car les 16 Go téléchargés occupent toujours de l'espace.

 

Question : Où le programme d’installation complet « Télécharger » enregistre-t-il les téléchargements ?
Je vais dans Utilisateurs/Bibliothèque/Support d'application et je ne vois rien concernant « Télécharger le programme d'installation complet ».

Merci pour ce petit conseil. Je souhaite installer Sequoia 15.7.1 sur un autre Mac aujourd'hui.

 

Merci pour cette aide peu amicale... mais je l'ai trouvé moi-même 😞

Have you done a reboot since ? Some times not finished thing goes in /tmp and are cleaned at reboot. If not found, install GtandPerspective from sourceforge to search it.

[Big_Aziz]

17 hours ago, tlac said:

I have no space to install any additional cards and I probably can’t change the Wi-Fi chip either since it uses the CNVi protocol (Gigabyte Z490i).

I can live without Apple VT-d because I can to set up both Intel Wi-Fi and i225-V without it. Also, I’ve tried running an older macOS using free VMware Fusion and it's working

when AppleIGC.kext is enabled and running

Spoiler

 

AppleIGC.kext is required to install the operating system and access the desktop. After successfully accessing the desktop, I always disable AppleIGC.kext. The system uses the default kext from Apple.  By default, DisableloMapper and DisableloMapperMapping are disabled in my system for booting. Everything works fine in Sequioa: Wi-Fi, Bluetooth, applevtd. To boot the Tahoe system, I chose the same settings, and as expected, everything works except Wi-Fi. For Wi-Fi to work properly in Tahoe, I need to enable DisableloMapper and DisableloMapperMapping, and I need AppleIGC.kext.

in Sequioa

Spoiler

 

Edited October 6, 2025 by Big_Aziz

[Big_Aziz]

In Tahoe

 

Spoiler

I do most of my work in the Sequioa operating system, and everything works fine there. Let's wait until they fix everything and release new driver versions for the Tahoe operating system.

Edited October 6, 2025 by Big_Aziz

[mnfesq]

On 9/23/2025 at 4:03 PM, mnfesq said:

I screwed up my test partition with Tahoe on it and decided to install it from scratch. I tried two different methods: installing to the Tahoe partition from my Sequoia partition and using the Tahoe recovery partition to install it to the Tahoe partition.  Each time it installed perfectly. Then I rebooted and got the symbol which translates to "you're screwed".  See the photo below.

 

 

Is there an easy fix for this in OC config or a bootarg I should be using for a fresh installation?  BTW, I am using a supported SMBIOS - MBP16,4.

 

I finally figured out was causing me to get to this screen after successfully installing Tahoe (any version).  The problem was file vault.  File vault was encrypting my drive and I tried to install the root patches with OCLP-Mod during the encryption process. What I did to resolve the problem was wait until the encryption process was completed, then turn off file vault and wait for the decryption process to be completed.  Then I could successfully install the OCLP-Mod root patches in order to get sound and USB WiFi to work.

 

Of course, I had already screwed up my system drive so I had to do all this while in recovery mode.  It also worked when I was booted into another macOS installation on the same laptop using Terminal to monitor the process and set File Vault to decrypt the drive after it finished encrypting. (It won't start to decrypt until it is finished encrypting.)

 

Here's the Terminal commands I used:

 

diskutil apfs list  -- This allows you to see which disk is being encrypted/decrypted and the percentage of completion.

 

Once the drive is fully encrypted, to decrypt the drive, I used these commands:

 

diskutil apfs list -- Find your drive that you want to decrypt in the list in the format of diskXs1 where X is the number of the disk you want to decrypt.

 

diskutil apfs UnlockVolume /dev/<volume-identifier>  -- where <volume-identifier> is in the format of diskXs1

 

diskutil apfs listcryptousers /dev/<volume-identifier> -- Use the same <volume-identifier> as you did in the preceding command.

 

diskutil apfs decryptVolume /dev/<volume-identifier> -user <UUID>  -- Once you enter the preceding command, you will see a list of two UUIDs.  Only one of the two will work to start the decryption process.  If the first one you choose doesn't work, try the other. The decryption process should then commence.  

 

diskutil apfs list -- This will allow you to monitor the percentage of completion of the decryption process. Be aware that it can take several hours to complete depending on the size of the drive you are decrypting.

[AlfredoM]

5 hours ago, mnfesq said:

 

I finally figured out was causing me to get to this screen after successfully installing Tahoe (any version).  The problem was file vault.  File vault was encrypting my drive and I tried to install the root patches with OCLP-Mod during the encryption process. What I did to resolve the problem was wait until the encryption process was completed, then turn off file vault and wait for the decryption process to be completed.  Then I could successfully install the OCLP-Mod root patches in order to get sound and USB WiFi to work.

 

Of course, I had already screwed up my system drive so I had to do all this while in recovery mode.  It also worked when I was booted into another macOS installation on the same laptop using Terminal to monitor the process and set File Vault to decrypt the drive after it finished encrypting. (It won't start to decrypt until it is finished encrypting.)

 

Here's the Terminal commands I used:

 

diskutil apfs list  -- This allows you to see which disk is being encrypted/decrypted and the percentage of completion.

 

Once the drive is fully encrypted, to decrypt the drive, I used these commands:

 

diskutil apfs list -- Find your drive that you want to decrypt in the list in the format of diskXs1 where X is the number of the disk you want to decrypt.

 

diskutil apfs UnlockVolume /dev/<volume-identifier>  -- where <volume-identifier> is in the format of diskXs1

 

diskutil apfs listcryptousers /dev/<volume-identifier> -- Use the same <volume-identifier> as you did in the preceding command.

 

diskutil apfs decryptVolume /dev/<volume-identifier> -user <UUID>  -- Once you enter the preceding command, you will see a list of two UUIDs.  Only one of the two will work to start the decryption process.  If the first one you choose doesn't work, try the other. The decryption process should then commence.  

 

diskutil apfs list -- This will allow you to monitor the percentage of completion of the decryption process. Be aware that it can take several hours to complete depending on the size of the drive you are decrypting.

As they always say, "schadenfreude is the best kind of joy."
Serves you right, why are you using that stupid file vault !!!

[chris1111]

5 hours ago, mnfesq said:

 

I finally figured out was causing me to get to this screen after successfully installing Tahoe (any version).  The problem was file vault.  File vault was encrypting my drive and I tried to install the root patches with OCLP-Mod during the encryption process. What I did to resolve the problem was wait until the encryption process was completed, then turn off file vault and wait for the decryption process to be completed.  Then I could successfully install the OCLP-Mod root patches in order to get sound and USB WiFi to work.

 

Of course, I had already screwed up my system drive so I had to do all this while in recovery mode.  It also worked when I was booted into another macOS installation on the same laptop using Terminal to monitor the process and set File Vault to decrypt the drive after it finished encrypting. (It won't start to decrypt until it is finished encrypting.)

 

Here's the Terminal commands I used:

 

diskutil apfs list  -- This allows you to see which disk is being encrypted/decrypted and the percentage of completion.

 

Once the drive is fully encrypted, to decrypt the drive, I used these commands:

 

diskutil apfs list -- Find your drive that you want to decrypt in the list in the format of diskXs1 where X is the number of the disk you want to decrypt.

 

diskutil apfs UnlockVolume /dev/<volume-identifier>  -- where <volume-identifier> is in the format of diskXs1

 

diskutil apfs listcryptousers /dev/<volume-identifier> -- Use the same <volume-identifier> as you did in the preceding command.

 

diskutil apfs decryptVolume /dev/<volume-identifier> -user <UUID>  -- Once you enter the preceding command, you will see a list of two UUIDs.  Only one of the two will work to start the decryption process.  If the first one you choose doesn't work, try the other. The decryption process should then commence.  

 

diskutil apfs list -- This will allow you to monitor the percentage of completion of the decryption process. Be aware that it can take several hours to complete depending on the size of the drive you are decrypting.

What is your USB Wifi adapter brand?

[mnfesq]

2 hours ago, AlfredoM said:

As they always say, "schadenfreude is the best kind of joy."
Serves you right, why are you using that stupid file vault !!!

 

Not by choice. I never had the option to turn it off during installation. (BTW, your comment was not appreciated and contributed nothing to this forum.)

 

2 hours ago, chris1111 said:

What is your USB Wifi adapter brand?

 

ASUS USB-AC53 AC1200 Nano USB Dual-Band Wireless Adapter USB-WIFI

Edited October 7, 2025 by mnfesq

[chris1111]

19 minutes ago, mnfesq said:

ASUS USB-AC53 AC1200 Nano USB Dual-Band Wireless Adapter USB-WIFI

Works good?

[mnfesq]

13 minutes ago, chris1111 said:

Works good?

 

It's definitely not as fast as my pci-e Broadcom chip but it's good enough to use on my system drive.  When I need to download a macOS update, I plug in an ethernet cable.

 

 

[LockDown]

All good here

[strangeron]

No problem.

[ANTIKO]

14 hours ago, eSaF said:

Не знаю, уместно ли здесь комментировать эту тему.

Кто-нибудь заметил проблему с Microsoft Mail на macOS?

 

Вход в систему через Safari или любой другой браузер на Tahoe возможен, но на Mac в качестве почтового клиента — нет.

Учетная запись Outlook.com, которую я использовал в течение многих лет как на Windows, так и на Mac, теперь приводит к появлению прикрепленного всплывающего окна.

 

Я даже сменил пароль, думая, что это повреждение связки ключей, но раздражающее всплывающее окно все равно появилось.

То же самое происходит и на всех остальных версиях macOS на этом устройстве: Tahoe, Sequoia и Sonoma.

 

С тех пор я узнал, что то же самое происходит и на настоящих компьютерах Mac, судя по некоторым сообщениям на MacRumors.

Кажется, старая проблема снова подняла голову.

 

Честно говоря, аккаунт Exchange не является для меня повседневным инструментом, как аккаунт Google, но он самый старый.

На данный момент я буду бороться с Outlook со стороны Windows, пока не будет предложено исправление или объяснение.

All right

Spoiler

 

[kgp]

2 hours ago, eSaF said:

Don't know if this is the correct place to comment about this.

Has anyone noticed that there is a problem with Microsoft Mail on macOS.

 

Logon with Safari or any other browser on Tahoe is fine but not Mac as a mail client.

An Outlook.com account I've been using for years on both Windows and Mac is now resulting in the attached pop-up.

 

I have even changed the P/W thinking a keychain corruption and still the same annoying resulting pop-up.

The same is happening on all other macOS versions on the machine, Tahoe, Sequoia and Sonoma.

 

I have since learnt the same is happening on real Macs according to some posts over on MacRumors.

It seems like an old problem has raised its head again.

 

To be honest the Exchange account is not a daily driver for me like my google account but it is the oldest.

At the moment I will contend with outlook on the Windows side until a fix or explanation is offered.

 

 

I had once a similar issue with Exchange under Sequoia.. Assure that your computer wakes from sleep with the correct RTC time.. 

[fuzzylogic]

you need to use exchange, delete outlook.com and pick exchange

[Irish_Man]

5 hours ago, eSaF said:

Thanks guys, I am in the process of tracking down the problem and haven't found a solution as yet.

Will try all suggestions posted so far, meanwhile all suggestions are welcomed.

 

If need be, I will start a Thread away from polluting this one.

Cheers.

I have the same issue as you my friend

I get the same error.  I was digging a bit and this is what I found out. 

 

 

I can’t add my Hotmail account on macOS 26 because:

 

1. Apple removed the “Outlook.com” option from Mail settings. 

2. That option was the only one that supported Microsoft’s modern login system (OAuth2).

3. Now, macOS only lets you add Hotmail using old-style IMAP with a plain password —
but Microsoft no longer allows that type of login for security reasons.

So Apple’s Mail app and Microsoft’s servers no longer speak the same login language.

 

Result: macOS says “can’t verify name or password,” even though my password is correct.

 

Open Terminal and type: openssl s_client -connect imap-mail.outlook.com:993 -crlf  and hit Enter.

Once connected (you’ll see a certificate dump), type: a login youremail yourpassword
If you get a NO LOGIN failed  then the IMAP server rejected the login — meaning it’s not Mail’s fault.

 

That “a NO LOGIN failed.” response means your credentials reached Microsoft’s IMAP server correctly, but the server itself refused the login, not macOS Mail.
So, this is a Microsoft-side authentication issue, not a Mail app or SSL problem.

 

Now im confused how others were able to add their account? 😕

[surenmunoo]

11 hours ago, eSaF said:

Don't know if this is the correct place to comment about this.

Has anyone noticed that there is a problem with Microsoft Mail on macOS.

 

Logon with Safari or any other browser on Tahoe is fine but not Mac as a mail client.

An Outlook.com account I've been using for years on both Windows and Mac is now resulting in the attached pop-up.

 

I have even changed the P/W thinking a keychain corruption and still the same annoying resulting pop-up.

The same is happening on all other macOS versions on the machine, Tahoe, Sequoia and Sonoma.

 

I have since learnt the same is happening on real Macs according to some posts over on MacRumors.

It seems like an old problem has raised its head again.

 

To be honest the Exchange account is not a daily driver for me like my google account but it is the oldest.

At the moment I will contend with outlook on the Windows side until a fix or explanation is offered.

I had issues with outlook on the Hack but it also gave issues on the Studio so it was a Mac thing I guess or just Tahoe issue. This morning, its all fine again.. 

[Anto65]

 

Spoiler

 

              

 

 

[strangeron]

I love adventure. Tahoe trial with IvyBridge. And yes, OCLP is required.

(Dear admin, if this is not suitable, it can be deleted.)

[arsradu]

Hey guys,

 

For the not so many of you guys who have tried AppleBCMWLANCompanion (including myself; yes, it works as long as you have a native Apple WiFi card), how did you solve the sound issue in Tahoe? Apple removed AppleHDA kext as far as I understood, in Tahoe. And I can't use OCLP-Mod to fix that (at least I don't think so), since the AppleBCMWLANCompanion kext requires the system to be specifically not-patched, and with SIP enabled.

 

So right now, I need to choose between having nice sound and...WiFi. :)) And I love having the nice sound.

Edited October 17, 2025 by arsradu

[kgp]

48 minutes ago, arsradu said:

Hey guys,

 

For the not so many of you guys who have tried AppleBCMWLANCompanion (including myself; yes, it works as long as you have a native Apple WiFi card), how did you solve the sound issue in Tahoe? Apple removed AppleHDA kext as far as I understood, in Tahoe. And I can't use OCLP-Mod to fix that (at least I don't think so), since the AppleBCMWLANCompanion kext requires the system to be specifically not-patched, and with SIP enabled.

 

So right now, I need to choose between having nice sound and...WiFi. :)) And I love having the nice sound.

 

 I am successfully running AppleBCMWLANCompanion.kext (BCMC) with AmfiPass.kext, SIP 03080000 and OCLP-mod AppleHDA root patch.

 

 

However, consider that BCMC is early beta...

Edited October 17, 2025 by KGP-iMacPro

[jlrycm]

31 minutes ago, arsradu said:

Hey guys,

 

For the not so many of you guys who have tried AppleBCMWLANCompanion (including myself; yes, it works as long as you have a native Apple WiFi card), how did you solve the sound issue in Tahoe? Apple removed AppleHDA kext as far as I understood, in Tahoe. And I can't use OCLP-Mod to fix that (at least I don't think so), since the AppleBCMWLANCompanion kext requires the system to be specifically not-patched, and with SIP enabled.

 

So right now, I need to choose between having nice sound and...WiFi. :)) And I love having the nice sound.

In my case, Tahoe will have to go with a USB Sound DAC or sound through the DP. But Tahoe is not my primary system - too buggy and unstable 

 

I also tried VoodooHDA setting SIP as 01000000 after installing it and the AppleBCMWLANCompanion kext works with this setting too.

Edited October 17, 2025 by jlrycm

[arsradu]

Awesome! Many thanks, guys!

[bluenote56]

18 hours ago, strangeron said:

I love adventure. Tahoe trial with IvyBridge. And yes, OCLP is required.

(Dear admin, if this is not suitable, it can be deleted.)

I confirm it works also on Ivy Bridge but unfortunately in my case I have all kepler gpus so I'll wait and I'll keep on with Sequoia for now.

[arsradu]

Hey guys!

 

Do you know of another way to download OCLP-MOD pkg for Tahoe? Looks like the GitHub Artifacts are expired now. Or can you please, upload it somewhere?