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.
In fact, I did not state the order of operations completely right. What I did was:

Open OCLP app --> confirm update message and update --> Install OC to disk --> get error message "dirty volume" --> Click Post-Install Patch and Revert patches --> reboot --> Confirm OCLP message and apply new root patches --> reboot.
I did that the first time, rebooted twice after that. Still getting the dirty volume message with a few patches teasing me.
 
Yes, after updating the root patches it should say something like all available patches are already installed, but instead seems to be offering them again, even if they have been correctly updated: a glitch that was present also in the previous nightly builds.
 
Last edited:
  • Like
Reactions: TimothyR734
just update to, see picture
Scherm­afbeelding 2026-09-08 om 19.46.56.png
 
I downloaded and installed the OCLP 2.5.0 pkg, and then opened it to update my sequoia USB to the latest installer. Right now it says 15.7.9 is the latest, and what I'm downloading to refresh the installer. Is this the way to go for now, for Sequoia? I thought about going with Sonoma, since it can be better for certain things when it comes to stability. What are the current thoughts here ?
 
  • Like
Reactions: TimothyR734
Right now it says 15.7.9 is the latest, and what I'm downloading to refresh the installer. Is this the way to go for now, for Sequoia? I thought about going with Sonoma, since it can be better for certain things when it comes to stability.

It's hard to give blanket advice. The "best practice" depends on your specific hardware and the software you want to run.

Personally, I don't bother with the beta versions of macOS on my OCLP machine, nor do I use beta/nightly builds of OCLP.

My blanket recommendation is to read the OCLP FAQ thoroughly, and then to read the specific notes for Sequoia and Sonoma, paying particular attention to the "Issues" sections. Choose the OS that is most likely to do what you want on the machine you want to use. That said, keep in mind that if Apple continues past practices, August 2026's Sonoma 14.8.9 probably is Sonoma's final scheduled security update.

FWIW, I've been using Sequoia 15.7.9 and OCLP 2.4.x on my mid-2012 13" MBP, though I updated OCLP to 2.5.0 official release today.
 
It's hard to give blanket advice. The "best practice" depends on your specific hardware and the software you want to run.

Personally, I don't bother with the beta versions of macOS on my OCLP machine, nor do I use beta/nightly builds of OCLP.

My blanket recommendation is to read the OCLP FAQ thoroughly, and then to read the specific notes for Sequoia and Sonoma, paying particular attention to the "Issues" sections. Choose the OS that is most likely to do what you want on the machine you want to use. That said, keep in mind that if Apple continues past practices, August 2026's Sonoma 14.8.9 probably is Sonoma's final scheduled security update.

FWIW, I've been using Sequoia 15.7.9 and OCLP 2.4.x on my mid-2012 13" MBP, though I updated OCLP to 2.5.0 official release today.
I upgraded my late 2015 27-inch 5K iMac again to sequoia today from Monterey using 15.7.9 and the official release of 2.5.0. It's not bad, and everything seems to work including my custom compiled stuff. I still think Monterey is the best version of macOS when it comes to a balance between a modern OS and performance. Apple is increasingly making it hard though to keep an older version unless I switch to open source, which I did for many things.

Even so, Linux is a better fit for me when it comes to moving at a slower pace, but I still need macOS for some things. I've noticed that some of my apps from the MAS, want newer than Sequoia as well, to have the absolute latest updates. So now I've come to the point where do I want a new Mac, or do I want to change platforms. Anyway for the time being, this setup is still running OK. It seems like Apple has gotten rid of Xcode and replaced it with Apple Developer. I know this because Xcode doesn't show up in searches anymore; just in my purchase history. I found out the changes Apple is making I really don't like during the process of updating my apps.
 
It seems like Apple has gotten rid of Xcode and replaced it with Apple Developer. I know this because Xcode doesn't show up in searches anymore; just in my purchase history.

I'm not sure what you mean by that. Xcode remains a central component of the macOS development. It's not installed by default, but it's easy enough to get.
 
I'm not sure what you mean by that. Xcode remains a central component of the macOS development. It's not installed by default, but it's easy enough to get.
Do a search for Xcode in the Mac App store, when I did, it returned Apple Developer, without any Xcode results. I had to update Xcode to the latest for Sequoia through my purchase history. Also, I had to drag my existing binary from binary to the trash first, and then I was able to install 26.6.3. Anything beyond that is Tahoe, and newer. Here is a screenshot to back up my claim, and experience.
 

Attachments

  • Screenshot 2026-09-09 at 10.29.16 AM.png
    Screenshot 2026-09-09 at 10.29.16 AM.png
    4.9 MB · Views: 8
Do a search for Xcode in the Mac App store, when I did, it returned Apple Developer, without any Xcode results. I had to update Xcode to the latest for Sequoia through my purchase history. Also, I had to drag my existing binary from binary to the trash first, and then I was able to install 26.6.3. Anything beyond that is Tahoe, and newer. Here is a screenshot to back up my claim, and experience.

Current Xcode 26.6 require Tahoe 26.2+ and won't show for earlier macOS - for past macOS releases always use www.xcodereleases.com

Direct link for Xcode 26.3 for Sequoia https://developer.apple.com/service...per_Tools/Xcode_26.3/Xcode_26.3_Universal.xip
 
Last edited:
Current Xcode require Tahoe 25.2+ and won't show for earlier macOS - for past macOS releases always use www.xcodereleases.com
Thanks for the heads up. I didn't realize the visibility had changed based on version. When I saw that, I got the impression Apple changed Xcode into Apple Developer and that was the new name for it going forward. Also keep in mind that I haven't been following Xcode either, as I had built llvm from source, as well as several versions of GCC so I could keep current independent of Apple since I usually don't build native apple tools, but cross platform open source tools. In fact in terms of security updates and patching my own system, I was doing well with that on Monterey, it's more the pre-compiled native macOS binaries that were falling behind in support, and I haven't found open source alternatives for everything yet.
 
Thanks for the heads up. I didn't realize the visibility had changed based on version. When I saw that, I got the impression Apple changed Xcode into Apple Developer and that was the new name for it going forward. Also keep in mind that I haven't been following Xcode either, as I had built llvm from source, as well as several versions of GCC so I could keep current independent of Apple since I usually don't build native apple tools, but cross platform open source tools. In fact in terms of security updates and patching my own system, I was doing well with that on Monterey, it's more the pre-compiled native macOS binaries that were falling behind in support, and I haven't found open source alternatives for everything yet.

Apple Developer is not an IDE/compiler/debugger, is just an app for Apple Developer site/forum/videos/keynotes/etc.
 
  • Like
Reactions: josehill and K two
Thanks for the heads up. I didn't realize the visibility had changed based on version. When I saw that, I got the impression Apple changed Xcode into Apple Developer and that was the new name for it going forward.

The only time you'd see Xcode in the App Store on an older version of macOS is if it is already installed, when it would say that you need to upgrade macOS to use the latest Xcode, or in your list of "Purchased" apps.
 
The only time you'd see Xcode in the App Store on an older version of macOS is if it is already installed, when it would say that you need to upgrade macOS to use the latest Xcode, or in your list of "Purchased" apps.
It was always searchable until Tahoe came out. And yes it shows up in my purchase history as well.
 
Am I mistaken in thinking the 26.x versions require Apple Silicon? For Intel I believe you'd need Xcode 16.x, though Homebrew complains about it.
We are using 26.5 on Intel FWIW so I would think this is not quite correct. But on Tahoe and supported Mac
so I would think limitations are not plain Intel. Yet.
 
Am I mistaken in thinking the 26.x versions require Apple Silicon? For Intel I believe you'd need Xcode 16.x, though Homebrew complains about it.

If you take a look on xcodereleases.com you’d see that Xcode 26.x are also for Intel Macs, for 26.3 the requirement is just Sequoia 15.6+, see below.

IMG_1780.jpeg
 
If you take a look on xcodereleases.com you’d see that Xcode 26.x are also for Intel Macs, for 26.3 the requirement is just Sequoia 15.6+, see below.
Interesting. I've previously downloaded Xcode command line tools for 26.3 for that very reason. When i ran the installer I got a message that it wouldn't install on my OCLP iMac with 15.7.8. Perhaps I'll try the full Xcode installer and see how it goes.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.