macOS 13 Ventura on Unsupported Macs Thread

[drastar999]

Due to the typos in your post, it is really hard to understand what happened and where you stand now.
That is, there is no macOS 14.4 or 14.4.1 (c). Did you mean 13.4 and 13.4.1 (c)?
macOS 13.4.1 should install with OCLP 0.6.7. If you have trouble installing that version there are 2 things you might try.
1. Create another Admin User in the System Settings/Users and Groups, enable fast user switching, switch to the new User and try the OS 13.4.1 install again using the full installer available here;

macOS Ventura Full Installer Database. Download Directly from Apple!

Download macOS Ventura full installer with one click straight from Apple! Every version of Ventura Beta & Final available all in one place!!

mrmacintosh.com

2. Try the nightly OCLP 0.6.8 available here; and then the OS 13.4.1 full installer

OpenCore-Legacy-Patcher/SOURCE.md at main · dortania/OpenCore-Legacy-Patcher

Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.

github.com

The 13.4.1 (c) SRS should be available (Software Update) after you start up in 13.4.1.

thanks for replay,
oh i see the confuse typos in my text. i mean 13.4 🙈
- installed is 13.4 - and the update to 13.4.1 is show in the system settings
- i update oclp from 0.6.6 to 0.6.7 and reboot
- after this, i cant't see the update - no updates available
- and now the update to 13.4.1(c) is occurred - and fails on installing

 

[davidlv]

thanks for replay,
oh i see the confuse typos in my text. i mean 13.4 🙈
- installed is 13.4 - and the update to 13.4.1 is show in the system settings
- i update oclp from 0.6.6 to 0.6.7 and reboot
- after this, i cant't see the update - no updates available
- and now the update to 13.4.1(c) is occurred - and fails on installing

There are many cases where the Software Update will fail, especially when running OCLP. You need to try the full installer I mentioned in my prior post.
Depending on the other software you have installed, you may need to create a new User and in that minimal setup, try to install 13.4.1 using the full installer. The update to 13.4.1 (c) should be done last of all.
The RSR (13.4.1 (c) ) update requires a Haswell or later CPU (2013 or later). See post # 6585 above.

 

[rehkram]

Is there a quick way to determine if a given update is safe to install or not, without having to read through the last few pages of this thread every time?

Nope. I wish people would just read through this thread, maybe do a couple of searches, before asking questions. It kind of clogs up the thread. Oh and putting what h/w and s/w versions you're running in your profile signature would be a great help. Jeesh!

Thank you.

 

[trifero]

Hi trifero, Thanks for the heads up on that.

I'm a wired mouse and keyboard kind of guy, which is why the USB 1.1 patch was of more concern to me, but I'll probably update the module anyway (it looks fairly easy to do). So, this only happened before you installed the new module?

Thanks

Don´t know. That module was installed about 4 years ago.

 

[Tockman]

Is there a quick way to determine if a given update is safe to install or not, without having to read through the last few pages of this thread every time?

And is there a way to bear a child for a month instead of nine?

 

[makra]

Is there a quick way to determine if a given update is safe to install or not, without having to read through the last few pages of this thread every time?

How quick do you want it to be? If you don't install updates immediately, searching this thread after some weeks for the version number will give you quite reliable information whether users have experience major problems. No guarantees of course.

 

[deeveedee]

Is there a quick way to determine if a given update is safe to install or not, without having to read through the last few pages of this thread every time?

We've seen in this thread that one's success does not guarantee another's. Having a way to recover is important. My production volume is backed by Time Machine and I maintain "sandbox" volumes for testing new macOS versions and updates. If you have a single Mac for testing, no changes or updates are without risk, but you can minimize risk by having a recovery mechanism and keeping a production volume untouched until you have tested in another volume. Before you modify the EFI on your SSD, first install the EFI to a bootable USB device and test by booting from the USB device before installing the EFI to your production SSD.

 

[antibolo]

Yes, I understand that things aren't that simple and that there may be various issues on various different models of hardware.

But may I suggest that whenever a new update introduces some major breakage (like when 13.3 broke a whole bunch of AMD graphics drivers), there should at least be a noticeable warning (ie. not burried in a collapsable section) on the first post of this thread?

 

[TOM1211]

Yes, I understand that things aren't that simple and that there may be various issues on various different models of hardware.

But may I suggest that whenever a new update introduces some major breakage (like when 13.3 broke a whole bunch of AMD graphics drivers), there should at least be a noticeable warning (ie. not burried in a collapsable section) on the first post of this thread?

Problem being no one would know until release? By that time someone would of installed it that shouldn’t can’t predict if it will work or not.

 

[antibolo]

Problem being no one would know until release? By that time someone would of installed it that shouldn’t can’t predict if it will work or not.

Of course I meant after release.

 

[deeveedee]

Yes, I understand that things aren't that simple and that there may be various issues on various different models of hardware.

But may I suggest that whenever a new update introduces some major breakage (like when 13.3 broke a whole bunch of AMD graphics drivers), there should at least be a noticeable warning (ie. not burried in a collapsable section) on the first post of this thread?

I think you're describing the Readme and Issues that are maintained by the OCLP Devs in GitHub. As much as the Devs have tried to make OCLP a "blackbox appliance that you never need to open or understand," once you commit to using OCLP on your Mac, it is not "set it and forget it." You as the owner of your revitalized, unsupported Mac have a responsibility to monitor multiple sources (including this thread). In my opinion, if anyone is not ready to assume that responsibility, they probably shouldn't be using OCLP and should probably just purchase a new Mac.

 

[antibolo]

I think you're describing the Readme and Issues that are maintained by the OCLP Devs in GitHub. As much as the Devs have tried to make OCLP a "blackbox appliance that you never need to open or understand," once you commit to using OCLP on your Mac, it is not "set it and forget it." You as the owner of your revitalized, unsupported Mac have a responsibility to monitor multiple sources (including this thread). In my opinion, if anyone is not ready to assume that responsibility, they probably shouldn't be using OCLP and should probably just purchase a new Mac.

Again, I understand that. All I'm saying is that serious issues should be better communicated.

Anyway, I don't wish to derail this thread any further, so I'll just go away now.

 

[TOM1211]

Of course I meant after release.

it’s impossible to have a one a one size fits all across so many different products available and different hardware configurations all you can have is a try at your own risk disclaimer.

 

[rehkram]

Right. So now can we please keep this thread free from irrelevant chit chat about what should or should not happen. Stick to facts please. Be self reliant. Use search. No free lunch for you or I.

 

[antibolo]

Right. So now can we please keep this thread free from irrelevant chit chat about what should or should not happen. Stick to facts please. Be self reliant. Use search. No free lunch for you or I.

I'm sorry I offended you.

 

[trifero]

And is there a way to bear a child for a month instead of nine?

For me , it´s always safe. Some decades ago that I don´t install a single thing without a full backup. 😉

Even, I conserve tha full Backup of my Mac Pro 1,1... 🤦🏻‍♂️

 

[trifero]

Right. So now can we please keep this thread free from irrelevant chit chat about what should or should not happen. Stick to facts please. Be self reliant. Use search. No free lunch for you or I.

I agree. Lastly, a lot of cry babies and people telling what should or sould not do.

 

[OKonnel]

I have reverted back to the same setup as @OKonnel 14,2 Imac macOS 13.2.1 OCLP 0.6.7 Release. with no improvement to adobe camera raw AI Denoise which i believe is the same as Lightroom classic Ai denoise each image about 20min. @OKonnel did you have any luck with your test? What i have noticed since moving to Ventura is certain programs aren't utilising the GPU correctly such as videoproc unable to test HEVC, DXO photolab (Denoise) and premier pro (rendering footage).

Guys and dear @Morphd I'm sorry I couldn't answer but, in this period, I haven't been to the computer at all due to various family and work commitments. I hope to be able to verify the various problems mentioned soon.
However, it must be considered that iMac 14,2 can have different GPUs and different amounts of RAM and VRAM. In my case I have an i7 CPU with 24GB of RAM and an nVidia GeForce GTX780M GPU with 4GB of VRAM. At the time, it was the top graphics configuration in Apple BTO purchases.
Greetings to everyone!

 

[OKonnel]

I have reverted back to the same setup as @OKonnel 14,2 Imac macOS 13.2.1 OCLP 0.6.7 Release. with no improvement to adobe camera raw AI Denoise which i believe is the same as Lightroom classic Ai denoise each image about 20min. @OKonnel did you have any luck with your test? What i have noticed since moving to Ventura is certain programs aren't utilising the GPU correctly such as Videoproc unable to test HEVC, DXO Photolab (Denoise) and premier pro (rendering footage).

Hi @Morphd! Meanwhile I just tested the AI Denoise of Photoshop Beta 24.7.0 and Camera RAW 15.4.1.1510 and it responded very quickly. The Camera RAW's Denoise filter loaded a 9MB Nikon RAW file in seconds and when I turned on AI Denoise it said it would take 6 minutes, but two or three seconds later it finished...
As for HEVC files, unfortunately I don't have any; however I have Videoproc and if you send me a link from which I can download some HEVC files I can try and let you know.
As soon as I can, I will also test DXO Photolab (Denoise) and let you know

EDIT
I also tested DXO Photolab (Denoise) and again everything happens fast.
I specify that I'm using OCLP AMFIPass Beta 4 but I can't tell you if everything is fine in my case thanks to AMFIPass Beta 4 or if it depends on my hardware and the RAM and VRAM indicated in my signature and in my previous answer (to you)

 

[mikelets456]

Just updated to macOS 13.4.1(c) on a Macbook pro (mid 2014). After updating the system didn't start up, I had to start on safe mode pressing Shift and then reinstall Root Patch. After reboot everything is working again.

Thanks for the update. I have a 2015 11,4 MacBook Pro....13.4.1c states 6 MB update? I was surprised as I'm used to seeing 11.6 GB updates. Is all still working? I might wait a bit longer before applying this patch...same process, correct?

 

[astraco]

Thanks for the update. I have a 2015 11,4 MacBook Pro....13.4.1c states 6 MB update? I was surprised as I'm used to seeing 11.6 GB updates. Is all still working? I might wait a bit longer before applying this patch...same process, correct?

13.4.1(c) is a security update, I don't know how big it's but I think the are two: One that replaces 13.4.1(a) and another one that just fixes the bugs in Safari, probably that's why it's so small.

Everything is working since the update, don't know the differences between 2014 and 2015 Macbook Pros but if yours is working with OCLP 0.6.7 it should still work after the update.

 

[h2kskull]

Deleted

 

[olad]

deleted

 

[Larry-K]

Just to let you know that once I updated my Mac Pro 5,1 to Ventura, I also updated my Macbook Pro M1 16" and my Macbook 12" 2015. And while working on my Mac Pro I noticed a very strange thing: the pointer disappeared of the screen now and then...

Yes, I forgot about Universal Control, 🤪.

I confim you that it works like a charm also. For that, I supose the Wifi/bluetooth module is necessary.

Hi trifero,

How many reboots did you have to do at the end of the Ventura Installation?

I must be past fifty now, and as patient as I am, I suspect I'm stuck in a Boot Loop.

Wouldn't have bothered you, but I couldn't find a relevant post.

Thanks

 

[Synaesthesia242]

Hi trifero,

How many reboots did you have to do at the end of the Ventura Installation?

I must be past fifty now, and as patient as I am, I suspect I'm stuck in a Boot Loop.

Wouldn't have bothered you, but I couldn't find a relevant post.

Thanks

Try holding down option while booting and selecting the OCLP booter.