The error in vm fusion is to do with AMFI being disabled looking on VMware communities UTM will still run windows 11 without it do you also have the preview error?
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
The error in vm fusion is to do with AMFI being disabled looking on VMware communities UTM will still run windows 11 without it do you also have the preview error?
I too noticed this behavior just now after your post, however if you zoom in/out, the picture displays - just not on normal zoom.
I can’t get it on zoom in/out but if you put the mouse over share the document or any bit of the top bar in preview and two fingers swipe any direction on the mouse the image will appear then disappear when you let go.
fix will be release when its ready, we'll wait for now, very impressed using iPhone as your webcam with continuity camera plus universal control unlocked working very well with 2015 13" MBP Ventura 13.3 RC.
Last edited:
Hopefully solution to the AMFI issue can be found patches where noted as experimental and 13.3 isn’t even released yet only installed on a second partition to test how it runs while my data safely on 13.2.1 .
Thanks to all Dev's !!!
@khronokernel
@ASentientBot
@dhinakg
Acidanthera OpenCore Team
moraea Team
HP Probook 650 G1 / Intel HD 4600
A great Laptop Haswell Work Station
All working 100% Fonctional!
@khronokernel
@ASentientBot
@dhinakg
Acidanthera OpenCore Team
moraea Team
HP Probook 650 G1 / Intel HD 4600
A great Laptop Haswell Work Station
All working 100% Fonctional!
First I wanna say THANK YOU for the great developing of OCLP. It gives my iMac 27" 11,1 a much longer life. This Mac was also patched before with DosDudes Patcher. So a have some experience with this patched machine.
Unfortunately I have an unknown problem so far. At the moment I'm on Ventura 13.2.1 with latest OCLP 0.6.2n.
When I format my USB sticks in ExFat using internal disk utility they are not recognized properly by different systems (two cars, windows PCs). Haven't had this issue before. But I don't know if it's related to OCLP nightly or OCLP in general (because I don't use USB sticks that much).
Anyone else seeing this issue? Any solution?
Thanks in advance.
Unfortunately I have an unknown problem so far. At the moment I'm on Ventura 13.2.1 with latest OCLP 0.6.2n.
When I format my USB sticks in ExFat using internal disk utility they are not recognized properly by different systems (two cars, windows PCs). Haven't had this issue before. But I don't know if it's related to OCLP nightly or OCLP in general (because I don't use USB sticks that much).
Anyone else seeing this issue? Any solution?
Thanks in advance.
always had better formatting with third party apps like paragon or tuxera I actually usually end up formatting on my windows 11 virtual machine in vm fusion with paragon software .
The partition table type is correctly set as Master Boot Record?
Shame on me and thank you for this hint.
Don‘t know why but it was GUID and now it is MBR again. Working like a charm again.
Did you have any luck installing the 13.3 RC on your MBP late 2013 with the latest OCLP?
Hi @shafez
I am not try because I have lots of Hack to test right now but tonight I will try then report to you
Another confirmation that VMware Fusion doesn’t like SIP and/or AMFI being disabled:
Strangely, with Parallels Desktop, my Ubuntu 22.10 VM resumed correctly and seems to be working, while the macOS and Windows VMs don’t work: odd, but essentially the same behaviour as with VMware Fusion. Well, if this AMFI thing won’t get addressed, I’ll have to go back to Monterey (which doesn’t have all these SIP, LV and AMFI problems with OCLP): but hopefully it will be fixed in a reasonable time…
Broadcom Community - VMTN, Mainframe, Symantec, Carbon Black
Broadcom Community - VMTN, Mainframe, Symantec, Carbon Black
communities.vmware.com
Strangely, with Parallels Desktop, my Ubuntu 22.10 VM resumed correctly and seems to be working, while the macOS and Windows VMs don’t work: odd, but essentially the same behaviour as with VMware Fusion. Well, if this AMFI thing won’t get addressed, I’ll have to go back to Monterey (which doesn’t have all these SIP, LV and AMFI problems with OCLP): but hopefully it will be fixed in a reasonable time…
Sharing my weekend experience with updating Ventura 13.2.1 to 13.3RC on MacBookPro11,3 (spolier: it was painful but SUCCESS in the end).
tl;dr: use _nightly_ build of OCLP (version 6.2 something, example: https://github.com/dortania/OpenCore-Legacy-Patcher/actions/runs/4520181474) and patch + post-boot root patch BEFORE updating your Ventura.
If however, you accidentally forgot to do that (like I did) and ended up with a non-booting system (error message `Couldn't alloc class “AppleKeyStoreTest”`):
- boot in safe mode (hold Shift and press Enter when selecting boot partition upon restart)
- while in safe mode, download the latest OCLP build (see above), and re-apply __post-install__ patches. This CAN be done in safe mode, unlike the root patch installation, which fails with `the volume is supported but damaged, try the "readOnly" option` message.
- your system should boot properly upon restart.
I just wish all this was mentioned in OCLP docs, as I had to google all this stuff from a safe-mode Safari, which probably is the closest imitation of Hell on Earth if it was running on the internet.
This is related: https://dortania.github.io/OpenCore...ck-screen-on-macbookpro11-3-in-macos-monterey
but due to the fact that root patches CANNOT be applied in safe mode (unlike post-install patches), it got me confused and wasted lots of time figuring this out the hard way.
---------
Now the full story for people googling it (trigger warning: lots of ranting towards Apple's interns who work this stuff, as I cannot imagine professional coders push releases of such quality to production).
First of all, big respect to OCLP devs for their hard work and thanks for giving 2nd-3rd-etc lives to our outdated but __perfectly__ functional computers. Opposite goes to Apple who is totally capable of supporting these machines (as OCLP devs prove over and over again), yet for marketing / financial / other evil reasons decide to drop support and force people onto new, often less reliable and less functional models (with missing F-keys, bad keyboard design, soildered SSD, missing ports etc)
So, as some may have noticed, Apple dropped a 13.3RC update this Friday. I'm not a big fan of updates, but 13.2.1 and priors had a bug with sporadic VPN disconnections, which I hoped was fixed in 13.3. Now, I know OCLP users should avoid betas, but 13.3 update was NOT marked as beta, and there was NO official OCLP version on GitHub beyond 6.1 which I already had installed and applied. All of this gave me an impression that it is safe to update so I went ahead. Initial update and reboot were uneventful, no errors, OCLP asked to re-apply the patches and to reboot. Which I did and 5 minutes later ended up with a broken system, failing to boot with `Couldn't alloc class “AppleKeyStoreTest”` error.
This particular system has been running and updated on various macbooks since OS X Snow Ocelot or whatever times, i.e. 15+ years, just update after update without significant issues. This weekend however, was going to be very different.
Upon quick research, it became obvious the cause is wiped-out-again support for my GPU (GeForce GT 750M in my case). I re-read OCLP docs and this thread opic and tried booting in safe mode, just to discover that __root patch cannot be applied in safe mode__. This particular VERY IMPORTANT piece of information is not in the docs, and just tangentially mentioned here and in some old github issues, and the error message `the volume is supported but damaged, try the "readOnly" option ` is not helpful to say the least. Upon more googling I figured there's no easy fix for this (if any), so the next option was to roll over most recent TM backup and move on.
Now I boot in recovery mode, got my TimeMachine ready, just to discover that you CANNOT re-apply a backup made in earlier MacOS version, even if it's only 0.0.1 version difference. I cannot remember exact error message, as I was livid about wasting 1/2 of my Saturday on this nonsense already with no end in sight, but it's along the lines `Error: This volume cannot be downgraded`. Turns out I have a week old backup that I cannot use unless I wipe out my whole system? In my mind wiping out would remove OCLP and I could end up in even more non-booting state unless I roll back to Mavericks and re-install all manually from scratch. Well thanks Apple, but not today I thought.
Next idea was to install Ventura on external drive and try patching from there (don't do that btw, apparently that's not possible either). Guess what? You CANNOT boot Ventura (or Monterey) from a USB SSD stick. Took another 1/2 day to discover this, as you can imagine installing Maverick -> Mojave -> Ventura from USB to USB is not the fastest process, just to encounter at the very very very last step the following, very informative message: `build_userspace_exit_reason: illegal flags passed from userspace (some masked off) 0x101, ns: 20, code 0x1.` (see ). Turns out, to run Ventura from an external drive, the drive has to be SATA-USB, not just any kind of USB stick. I cannot fathom the difference, but I guess Apple devs had a very good reason not to support it in latest MacOS versions. /s
Either way, at this point I was ready for a wipe out my system (and upgrade my SSD to a faster one, which I was postponing for a year now), but just out of curiosity one last time I tried safe mode -> post-install patching and IT WORKED. I was happy and furious at the same time, mostly with myself for not trying this earlier. I guess the main reason for my confusion was the above `read-only` message, which gave me wrong impression that no patching can be done in safe mode. Better error messages will be so so helpful.
So here I am, typing this from 13.3, with no data lost. I really hope the VPN problem is fixed so I don't have to ever update MacOS ever again on this machine.
Best of luck to everyone.
tl;dr: use _nightly_ build of OCLP (version 6.2 something, example: https://github.com/dortania/OpenCore-Legacy-Patcher/actions/runs/4520181474) and patch + post-boot root patch BEFORE updating your Ventura.
If however, you accidentally forgot to do that (like I did) and ended up with a non-booting system (error message `Couldn't alloc class “AppleKeyStoreTest”`):
- boot in safe mode (hold Shift and press Enter when selecting boot partition upon restart)
- while in safe mode, download the latest OCLP build (see above), and re-apply __post-install__ patches. This CAN be done in safe mode, unlike the root patch installation, which fails with `the volume is supported but damaged, try the "readOnly" option` message.
- your system should boot properly upon restart.
I just wish all this was mentioned in OCLP docs, as I had to google all this stuff from a safe-mode Safari, which probably is the closest imitation of Hell on Earth if it was running on the internet.
This is related: https://dortania.github.io/OpenCore...ck-screen-on-macbookpro11-3-in-macos-monterey
but due to the fact that root patches CANNOT be applied in safe mode (unlike post-install patches), it got me confused and wasted lots of time figuring this out the hard way.
---------
Now the full story for people googling it (trigger warning: lots of ranting towards Apple's interns who work this stuff, as I cannot imagine professional coders push releases of such quality to production).
First of all, big respect to OCLP devs for their hard work and thanks for giving 2nd-3rd-etc lives to our outdated but __perfectly__ functional computers. Opposite goes to Apple who is totally capable of supporting these machines (as OCLP devs prove over and over again), yet for marketing / financial / other evil reasons decide to drop support and force people onto new, often less reliable and less functional models (with missing F-keys, bad keyboard design, soildered SSD, missing ports etc)
So, as some may have noticed, Apple dropped a 13.3RC update this Friday. I'm not a big fan of updates, but 13.2.1 and priors had a bug with sporadic VPN disconnections, which I hoped was fixed in 13.3. Now, I know OCLP users should avoid betas, but 13.3 update was NOT marked as beta, and there was NO official OCLP version on GitHub beyond 6.1 which I already had installed and applied. All of this gave me an impression that it is safe to update so I went ahead. Initial update and reboot were uneventful, no errors, OCLP asked to re-apply the patches and to reboot. Which I did and 5 minutes later ended up with a broken system, failing to boot with `Couldn't alloc class “AppleKeyStoreTest”` error.
This particular system has been running and updated on various macbooks since OS X Snow Ocelot or whatever times, i.e. 15+ years, just update after update without significant issues. This weekend however, was going to be very different.
Upon quick research, it became obvious the cause is wiped-out-again support for my GPU (GeForce GT 750M in my case). I re-read OCLP docs and this thread opic and tried booting in safe mode, just to discover that __root patch cannot be applied in safe mode__. This particular VERY IMPORTANT piece of information is not in the docs, and just tangentially mentioned here and in some old github issues, and the error message `the volume is supported but damaged, try the "readOnly" option ` is not helpful to say the least. Upon more googling I figured there's no easy fix for this (if any), so the next option was to roll over most recent TM backup and move on.
Now I boot in recovery mode, got my TimeMachine ready, just to discover that you CANNOT re-apply a backup made in earlier MacOS version, even if it's only 0.0.1 version difference. I cannot remember exact error message, as I was livid about wasting 1/2 of my Saturday on this nonsense already with no end in sight, but it's along the lines `Error: This volume cannot be downgraded`. Turns out I have a week old backup that I cannot use unless I wipe out my whole system? In my mind wiping out would remove OCLP and I could end up in even more non-booting state unless I roll back to Mavericks and re-install all manually from scratch. Well thanks Apple, but not today I thought.
Next idea was to install Ventura on external drive and try patching from there (don't do that btw, apparently that's not possible either). Guess what? You CANNOT boot Ventura (or Monterey) from a USB SSD stick. Took another 1/2 day to discover this, as you can imagine installing Maverick -> Mojave -> Ventura from USB to USB is not the fastest process, just to encounter at the very very very last step the following, very informative message: `build_userspace_exit_reason: illegal flags passed from userspace (some masked off) 0x101, ns: 20, code 0x1.` (see ). Turns out, to run Ventura from an external drive, the drive has to be SATA-USB, not just any kind of USB stick. I cannot fathom the difference, but I guess Apple devs had a very good reason not to support it in latest MacOS versions. /s
Either way, at this point I was ready for a wipe out my system (and upgrade my SSD to a faster one, which I was postponing for a year now), but just out of curiosity one last time I tried safe mode -> post-install patching and IT WORKED. I was happy and furious at the same time, mostly with myself for not trying this earlier. I guess the main reason for my confusion was the above `read-only` message, which gave me wrong impression that no patching can be done in safe mode. Better error messages will be so so helpful.
So here I am, typing this from 13.3, with no data lost. I really hope the VPN problem is fixed so I don't have to ever update MacOS ever again on this machine.
Best of luck to everyone.
No idea what went wrong, but considering that 1) it was a completely fresh install of Ventura image created by latest OCLP release to a brand new 256gb Corsair USB SSD 2) I found many people report similar error in similar circumstances, hence it's free to assume there must be some MBP config that puts Ventura off.
As I mentioned, I have never went thru so much trouble to update MacOS, let alone need to re-install it from scratch, so all these shenanigans were totally new to me. I use my laptop for work, so last thing I expect is 1 day downtime over a simple update. I just leave my story here so it's googleable, as I can see few people on recent pages had similar kind of experience. I'm happy it worked smoothly for others though. OCLP is pretty awesome overall.
As I mentioned, I have never went thru so much trouble to update MacOS, let alone need to re-install it from scratch, so all these shenanigans were totally new to me. I use my laptop for work, so last thing I expect is 1 day downtime over a simple update. I just leave my story here so it's googleable, as I can see few people on recent pages had similar kind of experience. I'm happy it worked smoothly for others though. OCLP is pretty awesome overall.
I still cannot get it to work on my MBP 15” Mid2015 - can run and get OCLP to work on 13.2.1 but not 13.3RC. The AMD graphics still goes to hell in a bucket. Can run in safe mode but then can’t run the OCLP patch again.
Waiting, waiting, waiting
Waiting, waiting, waiting
Waiting? 13.3 hasn’t even been officially released enjoy 13.2.1 originally when Ventura was announced it was said there may be no Ventura support for 6+ months the fact we have support up to 13.2.1 is amazing don’t worry about 13.3 support may come it may not if you need to run the latest and greatest get a new Mac what stand out feature is it your after from 13.3? I know it’s got 15 new emoji characters .
You’re totally right and it may be just me wanting to run the latest and greatest for no other reason that it is the latest. Have done so for over 20 years and I guess it is now just a habit.
I said it too early perhaps. Now my MBP wouldn't boot, from OCLP on disk or USB, and even in safe mode. On booting, it just goes half way and stays there
I made no change except I had let it sit overnight and the battery had drained. Not sure what I can do except wait for some more fixes. Don't want to wipe and install 13.2.1.