Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS 15 Sequoia on Unsupported Macs Thread

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Using OCPL (and Dortania ) since 2016, using older Intel macbook pro when I was in the Maldives. Now using Imac Intel from 2009 in a daily basis for light work online, Zoom (with a green screen) and external hard drive, since last year I had more and more problem with heat disipation, do today I went for the hard choices. Upgrade to NVME hard drive and Cooling solution....by drilling Hiles for the fan and extra Holes near the copper on the back of the DVD drive. Here the Temp where around the 70C to high 90C, but, now 40 TO 60C MOST OF THE TIME WITHOUT AC IN THE ROOM. I LIVE IN JAPAN NOW, SMALL 1LDK AND AC IS EXPENSIVE. Thanks to all of you for helping people like me on a tight budget!!!
Thank You
IMG_1838.jpeg
IMG_1839.jpeg
IMG_1837.jpeg
Screenshot 2025-08-04 at 12.41.52.png
Screenshot 2025-08-04 at 12.50.41.png
 
  • Like
  • Wow
  • Love
Reactions: Riot Nrrrd, luckyduke23, MacRumors3590 and 6 others
Is there any way left to hide the Sequoia update from software updates under Sonoma? I'd like to get rid of the system settings badge, and have it stop saying updates are ready to install, when it's only referring to the macOS upgrade to Sequoia that I don't want. Thankfully it hasn't tried to force install it.
 
  • Love
Reactions: LlamaLarry
MacinMan said:
Is there any way left to hide the Sequoia update from software updates under Sonoma? I'd like to get rid of the system settings badge, and have it stop saying updates are ready to install, when it's only referring to the macOS upgrade to Sequoia that I don't want. Thankfully it hasn't tried to force install it.
Click to expand...
The following all at your own risk:

In terminal type:

sudo softwareupdate --ignore "macOS Sequoia"

Or something along this line…

If that doesn’t work, you could still try:

sudo chmod 000 /System/Library/CoreServices/Software Update.app

If you know how to edit a configuration file you could play around with the .mobileconfig

No risk, no fun! :)
 
  • Like
Reactions: olad, macpro_mid2014, hvds and 1 other person
amaze1499 said:
The following all at your own risk:

In terminal type:

sudo softwareupdate --ignore "macOS Sequoia"

Or something along this line…

If that doesn’t work, you could still try:

sudo chmod 000 /System/Library/CoreServices/Software Update.app

If you know how to edit a configuration file you could play around with the .mobileconfig

No risk, no fun! :)
Click to expand...
The ignore flag no longer exists / works with software update. I think Apple removed it a while back. Having the badge there isn't a big deal, as long as the upgrade isn't forced. Is there a way to change info in OCLP to say Sonoma is the latest version this mac can run?
 
MacinMan said:
The ignore flag no longer exists / works with software update. I think Apple removed it a while back. Having the badge there isn't a big deal, as long as the upgrade isn't forced. Is there a way to change info in OCLP to say Sonoma is the latest version this mac can run?
Click to expand...
You have to use OCLP 1.5.0, which is the latest version prior to 2.0.0, which enables Sequoia support
 
MacinMan said:
The ignore flag no longer exists / works with software update. I think Apple removed it a while back. Having the badge there isn't a big deal, as long as the upgrade isn't forced. Is there a way to change info in OCLP to say Sonoma is the latest version this mac can run?
Click to expand...

macpro_mid2014 said:
You have to use OCLP 1.5.0, which is the latest version prior to 2.0.0, which enables Sequoia support
Click to expand...
There is no way to do that as OCLP uses RestrictEvents to tell softwareupdate that the Mac is a virtual machine, which signals to softwareupdate "everything goes, everything is supported". This is done because otherwise OTA updates would not work at all and it doesn't matter which OCLP version you use, it will offer the update regardless. Using 1.5.0 just means you cannot root patch or possibly boot Sequoia with it.

Disabling automatic updates will prevent it from downloading or installing automatically (should be done with OCLP anyway) but Apple no longer offers a way to completely ignore a certain update, that is native behavior.
 
Last edited:
  • Like
Reactions: hvds, ronton3, macpro_mid2014 and 1 other person
Neon Ball said:
There is no way to do that as OCLP uses RestrictEvents to tell softwareupdate that the Mac is a virtual machine, which signals to softwareupdate "everything goes, everything is supported". This is done because otherwise OTA updates would not work at all and it doesn't matter which OCLP version you use, it will offer the update regardless. Using 1.5.0 just means you cannot root patch or possibly boot Sequoia with it.

Disabling automatic updates will prevent it from downloading or installing automatically (should be done with OCLP anyway) but Apple no longer offers a way to completely ignore a certain update, that is native behavior.
Click to expand...
That would explain why DRM doesn't work reliably on a patched Mac. Those features usually don't work in a VM either with an unaltered install. Even with a Windows VM, it's hit or miss under a supported config. They probably do it that way as a VM could potentially be used to steal content.

I'm actually at the point where Sonoma is letting me do all my usual tasks, it really doesn't matter if 3D acceleration doesn't work in VMs. Games suck in VMs so they run better on a direct hardware install. So, that's why I have Linux on an external drive now, for that very purpose.
 
MacinMan said:
That would explain why DRM doesn't work reliably on a patched Mac. Those features usually don't work in a VM either with an unaltered install. Even with a Windows VM, it's hit or miss under a supported config. They probably do it that way as a VM could potentially be used to steal content.

I'm actually at the point where Sonoma is letting me do all my usual tasks, it really doesn't matter if 3D acceleration doesn't work in VMs. Games suck in VMs so they run better on a direct hardware install. So, that's why I have Linux on an external drive now, for that very purpose.
Click to expand...
It's not running in a VM. That kext is just used to make certain parts of the OS (not full OS, just parts of it) think it's a VM like softwareupdate which means the kext is essentially lying to them about the machine's state, the OS runs on the hardware itself and is not virtualized.

DRM issues are likely caused by drivers and such.
 
Last edited:
  • Like
Reactions: macpro_mid2014, makra and hvds
Neon Ball said:
It's not running in a VM, that kext is just used to make certain parts of the OS think they're in VM like softwareupdate.
Click to expand...
I know it's physically running on hardware, but it made me wonder if it triggered other parts of the OS to think it's in a VM as well. That's the only reason DRM should break with valid graphics drivers available for a card that supports HDCP, which most DRM is based on for protected content.
 
MacinMan said:
I know it's physically running on hardware, but it made me wonder if it triggered other parts of the OS to think it's in a VM as well. That's the only reason DRM should break with valid graphics drivers available for a card that supports HDCP, which most DRM is based on for protected content.
Click to expand...
Issue is there are no "valid" graphics drivers available for unsupported models, the patches are using older drivers which requires modifying them and/or the frameworks as well (to make them work with the old drivers) and somewhere the DRM link/attestation may just cut off because it's modified too much.

However DRM should be supported on Metal Macs in places like Apple TV etc and lack of DRM to my knowledge is just a non-Metal issue because a lot of patching is required there.
 
  • Like
Reactions: houser, macpro_mid2014 and hvds
Neon Ball said:
Issue is there are no "valid" graphics drivers available for unsupported models, the patches are using older drivers which requires modifying them and/or the frameworks as well (to make them work with the old drivers) and somewhere the DRM link/attestation may just cut off because it's modified too much.

However DRM should be supported on Metal Macs in places like Apple TV etc and lack of DRM to my knowledge is just a non-Metal issue because a lot of patching is required there.
Click to expand...
I really wish I had kept up with programming, or at least the more inner workings of macOS. Maybe with my experience in broadcast production , and computer programming I could have come up with a fix for DRM on open core installs. Right now, I don't think I'm much help.
 
K two said:
macOS 15.7 installed atop 15.6 OTA, OCLP v.2.4.0, performs as expected.
View attachment 2534856:apple:👏
Click to expand...
Over here it wasn't a walk in the park:

Installation got stuck: grey screen white apple. I got impatient restarted with safe boot got presented with set up assistant to create a new user started running all sorts of problems just to find out this update needs a lot of patience and probably very recent back up.

So I restarted in normal mode got a cup of coffee and let it do its thing. Now back up and running 15.7 using 2.4.0 to reapply patches.
 
Last edited:
  • Like
Reactions: olad, Steve Gosselin, macpro_mid2014 and 2 others
I installed version 15.6 via OTA, everything is working correctly on the MacBook Pro 2017.

While we're on the topic, when I try to mirror my Mac screen to my Apple TV 4K gen3, the image goes black and only audio is transmitted. Even when mirroring just the desktop, it stays like this. Some say it's something to do with the DRM. Is there any strange DRM for mirroring my Mac screen to Apple TV?
 
mib01 said:
While we're on the topic, when I try to mirror my Mac screen to my Apple TV 4K gen3, the image goes black and only audio is transmitted. Even when mirroring just the desktop, it stays like this. Some say it's something to do with the DRM. Is there any strange DRM for mirroring my Mac screen to Apple TV?
Click to expand...
Can't reproduce that here: MBP 14,3 and Apple tV 4k gen3 work flawlessly.
 
makra said:
Can't reproduce that here: MBP 14,3 and Apple tV 4k gen3 work flawlessly.
Click to expand...
Got it. On the MBP 2017, the Apple TV 4K screen is black. AirPlay streaming is the only way to do this. I can mirror my iPhone screen perfectly.
 
  • Like
Reactions: makra
The problem I have run into with 15.7 (24G207) is that the root patching cannot locate a suitable KDK file (it appears that OCLP will match down to 15.6 but deems the 15.5 (24F74) KDK to be too distant from the required version to allow it to match down and proceed). Any ideas how to force OCLP to use the 15.5 (24F74) KDK (which seems to be the last one Apple has made available)? I'd be very grateful for any suggestions. (Mac is a 2015 iMac 17,2).
 
snapadee said:
The problem I have run into with 15.7 (24G207) is that the root patching cannot locate a suitable KDK file (it appears that OCLP will match down to 15.6 but deems the 15.5 (24F74) KDK to be too distant from the required version to allow it to match down and proceed). Any ideas how to force OCLP to use the 15.5 (24F74) KDK (which seems to be the last one Apple has made available)? I'd be very grateful for any suggestions. (Mac is a 2015 iMac 17,2).
Click to expand...
github.com

Releases · dortania/KdkSupportPkg

Kernel Debug Kit Mirror for macOS Ventura and newer - dortania/KdkSupportPkg
github.com github.com

From what I understand, 15.6 is included in the latest release.
 
Last edited:
I have recently made a dual boot NVME drive for Mojave and Sequoia using OCLP and it works fine (as in boots) however Id like to refine it if possible but as I'm new to opencore I dont know how to proceed (or if its possible)

So If I boot Mojave I use apple boot picker (no opencore) as standard, when I boot opencore I pick the opencore logo and it boots into opencore bootpicker but it always defaults over mojave and if I dont move it within the 5 seconds then ...

Is it possible to make opencore always pick sequoia (I know I can remove the 5 secont timeout when it works) rather than the last OS booted then when I reboot using apple bootpicker I can choose mojave without opencore? I have a flashed 5,1 so I have native bootscreen.

Thanks, Dave
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back