macOS 13 Ventura on Unsupported Macs Thread

[amaze1499]

FYI:Issue persists with latest 0.6.2n

ToConsoleUsers:gI0ScreenLockState
Couldn't alloc class *AppleKeyStoreTest

 

[Portiere]

Some little issues but not so important.
I can't see preview but i can paste to a post like you see, sometimes sys info is not smooth, but other seems working.

 

[webg3]

Using OCLP 0.6.1, I've successfully installed macOS Ventura 13.2.1 on my mid-2012 MacBook Pro (9,1), and Windows 10 using BootCamp Assistant. And to date, I'm delighted with the outcome and the lack of issues. But I'm in search of "safety nets" for both my Mac and Windows partitions. Specifically, what can and for that matter can't be achieved using MacOS Time Machine? I don't expect to be able to do a full system restore from the recovery environment. Or if Time Machine just isn't viable, is Carbon Copy Cloner a potential option?

And, with regard to my BootCamp partition, does anyone know of any feasible disk imaging options? I have a current license for WinClone, but I've raised the issue with them, and their response was that under OCLP, WinClone can back up the BootCamp partition, users are having issues with restoring. I don't know what the issues are, and I don't know whether these users were trying to restore UEFI or legacy Windows.

For the record, the Boot Camp partition on my vintage Mac is legacy MBR, using a hybridized GPT. Would a Windows imaging utility like Acronis or Macrium be able to back up the partition and restore it while running from a Windows PE bootable USB?

Thanks for looking

Hi, I have the same system as you, but the hardware is a little lower MacBook Air 2012 i5 1.7GHz, 4GB RAM, upgraded SSD, I have 1TB, left only 250GB for Windows 11 Pro, and it's running like butter.

On the subject of backup, I recommend backing up through the Windows system itself, and keeping a copy of your data in the cloud (OneDrive / iCloud Drive / Google One).

OCLP is only used to launch macOS Ventura, on Windows 11 Pro I also use Legacy mode (GPT hybrid with MBR).

in the mac partition, I format it, reinstall the system, I go from one version to another: macOS Catalina, Big Sur, Monterey and Ventura without any problem, but I don't touch the Windows partition, because it has worked perfectly since the launch of Windows 11, I keep it up to date and with the MS Office 2021 package, CS Source and Age of Empires III, usage is not very intense.

 

[webg3]

I downloaded the OCL 0.6.2 Nightly build, reinstalled OpenCore and post installed the Root Patch on my MacBookPro13,3 (late 2016 MacBook Pro 15") with macOS Ventura 13.2.1. Unfortunately I still can't play HEVC (x265) encoded videos (like these ones on a sample page https://x265.com/hevc-video-files/ ). The QuickTime Player hangs and has to be Forced Quit. VLC player takes a very long time to start playing using, I think, software based rendering of HEVC files. Also, using (copy right protected) streaming video services hangs/crashes the computer. x264 videos play without problems in Quicktime and VLC. So, this means that Hardware decoding/encoding of HEVC files (including all videos/photos shot on iPhones) is still not supported by the drivers in 0.6.2. Hardware decoding/encoding of x264 works. Unfortunately this means I (and many others I think) still can't switch from Monterey to Ventura yet. Hopefully the mighty developers of OCL will find a solution for this annoying and quite serious driver problem.

P.S. Would be nice if other forum members could test the same sample page for trying to play HEVC videos with their newest installs.

I've been using both the AppleTV+ and IINA and QuickTime app flawlessly to play DRM or x265 content on my Air 2012, and haven't encountered any OCLP 0.6.1 issues, I suggest reviewing the root-patch of your installation. I recommend replacing VLC with IINA, I'm on version 1.3.0, as the latest 1.3.1 failed to exit the application, even though it's working perfectly, so it's an application that always has updates and an innovative design: "This Is Way" (The Mandalorian)

 

[Bmld]

Hello, on an Imac 11.2, ocpl 6.1 Ventura I lost the system menu icons on the top right: control center, search Siri .. If I create a new user, the icons are there but after a few days they disappear. Do you have this problem? Any idea to fix this?

 

[StefanAM]

On my MBP4,1, backlit keyboard is working on Ventura and Monterey without root patching. Anybody know how I can stop OCLP to patch it automatically?

 

[cybazaar]

Latest nightly OCLP build with the 13.3 RC working well after root patching on Late 2013 15" MacBook Pro (Haswell, MacBookPro11,2 config). The experimental patches devs put in are working. Hopefully in due course they will find a way to enable AMFI as well.

 

[MacPeet]

Thanks to @khronokernel and other developers, great job

its working again

 

[vendini]

The patches worked on my iMac 13,2 (27" Late 2012)!
Excellent job from the developers, thank you!

 

[TOM1211]

Success sort of on mid 2014 using nightly but wasn’t without its hiccups for me with several failed attempts and deleting the patches in extensions from a big sur install anyhow at least it boots props to developers for there work so far
if your using virtual machines UTM works Parallels and vm fusion both won’t boot due to AMFI being disabled it looks like sticking to 13.2.1 and using a test install for 13.3.

 

[cab_007]

So far, so good - great job Devs!!! used the latest OCLP, was a little slow to log in initially but after root patch, all is back to normal. Noticed VMware Fusion does not launch guests but I figure they'll update it since 13.3 is out now.

 

[justperry]

Warning

I had to do a SMC/PRAM reset, lots of beachballing....so the OS did not boot again.

Solution, I patched the system again from another partition running an earlier OS.
Safe booting and then Patching might also do the trick, not sure though.

 

[Portiere]

Warning

I had to do a SMC/PRAM reset, lots of beachballing....so the OS did not boot again.

Solution, I patched the system again from another partition running an earlier OS.
Safe booting and then Patching might also do the trick, not sure though.

What i understood about OCLP.
Build and intall is to create installer or install it on HDD/SSD to boot system.
Root patches is to patch a specific system in use at the moment.
Ex. it is not pachatble Ventura from Monterey or others or catalina from Mojave.
In my case disk 0 is an SSD (ventura-Monterey.etc) and disk 1 is the origianl Apple disk (Mountain Lion-Sierra).
OCLP is always on SSD only so if i boot as know OCLP always starts first and it boots all systems.
If i like to boot mountain lion without OCLP i just press Option on boot.
If someone has the autopatch window, click exit as i always do.

 

[davidlv]

Warning

I had to do a SMC/PRAM reset, lots of beachballing....so the OS did not boot again.

Solution, I patched the system again from another partition running an earlier OS.
Safe booting and then Patching might also do the trick, not sure though.

I think it would be more useful to post your hardware and the OS version info with a post like this (maybe in your signature?), as I cannot make heads or tails of what you are talking about as it is. Do you expect anyone/everyone reading this post to remember what hardware you are talking about from a prior post perhaps? No way. As it is this post could be considered spam, as it is clearly not conversation or complete information dissemination.

 

[justperry]

I think it would be more useful to post your hardware and the OS version info with a post like this (maybe in your signature?), as I cannot make heads or tails of what you are talking about as it is. Do you expect anyone/everyone reading this post to remember what hardware you are talking about from a prior post perhaps? No way. As it is this post could be considered spam, as it is clearly not conversation or complete information dissemination.

Completely irrelevant.
My system (13.3 RC) did not boot after a SMC and PRAM reset, I had to, reason was a slow Mac, lots of beach balls.
I booted into another HDD that has the 1st Ventura beta installed, re-patched the SSD with OCLP, it then booted.

As above, hardware is irrelevant, resetting SMC/PRAM will result in an unbootable system since it can’t boot with AMFI enabled.

If you been here following this thread you know what hardware I have and what OS I run, been here long enough, I mentioned it in one of my last posts here, this or the former page.




Hint mm12

 

[Portiere]

Completely irrelevant.
My system (13.3 RC) did not boot after a SMC and PRAM reset, I had to, reason was a slow Mac, lots of beach balls.
I booted into another HDD that has the 1st Ventura beta installed, re-patched the SSD with OCLP, it then booted.

As above, hardware is irrelevant, resetting SMC/PRAM will result in an unbootable system since it can’t boot with AMFI enabled.

If you been here following this thread you know what hardware I have and what OS I run, been here long enough, I mentioned it in one of my last posts here, this or the former page.




Hint mm12

infact read here a post 2 pages ago

• Resolve boot support for 3802-based GPUs with macOS 13.3
  
  • Applicable for following GPUs:
    
    • Intel Ivy Bridge and Haswell iGPUs
    • Nvidia Kepler dGPUs
  • Note: patchset now requires AMFI to be disabled, patchset still in active development to remove this requirement
  • Do you see the note?
  • Smc/reset is irrilevant as you try with AMFI enabled
  • To boot with AMFI press shift/enter when you are on the system icon to boot, safe boot.
  • This is the only way to boot

[…]

 

[Tockman]

If you been here following this thread you know what I have, been here long enough, I mentioned it in one of my last posts here, this or the former page.

Do you really believe everyone out there has to know it by heart?

 

[chris1111]

Thanks to all Dev's !!!
@khronokernel
@ASentientBot
@dhinakg
Acidanthera OpenCore Team
moraea Team

Geforce 710 OK

 

[davidlv]

Completely irrelevant.
My system (13.3 RC) did not boot after a SMC and PRAM reset, I had to, reason was a slow Mac, lots of beach balls.
I booted into another HDD that has the 1st Ventura beta installed, re-patched the SSD with OCLP, it then booted.

As above, hardware is irrelevant, resetting SMC/PRAM will result in an unbootable system since it can’t boot with AMFI enabled.

If you been here following this thread you know what hardware I have and what OS I run, been here long enough, I mentioned it in one of my last posts here, this or the former page.




Hint mm12

If you are so confident that posting your hardware/system details is so "Completely irrelevant" and that everyone should remember what your hardware is, why don't you post a poll, asking "Do you remember what hardware I have, and the related OS?
I will vote "No" or "Definitely no" in advance.
Interesting to see the results, no?
Just edit your signature with that info after you see the results.

 

[vince22]

2012 13" MBP (9,2) latest OCLP 0.62n Ventura 13.3 RC, this might be a bug or just maybe due to AMFI disabled, anyway any photos open with preview app will result in blank image, no issues with 2015 13" MBP.

 

[amaze1499]

2012 13" MBP (9,2) latest OCLP 0.62n Ventura 13.3 RC, this might be a bug or just maybe due to AMFI disabled, anyway any photos open with preview app will result in blank image.
View attachment 2178557

Thanks for sharing, in my case I rolled back to 13.2.1 patched using 0.6.1. Seems like the winning team for now.

Booted from USB Installer, wiped SSD, migrated users from TimeMachine Backup done with 13.3RC previously.

 

[TOM1211]

2012 13" MBP (9,2) latest OCLP 0.62n Ventura 13.3 RC, this might be a bug or just maybe due to AMFI disabled, anyway any photos open with preview app will result in blank image, no issues with 2015 13" MBP.
View attachment 2178557

Same issue on 15” mid 2014 MBP

 

[Sven G]

MacBookPro11,3 + macOS Ventura 13.3RC + OCLP 0.6.2n = (almost) everything works as it should. TechTool Monitor crashes when opened: don’t know if this is an OCLP or macOS issue…

 

[Sven G]

So far, so good - great job Devs!!! used the latest OCLP, was a little slow to log in initially but after root patch, all is back to normal. Noticed VMware Fusion does not launch guests but I figure they'll update it since 13.3 is out now.

Yes, same here (MBP11,3): VMware Fusion 13.0.1 and also Parallels Desktop 18.2.0 refuse to resume most VMs; a rather serious issue (maybe due to AMFI now being disabled?): let’s hope this can be fixed, as soon as possible…

Edit (see below; and here, too, Preview displays a blank window: but option-clicking on the green maximise button displays the image correctly again): Yes, it looks like this error is indeed related to AMFI being disabled…

Broadcom Community - VMTN, Mainframe, Symantec, Carbon Black

Broadcom Community - VMTN, Mainframe, Symantec, Carbon Black

communities.vmware.com

 

[steve123]

I have applied some fixes to get power management back under control.

Can you provide some additional details about what you did?