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.
On MBP11,4 spoofed to MBP14,3 as recommended by OCLP 0.6.1. From past experience, I avoided the Ventura 13.3 betas and stayed on the 13.2.1. With the announcement of 13.3 today, I thought it was safe to update my laptop's OS. Not so. Hanging 1/3 of the way on rebooting. I am trying to go back to the 13.2.1. Time Machine is not cooperating - It did not show any backups. Ah well, I'll try to get back to 13.2.
 
I’m an user that jump without care to 13,3b having a Mac mini 2014

New 0.6.2 version seem that supports again that computer with 13.3 but there is a note about AMFI

Note: To restore support for these models, AMFI has to be disabled. If your workflow requires AMFI enabled, we recommend staying on macOS 13.2.1 or older

Which are real implication of not able to enable AMFI? I’ve read about not to do a PRAM reset that makes system unbootable? Can I rebootable usage mode after that?

Now I have two systems: 13.2.1 patched and 13.3b4 non patched

Is it worth update 13.3 release and 0.6.2 in the beta system and post patch it or maybe I should wait more

Depends what software you use and if it needs AMFI as mentioned in posts before virtual machines in vm fusion or parallels won’t boot without AMFI as the developers mentioned it depends on your workflow I think the best option is to have a separate 13.3 partition and find out if the software you use on a daily basis will function with this feature disabled I have a mid 2014 MacBook Pro and will be sticking at 13.2.1 as it seems the best option with everything working 99% where 13.3 was more of a 70% without the AMFI as the OCLP mentions this really depends on what you are doing with your Mac and 13.3 users mileage will vary.
 
I have a 2012 Mac Mini. I installed Ventura 13.3 and OCLP 0.6.2 with post install patches. Everything went fine. However, if I open App store, it starts to load then crashes. If I start Mail, go to settings, then click mail plugins or any of the settings tabs, Mail crashes. Anyone else having these issues?
 
Hello Out There.

My 2015 15” MacBook Pro is now freezing after running the Ventura 13.3 update.

After installing the post Install Patch from OCLP 0.6.2, my Mac freezes halfway in the black apple boot screen.


My laptop will boot in safe mode. But will freeze again after installing post install root patches.

Any Ideas of what I can do?
 
Mac freezes halfway in the black apple boot screen.
Which SSD do you have installed? If you have a Samsung PCIe Gen 4 SSD, there could be very long boot time issue. My 980 PRO can take up to 10 minutes or more to get past the halfway point.
 
Depends what software you use and if it needs AMFI as mentioned in posts before virtual machines in vm fusion or parallels won’t boot without AMFI as the developers mentioned it depends on your workflow I think the best option is to have a separate 13.3 partition and find out if the software you use on a daily basis will function with this feature disabled I have a mid 2014 MacBook Pro and will be sticking at 13.2.1 as it seems the best option with everything working 99% where 13.3 was more of a 70% without the AMFI as the OCLP mentions this really depends on what you are doing with your Mac and 13.3 users mileage will vary.
Good, actually I use sometimes VMware but as I mentioned I could use the 13.2.1 partition as princípial

What I was worry it’s about PR reset or SIP enabled. Is there any risk if I need do it one day or I will avoid enter system with safe mode and unpatching that with OCPL

I am suggesting is patching my 13.3 beta partition or wait for next OCPL version, not update my 13.2.1 one
 
Which SSD do you have installed? If you have a Samsung PCIe Gen 4 SSD, there could be very long boot time issue. My 980 PRO can take up to 10 minutes or more to get past the halfway point.
I have and installed a HatSSD (aftermarket reputable company). I let it sit for a half hour with no progress....
 
Depends what software you use and if it needs AMFI as mentioned in posts before virtual machines in vm fusion or parallels won’t boot without AMFI as the developers mentioned it depends on your workflow I think the best option is to have a separate 13.3 partition and find out if the software you use on a daily basis will function with this feature disabled I have a mid 2014 MacBook Pro and will be sticking at 13.2.1 as it seems the best option with everything working 99% where 13.3 was more of a 70% without the AMFI as the OCLP mentions this really depends on what you are doing with your Mac and 13.3 users mileage will vary.
This seems to be a bit of a watershed moment.

13.3 seems to have 49 security fixes, but (for us) at the cost of not having AMFI enabled AND losing the use of certain apps as described above.

So what to do? My 2013 MBA is supported so not a problem there, but would I have more or less security under an unsupported 13.3, all things considered?

Also, is this [more-or-less?] security/loss of apps issue something that might eventually be addressed via new versions of OCLP, or is this just the way it is now? Do we have a more complete list of apps dependent upon AMFI?

As TOM1211 mentioned, maybe we are looking at different boot partitions going forward. Or maybe buying a new real Mac...
 
  • Like
Reactions: Sammypurple
hello all last night updated to 13.3 on my MBP mid 2015. i can confirm that the update went well and yes no Vm's will start with Parallel Desktop and also no RDP sessions (with jump desktop results in a black screen)) will work anymore.

hope there will be a sollution soon

anyway... thx to all who made this possible great job !
 
This seems to be a bit of a watershed moment.

13.3 seems to have 49 security fixes, but (for us) at the cost of not having AMFI enabled AND losing the use of certain apps as described above.

So what to do? My 2013 MBA is supported so not a problem there, but would I have more or less security under an unsupported 13.3, all things considered?

Also, is this [more-or-less?] security/loss of apps issue something that might eventually be addressed via new versions of OCLP, or is this just the way it is now? Do we have a more complete list of apps dependent upon AMFI?

As TOM1211 mentioned, maybe we are looking at different boot partitions going forward. Or maybe buying a new real Mac...
From what I gathered:

"Apple Mobile File Integrity was first released in macOS 10.12, the daemon and service block attempts to run unsigned code. AMFI uses lanchd, code signatures, certificates, entitlements, and provisioning profiles to create a filtered entitlement dictionary for an app. AMFI is the macOS kernel module that enforces code-signing and library validation.

Rationale:
Apple Mobile File Integrity (AMFI) validates that application code is validated.

Impact:
Applications could be compromised with malicious code."

source:https://www.tenable.com/audits/item...0.0_L1.audit:43e7ba82ed7c66c9eec4d3d74b2c046d

In terms of security it looks like with using 13.3 and having AMFI disabled you could either run your Mac with wide open gates or gates wide open. Or is it?
 
Hello @ll. I have two internal SSD on my iMac 13.2 one with Ventura 13.2.1 and the other disk for testing purpose, with 13.3 release.

Build and Installed OpenCore 0.6.2 EFI on main disk with Ventura 13.2.1 and applied the root patches on both disks.


With Ventura 13.2.1 all apps that I am using working without problem even AMFI is disabled. With Ventura 13.3 so far I have noticed below:
  1. Most off sidebar icons in System Settings have disappeared.
  2. Image preview app flashes instantly the image and then gives a blank window.
 
  • Like
Reactions: DesertMom
Successful update of iMac mid 2011 27inch with NVIDIA K3100M
-From 13.2.1 to 13.3
-OCLP 0.6.2

So far, everything that I need works and I have not observed any problems yet. Again, thanks to all the devs, contributors, and testers of nightly OCLP and MacOS betas.
Screenshot 2023-03-28 at 3.40.21 PM.png
 
So far, the AMFI situation seems to be like this (for affected root-patched Metal-capable Macs):

- Monterey 12.x: default SIP is 0x802, and optionally the system boots also with 0x800, after having done the root patching (thus, with SIP enabled and only the SSV disabled: even better security); both LV and AMFI are enabled.

- Ventura up to 13.2.1: default SIP is 0x803, and won’t work with stronger SIP settings; LV is disabled (won’t boot if enabled) and AMFI is enabled.

- Ventura 13.3+: default SIP is 0x803, and won’t work with stronger SIP settings; LV is disabled (won’t boot if enabled) and AMFI is disabled (for now).

The most urgent thing is of course to return to the previous situation, with AMFI enabled also in 13.3+; and then, if at all possible (new patches?), restore the Monterey SIP and LV capabilities also in Ventura: let’s hope that at least AMFI can be reenabled (for example, besides the too lowered security, not being able to run VMs is definitely a major showstopper)…
 
Last edited:
If you read the OCLP 6.2 changelog it’s it long with some serious work gone on to get there in the changelog is this for 13.3

“Note: patchset now requires AMFI to be disabled, patchset still in active development to remove this requirement”

Now 13.3 been out for like a day now and it doesn’t say AMFI in the notes will be disabled forever on 13.3 and I’m sure if this becomes the case in a month or two developers will post that it will become the new standard of running OCLP as [mention]Sven G [/mention] mentioned all the pros and cons in there post I would probably go back to Monterey for full support without disabling things however I’m a long way off that given the development time to OCLP the fact there is already a version with some support for 13.3 shows how amazingly good the team behind it are.
Tom, a polite but important request: dots and commas, please. It very hard to understand your writing to non-native speakers.
 
Hi all,

I've just upgraded to Ventura 13.3 and OCLP 0.6.2 on my Mac Pro 5,1 with Vega 56 card but although it's booted up to desktop, screen refreshes, translucent effects etc are either slow or lacking - as if the graphic card isn't being utilised at all/properly. Additionally (although probably linked), one of my three screens isn't waking up at all, the two that are running are at a low resolution - again suggesting the graphic card isn't doing it's stuff.

The graphic card is showing correctly in the 'About This Mac' panel correctly.

I have reinstalled the post patches twice to double check things but no improvement.

Everything worked fine on OCLP 0.6.1 and Ventura 13.2 - am I missing something?

EDIT: I've reverted to the OCLP 0.6.1 post patches and my graphic card is now back to normal; obviously something not quite right with newer post patches and my own personal Mac setup.
 
Last edited:
MBP5,2: fine again with 13.3RC (22E252), KDK handling as before.

Safari: shows blank page unless its window is not in the foreground, as was reported in an earlier post. Exceptions: LinkedIn page always works. The favourites page is also fine.
Firefox: fine as alternative.
- Exception: LinkedIn login doesn't proceed in Firefox.
- EDIT: just tried LinkedIn in Firefox in 13.2.1 on supported MBP 16,1. Doesn't proceed either.
- So a problem of the LinkedIn/Firefox combination, NOT of OCLP or 13.3.

NB: used OCLP 062n 25 Mar (last commit: kdk_handler.py: Fix pkg detection)
NB2: 13.3 public release is 22E252, same build# as RC.
I am using MBP5,5 with OCLP 0.6.2 now.
I also have the same Safari issue - shows blank page...
Is there any way of fixing the issue now?
 
I am using MBP5,5 with OCLP 0.6.2 now.
I also have the same Safari issue - shows blank page...
Is there any way of fixing the issue now?
The issue could come from Safari 16.4.
My MBP 2011 was on 12.6.3 and I installed Safari 16.4 => blank pages. Same on 12.6.4.
So I went back to Safari 16.3, and all is OK now.
 
  • Like
Reactions: hvds
This morning I experienced a kernel panic related to one of the AMD gpu kexts:
Code:
com.apple.kext.AMDRadeonX4000
 
Hello,

OTA update OK on my test iMac 27" mid 2011:
- OCLP upgrade from 0.6.1 to 0.6.2 before Ventura upgrade
- rebuilt and installed OCLP 0.6.2 on the internal disk
- reboot
- OTA update from Ventura 13.2.1 to Ventura 13.3
- at the last reboot, OCLP detects and indicates that it is necessary to relaunch the post-install patches
- last reboot: everything seems OK :)

Capture d’écran 2023-03-28 à 15.39.09.jpeg
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.