Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
Safari 26.1 (20622.2.11.11.9)
Oh, seigh, dammed: I expected you were also experiencing font issues when using Safari on NVidea Kepler. But as it seems I‘m the only one having those rendering faults. Maybe this is due to a faulty chipset. Nevertheless It only appeared on Sonoma onwards :-/
 
  • Like
Reactions: rehkram
Oh, seigh, dammed: I expected you were also experiencing font issues when using Safari on NVidea Kepler. But as it seems I‘m the only one having those rendering faults. Maybe this is due to a faulty chipset. Nevertheless It only appeared on Sonoma onwards :-/
Your signature suggests you're using old versions of OCLP on your two Macs, specifically 0.6.8 & 1.4.2. Assuming that's correct, I have to ask why. Each new version of OCLP contains fixes and improvements which are not applied retroactively to older OCLP versions.

Of course, you may well have good reasons based on your local conditions. Personally I always install the latest public release of OCLP (2.4.1 at present) pretty soon after it becomes available.

Also, for persistent errors local to your m/c, before suspecting chipset problems (rare), I'd do a clean install back to the last supported version of macOS on your m/c, and update to Sequoia from there using the latest version of OCLP
 
Last edited:
  • Love
  • Like
Reactions: jotzet and ronton3
Your signature suggests you're using old versions of OCLP on your two Macs, specifically 0.6.8 & 1.4.2. Assuming that's correct, I have to ask why. Each new version of OCLP contains fixes and improvements which are not applied retroactively to older OCLP versions.

Of course, you may well have good reasons based on your local conditions. Personally I always install the latest public release of OCLP (2.4.1 at present) pretty soon after it becomes available.

Also, for persistent errors local to your m/c, before suspecting chipset problems (rare), I'd do a clean install back to the last supported version of macOS on your m/c, and update to Sequoia from there using the latest version of OCLP
Sorry for the misleading signature - I always kept OCLP up2date whenever a new release arrived...
 
Has anyone else had issues with Xcode 26.1 failing to update from the app store? I updated to 15.7.2, without issues, and Safari, and the command line tools updates installed fine, but Xcode won't update through the app store. 26.0.1 was the same way, and then it worked several hours later.

Finally got it to update. What I did is run the existing Xcode 26.0.1, went through the initial set up process again, as it seems to have reset itself after the macOS update, and then tried the update again, and this time it worked. Now 26.1 is downloading the Simulators, and so forth a first run of Xcode does.
 
Last edited:
Has anyone else had issues with Xcode 26.1 failing to update from the app store? I updated to 15.7.2, without issues, and Safari, and the command line tools updates installed fine, but Xcode won't update through the app store. 26.0.1 was the same way, and then it worked several hours later.

Finally got it to update. What I did is run the existing Xcode 26.0.1, went through the initial set up process again, as it seems to have reset itself after the macOS update, and then tried the update again, and this time it worked. Now 26.1 is downloading the Simulators, and so forth a first run of Xcode does.
Yes - I've experienced this. The problem resolved itself after I tried later. Not sure if it was my side or Apple's.
 
Yes - I've experienced this. The problem resolved itself after I tried later. Not sure if it was my side or Apple's.
Thanks, yes, I'm also fully up to date now, as well. Now, I'm wondering if Apple is going to release any updated KDKs, Sequoia is still using the 15.6 KDK. So far, it's not causing any apparent problems.
 
15.7.2 24G325 is available (not RC anymore as this has been referred to here without that tagged on)

This is along with the usual slew of 26.xx updates.

Edit:
MBA 6,2 updated OTA with OCLP 2.4.1 with no issues so far.

MBA 3,2 updated OTA with OCLP 2.4.1 using USB keyboard and USB ethernet.

A nice little side-effect is that Aerial wallpapers for some reason started working on both these Macs with 15.7.2
 
Last edited:
Upgraded via USB installer to 15.7.2 on my mid 2012 MBP (9,1). It was a smooth process if not a quick one. Afterward I also upgraded Safari and XCode Tools. No noticeable changes so far.
 
I installed Sequoia 15.7 by OCLP 2.4.1 to mac mini Late 2009, I found there is chime sound (it is like Option + Command + R to startup chime sound) repeated in one minute, how can I let this sound off?
 
I am just trying to install 15.7.2. on the following machine:

iMac 2011 27, 1TB SSD, 16GB RAM, K2100, OCLP 2.4.1. Triple boot with W11 & Linux Mint via OpenCore.

It was running flawlessly before on 15.7.1. Downloaded the image with OCLP and created a USB installer stick. Booted the installer from the stick. Unfortunately, after the black screen with "XX minutes remaining" I get the message"An Error Occurred While Preparing the Software Update" (see here). Tried PRAM reset after reboot several times, but no luck.

I remember having this error before at a 21,5" model (otherwise same configuration) with an earlier version of Sequoia. In the end I got it working, but I remember it being really annoying. Any ideas?

EDIT: Ok, after app. 10 retries it finally went through and everything's working now. What I did before (besides PRAM resets) was to boot into Windows 11 once. Afterwards the error was gone, though I am not sure if it has to do with this. The only thing left was that the OC entry for Mac OS was ugly – for each retry a "-Data" suffix seems to be added. Removed this by following this guide (with the side effect of now having an even nicer boot picker :))

It would still be nice to know what the cause of the error is. After all, the installation took like 3hrs instead of probably one - for the moment I will abstain from updating my other machines, which I also use productively. Seems the error is known by the devs, but no clear solution yet available besides retrying over and over.
 
Last edited:
I get the message"An Error Occurred While Preparing the Software Update" (see here).
What has worked here 100% is to delete the container that holds your Mac OS completely and then recreate it and do a fresh install from USB. This can effect boot sectors for other OS so proceed with caution and carry a large stick and a backup if you do this.
FWIW IMHO, this issue seems more frequent on multi-boot systems. No empirical data for this, as all my computers are multi-boot these days.
 
What has worked here 100% is to delete the container that holds your Mac OS completely and then recreate it and do a fresh install from USB. This can effect boot sectors for other OS so proceed with caution and carry a large stick and a backup if you do this.
FWIW IMHO, this issue seems more frequent on multi-boot systems. No empirical data for this, as all my computers are multi-boot these days.
That would have been the last resort but it would also mean having to reinstall everything/restoring from TimeMachine.

I am not completely sure, but I think I remember that it was because of this error that I switched from USB booting to launching the installer from Mac OS. Had not experienced this issue again until now.

Most of my Macs are also dualboot systems, but this is the only iMac which in addition to Windows 11 also has Linux Mint Cinnamon installed (which runs really well btw).
 
Last edited:
That sounds like a major hassle.

I hope the OCLP developers can figure out what is causing the installation failures.
 
Is Xprotect having more issues? It showed out of date last night, and the terminal commands said it was up to date. So, I gave it overnight until today, and it still says up to date in terminal, but Silent Knight is still saying it's not up to date. Running sudo Xprotect update in terminal still doesn't install any updates. Usually the terminal command fixes it, and usually waiting a day, also fixes it.

Edit: I checked this morning, and XProtect finally updated itself, so everything is green now. It was just really strange the manual update didn't do anything, it usually does when Silent Knight reports it's out of date.
Screenshot 2025-11-06 at 2.45.27 AM.png

Screenshot 2025-11-05 at 3.53.15 PM.png
 
Last edited:
Sequoia 15.7.3 just showed up on sys settings > general > OTA updates. Contains security updates apparently. I will update a supported Mac first before doing the unsupported one. Come to think of it, maybe in a couple of days. I'll let someone else try to break it before jumping in.
 
Last edited:
Sequoia 15.7.3 just showed up on sys settings > general > OTA updates. Contains security updates apparently. I will update a supported Mac first before doing the unsupported one. Come to think of it, maybe in a couple of days. I'll let someone else try to break it before jumping in.
Is it showing up under beta updates? I just looked, and it's not showing here, and beta updates is off.
 
Not a beta, just a security release I would guess. 15.7.3 (24G407)

I installed it, working fine on a supported mini 8,1 2018 here.

edit later: after a quick search on "24G407" it might be an RC1. If that's correct you'd probably need to have betas enabled to see it, I'm thinking?
 
Last edited:
Not a beta, just a security release I would guess. 15.7.3 (24G407)

I installed it, working fine on a supported mini 8,1 2018 here.

edit later: after a quick search on "24G407" it might be an RC1. If that's correct you'd probably need to have betas enabled to see it, I'm thinking?

I am installing also and OCLP is now downloading a KDK, but says no direct match still 24G407.
 
  • Like
Reactions: rehkram
Not a beta, just a security release I would guess. 15.7.3 (24G407)

I installed it, working fine on a supported mini 8,1 2018 here.

edit later: after a quick search on "24G407" it might be an RC1. If that's correct you'd probably need to have betas enabled to see it, I'm thinking?
Yes, most likely an RC, so I'll wait until it's Public.
 
  • Like
Reactions: rehkram
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.