The OCLP-Plus 3.x (Tahoe Patch Set).

[MakAsrock]

14 hours ago, Jessy Lou said:

Well, my dear friend MakAsrock, you just did it!

With this new release 3.2.2, reverting and reapplying the Root Patches works just great even on my exotic configuration (KGP knows where I'm coming from with my multiples EFI folders 😁).

 

 I can't stop saying MANY THANKS to you MakAsrock for this great valuable tool, as I can't stop THANKING VERY MUCH you KGP to your great support on my EFI nightmares. . 

I'm very glad that everything worked properly.
Hugs,
MakAsrock 🤗

Edited May 11 by MakAsrock

[MakAsrock]

I took a risk and tried an OTA update from macOS 26.4.1 (25E253) to 26.5 (25F71) for the first time with OCLP-Plus active. Everything was fully automated, including the KDK installation and root patches. It took 4 reboots in total and worked like a charm! 😉

OCLP-Plus_3.2.2_2026-05-12_05-41-03-996443.log 11.33 kB · 2 downloads.webloc

Edited May 12 by MakAsrock

[Jessy Lou]

Just for information: Tahoe 26.5 updated this morning with OCLP-Plus 3.2.2 detecting a new OS is going to be updated and starting to download

the new KDK... but it was in parallel of the upgrading process. I had only to plug Ethernet on to pursue the download once macOS finished its own upgrading process.
Then, normal process with full success.

Despite the risk of upgrading this morning, this demonstrates the strength of this solution: OCLP-Plus 3.2.2 is the perfect tool for Tahoe!

Edited May 12 by Jessy Lou

[MakAsrock]

45 minutes ago, Jessy Lou said:

Just for information: Tahoe 26.5 updated this morning with OCLP-Plus 3.2.2 detecting a new OS is going to be updated and starting to download it... but it was in parallel of the upgrading process. I had only to plug Ethernet on to pursue the download once macOS finished its own upgrading process.
Then, normal behavior with full success.

This demonstrates the strength of this solution: OCLP-Plus 3.2.2 is the perfect tool for Tahoe!

Here is the full story of what actually happened:

I was browsing InsanelyMac, reading the news about the official macOS 26.5 release. I figured, "Well, there's no rush to update, I'll go grab a smoke first."

I stepped away from my desk, completely unaware that macOS had already silently initiated the OTA update in the background. When I walked back into the room, my jaw dropped—the screen was literally displaying: "Update complete. Restarting in 5... 4... 3... 2... 1..."

I didn't even have time to panic properly until after the whole thing was over! My heart skipped a beat because I hadn't backed up a single thing. But OCLP-Plus 3.2.2 handled the entire emergency perfectly on its own: it intercepted the update, downloaded the new KDK over Wi-Fi in parallel, went through the 3 standard reboots, applied the root patches, and booted straight to the desktop. It turned out to be the ultimate, unplanned blind stress test of my own code!

Cheers! 😉

Edited May 12 by MakAsrock

[kgp]

6 hours ago, MakAsrock said:

I took a risk and tried an OTA update from macOS 26.4.1 (25E253) to 26.5 (25F71) for the first time with OCLP-Plus active. Everything was fully automated, including the KDK installation and root patches. It took 4 reboots in total and worked like a charm!

 

My dear friend 🤗,

 

Question:

 

All OCLP variants — including OCLP 2.4.1, OCLP 3.0.0 Nightly, OCLP-Mod and OCLP-Plus — automatically detect an ongoing macOS system update and perform the required changes automatically upon user confirmation.

 

However, when applying root patches, the system volume seal is usually broken. As a result, macOS no longer performs delta (sequential) OTA updates and instead downloads the full installer (~18 GB).

 

Therefore, in order to receive the smaller sequential OTA updates (~3 GB) instead of the full installer, I manually revert the root patches before every OTA system update.

 

So are you saying that OCLP-Plus does not break the system volume seal? 🙂

 

Hugs,

KGP 

🤗

 

Edited May 12 by kgp

[deeveedee]

1 hour ago, kgp said:

So are you saying that OCLP-Plus does not break the system volume seal? 🙂

 

No.  The OCLP Dev guidance is to perform macOS updates with OCLP post-install patches (forcing a full install).  Most OCLP users on real Macs never revert patches, so they're accustomed to receiving a full macOS update (not incremental).  There are some legacy Macs (like old non-metal) that cannot apply macOS updates without the OCLP patches, so reverting root patches before an update is not an option.

 

;TLDR - OCLP patches always break the APFS seal.  Performing macOS update with the patches in place is the OCLP Dev recommended way to update real Macs.

[MakAsrock]

1 hour ago, kgp said:

 

My dear friend 🤗,

 

Question:

 

All OCLP variants — including OCLP 2.4.1, OCLP 3.0.0 Nightly, OCLP-Mod and OCLP-Plus — automatically detect an ongoing macOS system update and perform the required changes automatically upon user confirmation.

 

However, when applying root patches, the system volume seal is usually broken. As a result, macOS no longer performs delta (sequential) OTA updates and instead downloads the full installer (~18 GB).

 

Therefore, in order to receive the smaller sequential OTA updates (~3 GB) instead of the full installer, I manually revert the root patches before every OTA system update.

 

So are you saying that OCLP-Plus does not break the system volume seal? 🙂

 

Hugs,

MakAsrock
🤗

 

It's usually best to roll back the ROOT patches and enable Ethernet right away before an OTA update. But I completely missed it. 😉
OCLP patches always break the APFS seal bat everything downloaded in the 10 minutes I went to smoke.
Hugs,
MakAsrock
🤗

Edited May 12 by MakAsrock

[kgp]

8 hours ago, MakAsrock said:

I took a risk and tried an OTA update from macOS 26.4.1 (25E253) to 26.5 (25F71) for the first time with OCLP-Plus active. Everything was fully automated, including the KDK installation and root patches. It took 4 reboots in total and worked like a charm! 😉

 

4 hours ago, MakAsrock said:

Here is the full story of what actually happened:

I was browsing InsanelyMac, reading the news about the official macOS 26.5 release. I figured, "Well, there's no rush to update, I'll go grab a smoke first."

I stepped away from my desk, completely unaware that macOS had already silently initiated the OTA update in the background. When I walked back into the room, my jaw dropped—the screen was literally displaying: "Update complete. Restarting in 5... 4... 3... 2... 1..."

I didn't even have time to panic properly until after the whole thing was over! My heart skipped a beat because I hadn't backed up a single thing. But OCLP-Plus 3.2.2 handled the entire emergency perfectly on its own: it intercepted the update, downloaded the new KDK over Wi-Fi in parallel, went through the 3 standard reboots, applied the root patches, and booted straight to the desktop. It turned out to be the ultimate, unplanned blind stress test of my own code!

Cheers! 😉

 

1 hour ago, MakAsrock said:

It's usually best to roll back the ROOT patches and enable Ethernet right away before an OTA update. But I completely missed it. 😉
OCLP patches always break the APFS seal bat everything downloaded in the 10 minutes I went to smoke.
Hugs,
MakAsrock
🤗

 

What a crazy story, my friend - almost hard to believe 😄

 

Usually, all OCLP variants automatically ask for explicit user confirmation before applying root patches — either when no root patches are currently installed or when OCLP detects an ongoing system update requiring new root patching.

 

To my knowledge, standard OCLP does not perform any root patching fully unattended without user interaction.

 

Thus, my final question is: did you remove or bypass the usual OCLP user confirmation dialogue in OCLP-Plus in order to allow fully automatic OTA handling and root patching?

 

If that is indeed the case, I would personally have some concerns regarding such a strategy, since uncontrolled or unattended root patching could potentially break user systems rather easily.

 

Still, very impressive stress test for OCLP-Plus 😄👍

[MakAsrock]

1 hour ago, kgp said:

 

 

 

What a crazy story, my friend - almost hard to believe 😄

 

Usually, all OCLP variants automatically ask for explicit user confirmation before applying root patches — either when no root patches are currently installed or when OCLP detects an ongoing system update requiring new root patching.

 

To my knowledge, standard OCLP does not perform any root patching fully unattended without user interaction.

 

Thus, my final question is: did you remove or bypass the usual OCLP user confirmation dialogue in OCLP-Plus in order to allow fully automatic OTA handling and root patching?

 

If that is indeed the case, I would personally have some concerns regarding such a strategy, since uncontrolled or unattended root patching could potentially break user systems rather easily.

 

Still, very impressive stress test for OCLP-Plus 😄👍

I don't understand why the update started by itself!
OCLP asked, but I was so confused that it was too late to connect the Ethernet cable.
The only hope was that it would download Kernel Debug Kit and install in time.

It was a bit nerve-wracking. 😉
I consciously agreed to the root patch at the last stage.
Hugs,
MakAsrock
🤗

Edited May 12 by MakAsrock

[kgp]

Fully automated OCLP root patching during delta and full macOS OTA Updates by all OCLP variants!

 

@MakAsrock, my friend! 🤗

 

I have to contradict some of my earlier conclusions and fully confirm your findings — this behavior works exactly as you described across all tested variants: OCLP 2.4.1, OCLP 3.0.0 Nightly, OCLP-Mod and OCLP-Plus.

 

Most importantly, this behavior is not specific to macOS 26.5 and appears to be part of the general OCLP OTA update workflow during both delta and full macOS OTA updates.

 

1.) I first reverted the root patches in order to receive the smaller delta (sequential) OTA update for macOS 26.5.

 

2.) Immediately after launch and during the download of the sequential OTA update, OCLP automatically detected the pending macOS installation and launched the following GUI prompt:

 

 

If the user does not press “Cancel” within roughly 10–15 seconds (which so far I always did), OCLP automatically starts downloading the matching KDK required for the target macOS version (2) - in this particular case, KDK Build 25F71 - without any explicit user confirmation by pressing “OK”.

 

Even during the KDK download itself, the process can still be interrupted manually via the “Cancel” button.

 

Without interruption, the GUI then entered a second phase simply stating:

 

“Preparing for macOS Software Update — macOS 26.5 (25F71). This may take a few minutes.”

 

 

 

From this point onward, the OCLP GUI remains visible without providing much additional feedback while the macOS installer download and preparation continue in the background.

 

Subsequently, the system reboots several times as part of the usual macOS update procedure and then boots directly into the updated macOS installation with modern Audio and modern Wi-Fi fully operational — without any need to manually reinstall the root patches afterward.

 

Modern Audio and modern Wi-Fi simply continue to work flawlessly. The same applies to the entire fully automated OTA update process itself.

 

Despite this impressive manifestation of completely automated OCLP “magic” by all OCLP variants,  I personally still prefer pressing “Cancel” within those initial 10–15 seconds and performing the root patching process manually afterward. 😉

 

Cheers,

 

KGP 👍

Edited May 13 by kgp

[MakAsrock]

1 hour ago, kgp said:

Fully automated OCLP root patching during delta and full macOS OTA Updates

 

@MakAsrock, my friend! 🤗

 

I have to contradict some of my earlier conclusions and fully confirm your findings — this behavior works exactly as you described across all tested variants: OCLP 2.4.1, OCLP 3.0.0 Nightly, OCLP-Mod and OCLP-Plus.

 

Most importantly, this behavior is not specific to macOS 26.5 and appears to be part of the general OCLP OTA update workflow during both delta and full macOS OTA updates.

 

1.) I first reverted the root patches in order to receive the smaller delta (sequential) OTA update for macOS 26.5.

 

2.) Immediately after launch and during the download of the sequential OTA update, OCLP automatically detected the pending macOS installation and launched the following GUI prompt:

 

 

If the user does not press “Cancel” within roughly 10–15 seconds (which so far I always did), OCLP automatically starts downloading the matching KDK required for the target macOS version (2) - in this particular case, KDK Build 25F71 - without any explicit user confirmation by pressing “OK”.

 

Even during the KDK download itself, the process can still be interrupted manually via the “Cancel” button.

 

Without interruption, the GUI then entered a second phase simply stating:

 

“Preparing for macOS Software Update — macOS 26.5 (25F71). This may take a few minutes.”

 

 

 

From this point onward, the OCLP GUI remains visible without providing much additional feedback while the macOS installer download and preparation continue in the background.

 

Subsequently, the system reboots several times as part of the usual macOS update procedure and then boots directly into the updated macOS installation with modern Audio and modern Wi-Fi fully operational — without any need to manually reinstall the root patches afterward.

 

Modern Audio and modern Wi-Fi simply continue to work flawlessly. The same applies to the entire fully automated OTA update process itself.

 

Despite this impressive manifestation of completely automated OCLP “magic” by all OCLP variants,  I personally still prefer pressing “Cancel” within those initial 10–15 seconds and performing the root patching process manually afterward. 😉

 

Cheers,

 

KGP 👍

Greetings, my friend! 🤗

Just so you know, I actually implemented that safety fallback autopilot back in version 3.1.9 after checking out how it's done on Dortania, but I completely reworked it. Later, in version 3.2.2, I only patched some critical flaws in detecting already installed root patches, which prevents overwriting the last sealed snapshot.

But in any case, I have always preferred strictly manual control until now. I’m glad the automation worked exactly as intended this time, though I did panic a bit during the macOS update process.

As I mentioned before, I was completely caught off guard and didn't react in time. When I came back from my smoke break, I saw that the update process was already entering the home stretch, while the KDK was still downloading! I only snapped out of it after logging into the desktop, and from that point on, I took back manual control.

I still haven’t figured out why the macOS update triggered on its own without any interaction, and frankly, that part scares me a bit. I hope KGP can shed some light on what actually happened this time. Maybe I was typing a reply on the forum and hit Enter to post it, but the window lost focus, and that Enter keypress was interpreted by macOS as a confirmation to start the update. Still, it makes no sense where the license agreement prompt went.

Hugs,
MakAsrock 🤗

Edited May 13 by MakAsrock

[deeveedee]

2 minutes ago, MakAsrock said:

...When I came back from my smoke break...

Give us some advanced notice next time so we can join you for a second-hand smoke break. 😄

[MakAsrock]

5 hours ago, deeveedee said:

Give us some advanced notice next time so we can join you for a second-hand smoke break. 😄

Will send out a calendar invite for the next deployment. 😉

[MakAsrock]

Greetings, my friends! 🤗

I've completely rewritten the first post.
Read what's been added and revised there.

Hugs,
MakAsrock 🤗

[deeveedee]

@MakAsrock Good to see you again!  I wish I had your developer skills.  Nice.

 

EDIT: OCLP Devs have confirmed that they're still working on the "official" OCLP 3.0.  I wish they'd be more open to supporting the development forks like yours, but I do understand how pride can get in the way.  I noticed mention of  lzhoang2801 and laobamac in your credits.  Maybe it would be good to extend an olive branch to OCLP Developer crystall1nedev and include her in the credits, since their git hub repositories started as forks of her public Tahoe Patchset fork.  Not sure if that would help to further possible relations.

Edited May 28 by deeveedee

[MakAsrock]

4 hours ago, deeveedee said:

@MakAsrock Good to see you again!  I wish I had your developer skills.  Nice.

 

EDIT: OCLP Devs have confirmed that they're still working on the "official" OCLP 3.0.  I wish they'd be more open to supporting the development forks like yours, but I do understand how pride can get in the way.  I noticed mention of  lzhoang2801 and laobamac in your credits.  Maybe it would be good to extend an olive branch to OCLP Developer crystall1nedev and include her in the credits, since their git hub repositories started as forks of her public Tahoe Patchset fork.  Not sure if that would help to further possible relations.

Greetings, my friend! 🤗
I'm glad they're continuing to work on the "official" OCLP 3.0 release. It's just not mentioned anywhere, and I'm mostly just I'm polishing the formulations in the readme.
At your request, I've included her in the credits. Although I had the line "Full list of OCLP contributors can be found in the original repository."
However, I have no feedback whatsoever from any of the original OCLP authors.
Hugs,
MakAsrock 🤗

Edited May 28 by MakAsrock