I have several OCLP Macs now updated to 15.7.3, all of them with Defer90.mobileconfig. None of them is showing Tahoe. Not inclined to run the softwareupdate command, since this might trigger it 
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Defer Tahoe for 90 days
- Thread starter bogdanw
- Start date
- Sort by reaction score
"reapplying" doesn't do anything. It doesn't matter when you installed the profile of how many time are you going to reinstall it, it’s always 90 days since the OS was released.
Release dates https://support.apple.com/en-us/100100
Depending on what Mac OCLP is faking, you may not need a profile at all.I have several OCLP Macs now updated to 15.7.3, all of them with Defer90.mobileconfig. None of them is showing Tahoe. Not inclined to run the softwareupdate command, since this might trigger it
Example: macOS Sequoia is compatible with iMac (Retina 4K, 21.5-inch, 2019), but macOS macOS Tahoe is not. So, if OCLP is making your Mac appear as an iMac from 2019, Tahoe will not show up as an upgrade.
macOS Tahoe is compatible with these computers https://support.apple.com/en-us/122867
macOS Sequoia is compatible with these computers https://support.apple.com/en-us/120282
That's an interesting point. Is there a quick way to find out which model is faked by OCLP (without mounting EFI partition and checking config.plist)?
There, in fact, the correct model is listed. Does that mean it is possible to run Sequoia on 2011 iMacs without faking the model (just inserting kexts and root patches)?About This Mac
I doubt it. I don’t know what OCLP does on your iMac, but someone in the dedicated thread should know https://forums.macrumors.com/threads/macos-15-sequoia-on-unsupported-macs-thread.2428654/
I just checked on my OCLP MBP 2015 – it is showing the same screen. From my view, it means that even if OCLP is spoofing a non-supported model for Tahoe, the defer policy is still in place. Otherwise it wouldn't mention the organization at all, wouldn't it?
I honestly don't know -- I'm just happy it's continuing to defer 😂
Me too! When things work I do not have too many questions, I’m just enjoying it. 😅
The next milestone will be 28 December 2025, 90 days since the release of macOS Tahoe 26.0.1 (29 September 2025). 🤞
Given that going on iOS 18 beta track switches of the nag for iOS 26...
...is it possible that going on macOS 15 beta track will switch off the nag for macOS 26? I'll try soon.
Could be yet another layer for our shield.
...is it possible that going on macOS 15 beta track will switch off the nag for macOS 26? I'll try soon.
Could be yet another layer for our shield.
Last edited:
Happy holidays!
I don't like that most document icons in the Finder are generic, and the new design of the Contacts app is functionally unusable for me.
My employer just pushed the forced upgrade to 26.2 on my MBP to 12th March 2026.
Merry Christmas & Happy New Year!
Merry Christmas & Happy New Year!
29 December in my timezone,
softwareupdate --list-full-installers lists macOS Tahoe, Version: 26.0 and 26.0.1 with Deferred: NO, but neither appear in Software update or softwareupdate -l
Everything is looking good here as well. No pesky reminders from Apple side as of today.
Hey everyone, I’ve noticed a few questions popping up about OCLP and automatic updates. While I was helping out with lots of questions and comments about OCLP and running Sequoia and Tahoe on older MacBook Pros on other Apple-related channels and servers, some folks were concerned about automatic updates on their unsupported Macs running the latest versions of macOS.
One user experienced a 🚫 startup screen on their MacBook Air (pre-2018) when they accidentally left automatic updates disabled on system settings on OCLP Sequoia. Their Mac then tried to update to Tahoe.
OTA blockers are often a must for open-core legacy patcher Macs because people sometimes forget to disable automatic updates on system settings, and they worry about their Mac being bricked or needing Internet recovery or a reinstall of macOS. Many of these can also be set up using a custom configuration profile on Apple Configurator 2, but you’ll need a spare Mac and the Mac on OCLP needs to be in MDM supervision mode. Is there a better way to do this using the terminal?
One user experienced a 🚫 startup screen on their MacBook Air (pre-2018) when they accidentally left automatic updates disabled on system settings on OCLP Sequoia. Their Mac then tried to update to Tahoe.
OTA blockers are often a must for open-core legacy patcher Macs because people sometimes forget to disable automatic updates on system settings, and they worry about their Mac being bricked or needing Internet recovery or a reinstall of macOS. Many of these can also be set up using a custom configuration profile on Apple Configurator 2, but you’ll need a spare Mac and the Mac on OCLP needs to be in MDM supervision mode. Is there a better way to do this using the terminal?
I don't know what OCLP does on specific Macs, there is a special thread that might be useful https://forums.macrumors.com/threads/macos-15-sequoia-on-unsupported-macs-thread.2428654/
Same here. System settings showing "newest update allowed by organization" on OCLP MBP 2015 and OCLP iMac 2011.
Is that an Apple Configurator custom OTA blocker? Or the one the OP made that you installed it and you delay it every 90 days?