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.
The latest KDK is 26.2, the latest for Sequoia is 15.6. I already have 15.6. Which one did you get? It shouldn't be downloading a 26 one for Sequoia.

15.7.3. from 15.7.2 OCLP downloads KDK's during the repatch process after an update, then says the old one is still the latest. I do it all OTA, not USB.
 
15.7.3. from 15.7.2 OCLP downloads KDK's during the repatch process after an update, then says the old one is still the latest. I do it all OTA, not USB.
The method doesn't matter. If there is a newer KDK when the install process re-applies patches, it will be downloaded. The USB just automates the process, so you don't have to do the steps manually.
 
15.7.3. from 15.7.2 OCLP downloads KDK's during the repatch process after an update, then says the old one is still the latest. I do it all OTA, not USB.
I think it would be nice if we continue to differentiate here between dev and public betas/rc and release versions. FWIW. But maybe I am missing something. I obviously do not mind anyone testing or discussing any version to their heart's content but it is always nice to know the state of what is being tested and I for one do not use betas anymore unless it fixes something important with OCLP in an attempt to stay sane in an ever changing world ;)
 
Last edited:
  • Like
Reactions: dogen and INK1
I think it would be nice if we continue to differentiate here between dev and public betas/rc and release versions. FWIW.
But maybe I am missing something. I for one do not use betas anymore unless necessary with OCLP in an attempt to stay sane in an ever changing world ;)
That's the same with me, I don't do Beta anymore either, unless it's just a basic app, but never the OS, or anything else critical.
 
I think the key word is "differentiate." Totally agree. No reason to avoid testing and reporting Betas if you like doing that as long as we're clear about the tested version when posting results. Simply posting the BuildVersion (which is found in About This Mac after clicking on the macOS version or when executing sw_vers in terminal) with posted results should be sufficient.
 
Simply posting the BuildVersion >>>should be sufficient.
Agreed generally, but as we know an RC can have a buildversion that then is the same when it becomes the release, so the beta and RC denominations can still be useful at times. Ah well, hairsplitting a tad maybe, but there it is ;)
Ah well, I am also pretty sure we can count on Apple to still throw a spanner or two into the Sequoia OCLP machinery so some caution when upgrading is still always a good idea IMHO.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.