Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 13 Ventura on Unsupported Macs Thread
- Thread starter 0xCUBE
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
OTA update from beta2 to beta3 went fast and fine - 1,21 gb for MBA 7,2. No problems with post patch.
Last edited:
Same situation and I returned back to Ventura 13.0 and got the same message now.... strange , I din't got that message at initial time I installed Ventura 13.0. May be some part of Ventura 13.0.1 is still there on my iMac Late 2015. I think Apple make it difficult to keep our device to work properly with new OS release... business strategy ....
If you have a developer account you can dl - this will help:
Kernel Debug Kit 13.0 build 22A5365d
just this afternoon I found this procedure and I bought DLink DWA-121 on Amazon, tomorrow I'll try hoping that everything works, already installed the app package ... I hope that oclp fixes the problem of Wi-Fi cards with native drivers
Sorry, I'm not familiar with it. I create developper account, search Kernel Debug Kit 13.0 build 22A5365d and didn't find it. If you can point me where it is and what to do with it. Does it resolve the problem or shw detail error.
I wish to stretch my iMac 27 inch late 2015 and avoid to buy a Mini ou MiniStudio....All video on the web look easy do do so but got problem. I’m close to declare I'm done or someone have solution.
Last edited:
Hi, In another forum I have been suggested to do in the same way, that is to download the Kernel Debug Kit from here. I tryed without success: https://developer.apple.com/download/all/?q=Kernel Debug Kit
Issue on Apple's side for the KDK download.
github.com
If you have a developer account you can download and install the 13.0 kdk, then you can run the post volume patch.
Automatic Kernel Debug Kit download broken · Issue #1016 · dortania/OpenCore-Legacy-Patcher
As per earlier this week, we've been notified that Apple has removed the ability for OpenCore Legacy Patcher to automatically download Kernel Debug Kits from Apple's Developer Site. This change was...
github.com
If you have a developer account you can download and install the 13.0 kdk, then you can run the post volume patch.
Thank you very much. It worked immediatelyIssue on Apple's side for the KDK download.
Automatic Kernel Debug Kit download broken · Issue #1016 · dortania/OpenCore-Legacy-Patcher
As per earlier this week, we've been notified that Apple has removed the ability for OpenCore Legacy Patcher to automatically download Kernel Debug Kits from Apple's Developer Site. This change was...
If you have a developer account you can download and install the 13.0 kdk, then you can run the post volume patch.
Good News I have also a Mid-2011 iMac 27". Did you just update through the standard update mac os or did you install through an usb key over an existing monterey ?
I patched yet my existing startup drive with the last oclp & now I don't know what's the best...?
@Cliff8928 @Fran Frin
Try to remove all kexts in /Library/Extensions but this 4 or any other related to a 3rd party software you have installed.
EnergyDriver.kext HighPointIOP.kext HighPointRR.kext SoftRAID.kext
Reboot and try again the patch.
Try to remove all kexts in /Library/Extensions but this 4 or any other related to a 3rd party software you have installed.
EnergyDriver.kext HighPointIOP.kext HighPointRR.kext SoftRAID.kext
Reboot and try again the patch.
Anyone else experiencing corrupted APFS containers with OCLP and Monterey or Ventura?
I have asked about this before a while back. Still seeing it on my rMBP 10,1 regardless of OCLP placement.
Could be a faulty error on my SSD but never happened before Monterey and still never happens on the Windows Bootcamp EFi. Upside is I am getting the procedure of reformat, install restore down to a discipline as I have maybe done it 6-7 times in the last year or so
I have asked about this before a while back. Still seeing it on my rMBP 10,1 regardless of OCLP placement.
Could be a faulty error on my SSD but never happened before Monterey and still never happens on the Windows Bootcamp EFi. Upside is I am getting the procedure of reformat, install restore down to a discipline as I have maybe done it 6-7 times in the last year or so
I'm not having this problem on my rMBP10,1. I don't use Windows Bootcamp EFI though, maybe that's the point of failure, since we have the same m/c? Worth investigating perhaps.Anyone else experiencing corrupted APFS containers with OCLP and Monterey or Ventura?
I have asked about this before a while back. Still seeing it on my rMBP 10,1 regardless of OCLP placement.
Could be a faulty error on my SSD but never happened before Monterey and still never happens on the Windows Bootcamp EFi. Upside is I am getting the procedure of reformat, install restore down to a discipline as I have maybe done it 6-7 times in the last year or so
Thanks for reply, as always. Appreciated.
I have tried running without Bootcamp also. Same result. My best guess so far is EFI corruption but could also be hardware.
Same computer, no problems with apfsAnyone else experiencing corrupted APFS containers with OCLP and Monterey or Ventura?
I have asked about this before a while back. Still seeing it on my rMBP 10,1 regardless of OCLP placement.
Could be a faulty error on my SSD but never happened before Monterey and still never happens on the Windows Bootcamp EFi. Upside is I am getting the procedure of reformat, install restore down to a discipline as I have maybe done it 6-7 times in the last year or so
Disk Utility tells me the container disk is corrupted and can not be repaired. As I understand it DU can not repair container disks reliably,
This has happened for me after a relatively short period of using a new SanDisk SSD in my iMac. I replaced it with a Samsung EVO SSD and didn't have that problem again. To me it seems to have been a firmware problem in the SSD.Anyone else experiencing corrupted APFS containers with OCLP and Monterey or Ventura?
I have asked about this before a while back. Still seeing it on my rMBP 10,1 regardless of OCLP placement.
Could be a faulty error on my SSD but never happened before Monterey and still never happens on the Windows Bootcamp EFi. Upside is I am getting the procedure of reformat, install restore down to a discipline as I have maybe done it 6-7 times in the last year or so
Very possible. Thanks for commenting.
The odd thing for me is that it only started happening with Monterey.
Possibly a coincidence. Possibly R/W is different for the firmware in my SSD for these latter versions of Mac OS/OCLP.
Time to start saving up for new SSD probably. I have gone 2 months without issues at best. Then corruption.
Maybe build up of R/W errors. Ah well.
Unreliable RAM modules can also cause any kind of subtle problems.
Hello to all,
Installed Ventura 13.1 beta3 OTA, onto an internal Fusion Drive of Mac 13,2 (late 2012) via OCLP 0.5.2n.
While I downloaded the Kernel_Debug_Kit_13.0_build_22A5365d from apple developer website, I did not have to use it; OCLP 0.5.2n is fully functional on my computer.
Subjectively the system “feels’ faster than Ventura 13.1 Beta2 and , so far, I did not encounter any obvious bugs while running any programs I use.
Hope this data point may be of help.
Installed Ventura 13.1 beta3 OTA, onto an internal Fusion Drive of Mac 13,2 (late 2012) via OCLP 0.5.2n.
While I downloaded the Kernel_Debug_Kit_13.0_build_22A5365d from apple developer website, I did not have to use it; OCLP 0.5.2n is fully functional on my computer.
Subjectively the system “feels’ faster than Ventura 13.1 Beta2 and , so far, I did not encounter any obvious bugs while running any programs I use.
Hope this data point may be of help.
Last edited: