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.
So apparently there's reports coming through that the Rapid Security Response for macOS Ventura 13.3.1 (a)
is breaking OCLP installs. What's everyone's experience? I've turned off all updates since my last bad experience of going from 13.2 to 13.3.1 update on OCLP 0.6.4.

What I've read is that "pre haswel cpus wont handle this update and will not install it. "
And some installs have resulted in non-bootable machines.

Anyone with a definitive answer or is skip till 13.4 works?
I'm running the update on both a iMac 2013 27", and MacBook 2015 13", 7-9-13 it seems to work just fine.
When I reboot after an update I always re-patch, I have run the 13.3.1 (a) update on both OCLP 0.6.4 and now OCLP 0.6.5n ... perhaps the machine feels a tiny (like I'm in doubt) bit slower after that update.

There is a YouTube of Mr. Macintosh updating that update (I followed that those the first time), I seem to remember he say this update is critical for security ...


We have to remember that hackers is always most interested in the newest macOS ... so we are the most vulnerable.

PS: I don't use little snitch or similar though.
 
  • Like
Reactions: ofeyvi
Regarding Photoshop: are you really sure that everything works well if OpenCL is active?… Can you kindly check by opening a large photo and trying to use the Advanced Sharpening filter?…
Regarding what Live Text and Remove Background does, you can read the Apple’s pages about Ventura
You where right, no OpenCL it just makes it black with a few dots.
Works great in metal ... and the latest PS runs faster on this machine than I had expected 7-9-13 🤞🏻

As for remove backgrounds and live text (in ventura not PS), you seem to be right that they are not working :)
Everything else seems stable and running greatly so far.

I'm running 13.3.1 (a) (22E772610a) with OCLP 0.6.5n on both an iMac 2013 27", and MacBook 2015 13".
 
Last edited:
I updated my MBA2015, OCLP 6.4 Ventura13.3.1 with RSR and had no problem. However my upgraded 2012 iMac with the same OCLP and Ventura upgrades will not download the RSR. ("Failed to prepare the software update. Please try again." The progress bar stops at about 3/4 distance.
Same here on my A1278/13'' 2012 MacBook Pro/MacBookPro9,2… It's almost as if the machine knows it would get borked and protected itself from it… 😂
 
  • Like
Reactions: olad
RSR doesn't work on pre-Haswell Macs and possibly never will
That's what Mr. Macintosh said in his video regarding the subject. That it's safe to install on Haswell and newer, but earlier isn't supported. He basically said 2012, and below aren't supported. Just clear up some of the confusion I read earlier in the thread regarding people saying it didn't work on their machines.
 
  • Like
Reactions: Heliotropen
No problems other than the known 13.4 (since 13.3.1) issues related to AMFI being disabled and now the need for LS to be disabled with 13.4b4 (used OCLP 0.6.5n) -
1683210864984.png
 
I just checked the OCLP releases page, this is now stated clearly, with no exceptions, at the top of the OCLP 6.4 release blurb:

WARNING: Do not install macOS 13.3.1 (a) Rapid Security Response Update, currently unsupported on Macs running OpenCore Legacy Patcher. If you installed the update by accident, you can recover by booting into Safe Mode, and repatch macOS​


I've turned off all automatic updates in System Settings on the rMBP10,1 for the time being. 13.3.1 is working well.
Yeah, yesterday afternoon it automatically downloaded and installed without my permission on my MacBook Pro 11,4 when shutting it down, so I got the problem where it would get stuck while booting. But I was able to boot the Pro into Safe Mode, re-patch MacOS using the OCLP 0.6.5 beta, and now it runs just fine, even with the 13.3.1 (a) update still installed.
 
That's what Mr. Macintosh said in his video regarding the subject. That it's safe to install on Haswell and newer, but earlier isn't supported. He basically said 2012, and below aren't supported. Just clear up some of the confusion I read earlier in the thread regarding people saying it didn't work on their machines.
This makes you wonder if RSR is a Security Update or or a step to prevent older macs from running Ventura.
 
Should work now on OCLP 0.6.5 release
Tried the RSR 13.3.1 (a) on a rMBP 10,1 mid 2012. Got the same message as in the video above by
Mr. Macintosh ;) Not important for me in my context but perhaps useful info for someone. Many thanks.

.
Screenshot 2023-05-04 at 17.50.12.png
 
Tried the RSR 13.3.1 (a) on a rMBP 10,1 mid 2012. Got the same message as in the video above by
Mr. Macintosh ;) Not important for me in my context but perhaps useful info for someone. Many thanks.

.View attachment 2197376
RSR doesn't work on pre-Haswell Macs (because we're using the Rosetta cryptex and receiving RSR for x86_64h which has the AVX2 requirement)
 
I think that Macs from late 2013 and newer are Haswell+
Thanks to @educovas for all of the hard work!
BTW, love your Sad Mac avatar!!
Feedback: Successfully installed 0.6.6n (today's 5-5-2023 0:43 version) on my late 2014 iMac (Definitely Haswell) running 13.3.1 (a). One quirk noticed, screen (GPU) scrambled for a split second after post install root patches applied upon clicking the reboot button, for about 1 second before it rebooted. First time seeing that, but after the reboot, everything seems OK.
 
This makes you wonder if RSR is a Security Update or or a step to prevent older macs from running Ventura.
After a 2-hour session with Apple Care necessary to get that RSR thing installed on my "supported" M2 MBA, I seriously think it should be named Rabid Security Release! Issue solved via creating a new admin user, which allowed installation. Apple thought it was due to anti-virus or VPN software, but nothing like that installed. Cause remains unknown but I suspect it was due to a Japanese Input Method software installation (unproven and 13.3.1.(a) is running fine now even with that Input method installed).
That was by no means a Rapid event!
 
  • Like
Reactions: olad and NataliaC
Hey y'all, so I YOLO installed macOS 13.3.1 (a) on my 2014 MacBook Air 6,2 last night, and it went SNAFU. Looks like this update left my graphics kexts in limbo, so it would get the progress bar on boot to about 50% and just hang there with the CPU fan screaming. If you're like me, you hide the boot picker on your local OCLP installation, so here's what I did to fix mine:

1. Write OCLP for a MacBook Air 6,2 to USB using my iMac with the boot picker enabled
2. Boot said USB from my MacBook Air
3. Boot the macOS hard drive by pressing shift+enter. This will boot you into safe mode.
4. Once booted in safe mode, launch OCLP and reapply the post-install patches (haswell graphics).
5. Reboot
6. Profit

I hope this helps someone else who soft bricked their Mac by updating all willy nilly.
 
  • Like
Reactions: NataliaC
Hello to all,

Successful installation of Ventura 13,4 beta4 on iMac 13,2 and Macbook Pro 5,2

iMac 13,2:

Updated from 13.4 beta3 to 13.4 beta4, but, unlike usually, not via OTA; the system update panel, in System Settings->General -> Software Update, was unresponsive. Resetting SMC or NVRAM had no effect. It was probably a 13,4 beta3 glitch with very low probability of OCLP related issue. I downloaded newest OCLP 0.6.5n (with time stamp of 5.3.23), then was lucky enough to download full 13.4 beta4 installer package from Mr Macintosh site, which also just became available for download. Installed newest OCLP to the internal disk, then used it to create USB 13,4 beta4 installer. Booted into USB installer and installed 13.4 beta4 without incident. It may be prudent, however, to watch the installation process to assure that the correct system installer icon is selected by system boot-picker during the somewhat lengthy process. iMac runs smoothly; all System Settings are operational, with finder and applications very responsive. Streaming services are fully functional, as is the YouTube. I experienced no network issues reported by others, but I do not have Little Snitch, or related software on my system. In reports, disabling the LS restored network functionality. All application in my use work without issues, including Apple TV, Safari, FireFox, 1Password, OpenOffice, Gimp, Blender, etc.


MacBook Pro 5,2:

Updated to 13.4 beta4, using the OTA (Over the Air) method, without issues. Internal bluetooth is no longer active (it was not available in 13.4 beta3), but I have an external USB bluetooth 4.0 "dongle", which works without issues.
OCLP 0.6.5n (from 4.28.23) was "resident" on the internal drive (will update to OCLP 0.6.5n from 5.3.23 just to test it)
All applications not fully dependent on Metal appear to be functional (see above paragraph).

Another accomplishment to add to long list of the OCLP and non-Metal development team(s)' success record.

Hope this post may be of help.
 
Last edited:
RSR doesn't work on pre-Haswell Macs (because we're using the Rosetta cryptex and receiving RSR for x86_64h which has the AVX2 requirement)
Many thanks for this clarification. Much appreciated. I misunderstood the documentation and assumed wrongly that this support might be added with a new OCLP version. All workable regardless.
May I add that this project is one of the most useful and impressive dev projects I have come across over some 35 years of computer use. Kudos.
 
  • Like
Reactions: MacRumors3590
OCLP 0.6.5 was finally released today and I just installed it on my TestOS 13.3.1 and then updated to 13.3.1(a), which was offered to me immediately (late 2013 iMac 27"). Then post install again with OCLP 0.6.5.
Both Parallels 18 VMs (W10 and W11) now start again although AMFI remains "disabled" by OCLP. I will watch the forums for a while before I update my regular OS accordingly (currently still 3.2.1/0.6.1).
 
I recall the Lilu plugin "OpCodeEmulator." I thought this plugin was supposed to emulate opcodes, including AVX2 on platforms where native OpCode support was not available. If there is hope for pre-Haswell platforms, could OpCodeEmulator be a possible solution? OpCodeEmulator
 
Last edited:
  • Like
Reactions: houser
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.