Toggle sidebar Toggle 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.
EDIT4: Apple did publish KDK 15.7.4. This was not Apple's fault.

EDIT5: Leaving the text below just for history, but the problem with <Shift><Command> screenshots was the missing KDK as noted here.
I rebooted and <Shift><Command> screenshots are not working again. Not sure what happened, but the KDK isn't the whole story.

======================================

@amaze1499 It does appear that 15.7.5 is still using the same kernel. Thank you for clarifying.

EDIT: That kills my theory that the KDK was to blame for the non-working screen shots after applying OCLP 2.4.1 and 2.5.0n non-metal NVIdia patches to Sequoia 15.7.x. I guess this is an OCLP bug.

EDIT2: This reports the 15.7.1 kernel as 11417.140.69.701.11 and the 15.7.5 kernel is 11417.140.69.709.8. Not sure if this minor version difference indicates any changes to the 15.7.5 kernel.

EDIT3: These are the xnu kernel version octet definitions that I found

In the macOS XNU kernel version number (e.g.,
xnu-10002.40.63.503.1~1), the 4th and 5th octets (octets 4 and 5) usually represent more granular updates, such as bug fixes, specific kext updates, or minor changes applied to the kernel during the development and stabilization process.

These numbers are part of the xnu build number, which is derived from the CFBundleVersion within the kernel's Info.plist file, and typically increase with each iteration of the kernel, often incrementing rapidly during beta periods.

Breakdown of the XNU version (e.g., xnu-10002.40.63.503.1~1):
  • Octet 1 (10002): Major XNU version (correlated with the Darwin Kernel version).
  • Octets 2 & 3 (40.63): Intermediate build versions, often indicating a specific beta or release candidate stage.
  • Octets 4 & 5 (503.1): Further refinements or bug fixes (e.g., specific driver updates) within a release.
  • ~1 (After the tilde): Represents the final build number of the specific kernel release.
 
Last edited:
  • Like
Reactions: LookingOut and amaze1499
amaze1499 said:
Check for drives that are encrypted or at least are being flagged as encrypted. I assume if this is one drive and you cancelled the prompt, this is the one thats not being be mounted.
diskutil apfs list
You could also connect the volumes one by one and check for the prompt appearing.
When you found the drive:
diskutil apfs decryptVolume diskXsY
Click to expand...
I routinely hit cancel every time (the prompt appears 5 times every time DiskUtility opens. I don't see any drive at all not mounting as a result, all drives/partitions are present. It seems that cancelling the prompt has no effect on either drives mounting or appearing in the DiskUtility list. Its simply requesting a password and there is absolutely no difference whether I enter the password every request, or hit Cancel every request.
 
xboxbml said:
Yeah I've tried cables and different monitor, all that work fine under Monterey.. I went thru all this last year when I tried this before. I was hoping the issue would be fixed by now. It all works fine under Monterey. Anything above that does not.
Click to expand...
I've got Monterey all back together on this now. Restored TM backup, and last of my movies redownloading. I really wanted to be able to go to Sequoia for the Password app, and of course security updates. Bummer. I think I was trying to do the Universal Control/model spoofing for this 2015 MBP and that's why I had settings changed on this in OCLP. I don't think I ever got that working on this either. Open to any other suggestions for either issue. Thanks. Unless I can get solid proof/instructions on alleviating either of these issues, I'm stuck on Monterey until I get a new MacBook.
 
Hello, I have an issue on a Oclp 2010 iMac I5 8go radeon 6750M and sequoia 15.7.4. Impossible too use the native app screenshot. It don't work. I try with the keyboard and the app directly and no result. I try with an another app and it works. I use ocpl on lot of Mac without problem. On the same iMac, I have Sonoma and the screenshot works.have you an idea to find a solution.

I read the other post and I am not alone .... I answert to myself, it a pb with the last update and non metal card. So to solve I add iscreen an app from Applestore.
 
Last edited:
Bigwaff said:
No. You need USB installer with macOS and OpenCore on it. After boot installer USB, you clean install OC macOS on another external drive. Hold down Option key on boot to get macOS boot picker. You need to select OC EFI on external drive, then you get OC boot picker. Select macOS on external drive. Order of operations very important.


Model specific as it boots and installs unsupported macOS on your old hardware. Needs specific OC EFI.
Click to expand...
Gemini advised me that I can install Sequoia for another model on external disk.Steps
Build USB installer for my iMac13,1
Boot from it on MBA, it will trick it thinking it is iMac. It did, tcakpad was not working at least
Then run installation on external SSD.
Boot it on iMac, run post install patch.
But oclp restarts several time and I have no clue what happens during that and what HW identification goes on during that.
Resulting drive stops at about 5% of boot. has to try verbose boot yet.

Is it possible to do that or is Gemini hallucinating?
Direct install on iMac is nearly impossible because throttling because of drive missing thermal sensor.

EDIT: It is possible, but has many but and it is pain 😂
 
Last edited:
  • Haha
Reactions: CrowerFlowns
Frantisekj said:
i do but you can not use it during install. Now I managed to get Sequia on iMac14,3 but CPU is maxed all the time with Kernel task and MTLCompierService
Click to expand...
How long has elapsed since the install completed? MTLCompilerService instances will be present for a few days. It varies how many days, and how many instances, are active for different macOS releases. Patience is a virtue in this case.
 
  • Like
Reactions: deeveedee
Hi again everyone, second time I'm asking this question which I thought I had solved.

My iPhone does NOT connect to my primary desktop iMac (2015 iMac 27"15,1 Retina 32GB Sequoia15.7.5–OCLP2.5.0N). It connects to every other machine on my signature list.

I've noticed that whenever I upgrade the OS (15.7.3->15.7.4 and now 15.7.4 -> 15.7.5), after patching, it connects no issues. Then after the first reboot following that, I lose the ability to connect. So to get this working, I have to resintall the OS and go through the loop.

Can anyone suggest what I can do to fix this?
 
rehkram said:
How long has elapsed since the install completed? MTLCompilerService instances will be present for a few days. It varies how many days, and how many instances, are active for different macOS releases. Patience is a virtue in this case.
Click to expand...
I realized where is the problem. I was resurrecting two imacs with broken displays and when display is not connected to motherboard fans go full blast. They are dead silent now 🙂. It was my first experience with iMacs at all.
I must admire speakers 🙂
 
  • Like
Reactions: MacMorrison and rehkram
Let’s see if someone can help me with this, essentially my only remaining glitch with Sequoia and OCLP… As I have said before, it has been some time that FileVault requests a double password, one at boot and another (the same one) before login: while it should only request it one time, before booting, if everything is in sync; and I tried everything (even, again, decrypting, rebooting and re-encrypting the full disk, which should force a password sync; and the Keychain password is also the same and anyway cannot be changed), but it still requires the password twice: so, is this an OCLP 2.5n problem (in config.plist, maybe?), or some glitch in my MacBook Pro’s configuration…? I’ve also reset NVRAM and SMC: nothing changed. BTW, the secure token is enabled for my user, so everything’s looks like it’s correct: but nevertheless there is this odd double password prompt, before booting (normal) and also before logging in (shouldn’t be there). Vaulting is enabled in OCLP…
 
Last edited:
Same on my FileVault enabled machines - i didn't found a solutions so far but not a big deal for me i think for the moment we have to login twice ;-) let's see...
 
  • Like
Reactions: Sven G
The strangest thing is that it only happens on my MBP11,3, while currently on the MBP11,1 - also filevaulted - there correctly is only one password prompt at boot (some time ago, it was the reverse: worked normally on the former, but with double password prompt on the latter). Not a big deal, of course: but it would be really interesting to know why this happens (and also seems to “fix by itself”, sooner or later). BTW, without the root patches (after unpatching), it works as it should: with only one password prompt at the beginning…
 
Last edited:
Mid-2012 rMBP 15inch
Sequoia 15.7.5 with OCLP v.2.4.1

I am currently using a MacBook with the specifications described above.
However, when the MacBook goes into sleep mode, it occasionally fails to wake up and shows a black screen, forcing me to reboot. Is there any way to fix this issue?
 
figyu said:
Mid-2012 rMBP 15inch
Sequoia 15.7.5 with OCLP v.2.4.1

I am currently using a MacBook with the specifications described above.
However, when the MacBook goes into sleep mode, it occasionally fails to wake up and shows a black screen, forcing me to reboot. Is there any way to fix this issue?
Click to expand...
First, before using OCLP, did you update to latest supported macOS 10.15.7 to get latest firmware for your hardware?
Second, are you using FileVault? If so, try disabling FileVault.
 
figyu said:
Mid-2012 rMBP 15inch
Sequoia 15.7.5 with OCLP v.2.4.1

I am currently using a MacBook with the specifications described above.
However, when the MacBook goes into sleep mode, it occasionally fails to wake up and shows a black screen, forcing me to reboot. Is there any way to fix this issue?
Click to expand...
Do a search for "Fix dark wake, sleep issues in Sonoma and Sequoia" on MacRumors
This solution fixed a similar issue for several users here, me too.
1. Open Terminal
2. Create the folder structure necessary in terminal with this Terminal command:
sudo mkdir -p /Library/Preferences/FeatureFlags/Domain/,
3. Copy the code below into a editor and make sure the boolean flag is changed from <true/> to <false/>
Save the file as powerd.plist into the new folder: /Library/Preferences/FeatureFlags/Domain/
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>CoreSmartPowerNap</key>
<dict>
<key>Enabled</key>
<false/>
</dict>
</dict>
</plist>
4. Reboot
An extensive search on MacRumors shows an addition to the previous sleep-wake, dark wake solution, which also includes making that /Library/Preferences/FeatureFlags/Domain/ folder and copying the new edited powerd.plist to that folder.
Stop the dark wakes due to "RTC.Maintenance" (Apple’s intrusion): Do these Terminal commands line by line:
sudo defaults write /Library/Preferences/com.apple.mDNSResponder.plist NoMulticastAdvertisements -bool true
sudo pmset disksleep 0
sudo pmset womp 0
sudo pmset powernap 0
sudo pmset ttyskeepawake 0
sudo pmset tcpkeepalive 1
sudo pmset schedule cancelall
sudo pmset repeat cancel
Note; to lock the sleep / Wake schedule:
sudo chflags schg /Library/Preferences/SystemConfiguration/com.apple.AutoWake.plist
Unlock before any OS update, using the code below, Relock afterwards:
sudo chflags noschg /Library/Preferences/SystemConfiguration/com.apple.AutoWake.plist
reboot
 
  • Like
Reactions: Riot Nrrrd
figyu said:
Mid-2012 rMBP 15inch
Sequoia 15.7.5 with OCLP v.2.4.1

I am currently using a MacBook with the specifications described above.
However, when the MacBook goes into sleep mode, it occasionally fails to wake up and shows a black screen, forcing me to reboot. Is there any way to fix this issue?
Click to expand...

Try selecting the option "Disable mediaanalysisd service". Them rebuid and install OpenCore.

I use the same Mac model, the cause for frozen black screen is the mediaanalysisd trying to detect faces in Photos when idle. Only affects Macs with Kepler graphics (3802-based).

Disabling the service will lose the photos face and objects detection feature. What was previously detected will remain.


Edit: Alternatively you can also try enabling "Hibernation Work-around" to see if helps.
 
Last edited:
I'm encountering a persistent issue with Safari 26.5.
Every download starts correctly, reaches 100%, but then fails with the error: "Impossible to move file". The file remains on the Desktop/Downloads folder as a .download package.

System Details:
15.7.6 (Build 24G707)
Safari 26.5
OCLP 2.5.0 (MetallibSupportPkg-15.7.6-24G707.pkg)
MacBook Pro 2014 11.3

Log show reveals Sandbox denials for com.apple.coreservices.quarantine-resolver and com.apple.WebKit.Download.
The com.apple.quarantine extended attribute seems to be the trigger; if I manually strip it via terminal, I can extract the file from the .download package.
Sandbox restrictions seem to prevent the rename or move operation at the very end of the download process.

Things I have already tried:
1. Re-applying OCLP Post-Install Root Patches (Revert and Repatch).
2. Disabling "Open 'safe' files after downloading" in Safari Settings.
3. Changing the Download location to a custom folder with 777 permissions.
4. Disabling AdGuard and its Network Extension.
5. Granting Full Disk Access to Safari in Privacy & Security.
6. Running tccutil reset All com.apple.Safari.
7. Clearing LSQuarantineEvent database via SQLite.

Chrome and Firefox work fine.
Has anyone seen this specific error on macOS 15.x? Is there a known workaround for the quarantine-resolver sandbox denial?
 
Just upgraded my trash can Mac Pro to Sequoia 15.7.5 from Ventura. The installation itself was straightforward, but recovering files from my Time Machine backup from Ventura wasn't. I ended up manually restoring the files I need after the installation, as anything I tried with migration assistant left the machine unable to boot.
But anyway, all seems good now. Except, I tried installing the latest supported version of Lightroom classic (14.0.1) with creative cloud installer, and while it installed just fine, it crashes on launch. Any similar experiences or fixes? Stock installation of Sequoia 15.7.5 OCLP 2.4.1, 12-core xeon, Firepro D500 gpu.
 
EDIT: I have confirmed that the Dortania KDK mirror did not pull KDK 15.7.4 at the time of this post. This missing KDK was the cause of the non-working <Shift><Command> screenshots in non-metal NVidia Tesla as noted here.
I rebooted and <Shift><Command> screenshots are not working again. Not sure what happened, but the KDK isn't the whole story.

==========================================

Could someone check this to confirm that I'm not seeing things? It appears to me that Apple had released KDK 15.7.4,
Screenshot 2026-04-10 at 2.04.14 PM.png

but the Dortania KDK mirror did not pull KDK 15.7.4.
Screenshot 2026-04-10 at 2.05.26 PM.png

Are you seeing what I'm seeing?
 
Last edited:
Frantisekj said:
I realized where is the problem. I was resurrecting two imacs with broken displays and when display is not connected to motherboard fans go full blast. They are dead silent now 🙂. It was my first experience with iMacs at all.
I must admire speakers 🙂
Click to expand...
I fine tuned Sequioa install but... I face weird sound problem not sure it is related to OCLP.

I hear startup sound but when imac 2013 21,5" boots sound output turns to Digital output and no sound.
I tried all AI tricks. SMC, PRAM reset, midi devides setup, cleaning audio jack, reset core audio and other terminal hacks.
What I have not tried is disconecting broken display. I would bet i played youtube videos on both imacs and sound was working in some stage of messing with installation.

I have no clue whether it can have relation to OCLP as I said.
Cherry on top is that it already happened that display has came co life twice but goes off after reboot again 😀 Not sure it is related to display itself or cables or some chips on board.
 
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