FYI SilentKnight update alert this evening:
XProtect 2163, 78 should be 2163, 83
XProtect 2163, 78 should be 2163, 83
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
It’s all about all the Dev’s brilliant minds and hard work involved with this project .👍
Last edited:
I can only confirm it's safe on my supported 2018 intel Mac mini. Safari has never been an issue for me.
I don't run betas on my unsupported mac, preferring to wait for public releases of both macOS and OCLP. Unsupported Macs are in lock-step with OCLP dev, we need to keep that in mind. As soon as the moon and stars are aligned, jump!
Last edited:
Funny... I have the same iMac and had to install the Root Patches because after the install the screen wasn't recognized as an Apple built-in but as a 3rd party monitor, which broke the resolution (huge screen space). Also the control keys of the keyboard weren't working.
After installing the root patches it all came back to normal.
Guys, I'm new to dis... How will OpenCore handle the future OS updates?
Hello to all,
Successful installation of Ventura 13 beta 11, followed by update to Ventura 13.1 beta1 on late 2012 iMac 13,2.
Method:
While booted into Monterey, and using Disk Utility, created a 200 GB APFS partition on iMac’s (original) internal
1 TB Fusion HDD. Drive has two other partitions (for total of three); other partitions hold Catalina and Monterey.
Downloaded latest OCLP patcher from Dortania; (then) OCLP 0.5.0
While booted in Monetary, build and installed OCLP onto USB thumb Drive and iMac’s internal HDD.
Downloaded latest, then available, Ventura beta installer from Mr. Macintosh site ( Ventura 13.0 22A5373b B11 P9)
Created a USB Ventura installer via OCLP’s build-in function (selection in OCLP’s main menu)
Booted into USB Ventura installer and proceeded to install OS onto designated internal HDD partition.
It required few reboots to complete, including a stall (latter required hard reboot), but Ventura fully installed.
Installation does necessitate a level of vigilance, to make sure that during reboots, boot-picker points to the appropriate installer, e.g. install MacOS , or in latter phases, Ventura (Beta) icon, rather than inadvertently reboot into other operating system version (or not at all).
Applied post install patches while booted into Ventura.
Rebooted without incidents, into fully functional, accelerated Ventura 13 beta11.
Updated to Ventura 13.1 Beta1 via the OTA route without problems.
Applied (latest?) Post-install patches using OCLP 0.5.2n. On reboot found Ventura 13.1 beta1 fully operational, and very responsive. Appears to perform significantly faster than Monterey.
Applications, such as MAPS, GIMP, Blender, LibreOffice, Safari and FireFox (developer edition) perform as expected; no problems noted with playing any video content, inclusive of YouTube.
Tremendous thank you to all the superb developers.
Successful installation of Ventura 13 beta 11, followed by update to Ventura 13.1 beta1 on late 2012 iMac 13,2.
Method:
While booted into Monterey, and using Disk Utility, created a 200 GB APFS partition on iMac’s (original) internal
1 TB Fusion HDD. Drive has two other partitions (for total of three); other partitions hold Catalina and Monterey.
Downloaded latest OCLP patcher from Dortania; (then) OCLP 0.5.0
While booted in Monetary, build and installed OCLP onto USB thumb Drive and iMac’s internal HDD.
Downloaded latest, then available, Ventura beta installer from Mr. Macintosh site ( Ventura 13.0 22A5373b B11 P9)
Created a USB Ventura installer via OCLP’s build-in function (selection in OCLP’s main menu)
Booted into USB Ventura installer and proceeded to install OS onto designated internal HDD partition.
It required few reboots to complete, including a stall (latter required hard reboot), but Ventura fully installed.
Installation does necessitate a level of vigilance, to make sure that during reboots, boot-picker points to the appropriate installer, e.g. install MacOS , or in latter phases, Ventura (Beta) icon, rather than inadvertently reboot into other operating system version (or not at all).
Applied post install patches while booted into Ventura.
Rebooted without incidents, into fully functional, accelerated Ventura 13 beta11.
Updated to Ventura 13.1 Beta1 via the OTA route without problems.
Applied (latest?) Post-install patches using OCLP 0.5.2n. On reboot found Ventura 13.1 beta1 fully operational, and very responsive. Appears to perform significantly faster than Monterey.
Applications, such as MAPS, GIMP, Blender, LibreOffice, Safari and FireFox (developer edition) perform as expected; no problems noted with playing any video content, inclusive of YouTube.
Tremendous thank you to all the superb developers.
Attachments
Last edited:
MacBook 2016: So easy to install Ventura with OCLP. Thanks to everyone involved.
Not difficult.
Let's say Apple releases Ventura 13.1 and it shows up in Software Update as OTA.
You can go ahead and apply that update as per supported mac. Once reboot done, re-apply OCLP root patch, reboot and that's it.
OCLP will probably auto-prompt anyway.
I realised MBP 13,3’s are also not supported on Ventura, so not surprising that it wouldn’t boot. Spoofing an MBP 14,3 machine seems to work a lot better: AirPlay Receiver & UC options now seem to be back.
How did you update? It's mentioned on this thread the recommended way is to create a USB installer with OpenCore patcher and do either do an upgrade / clean install that way. I'm glad you were able to get it working by applying the root patches after install. Mine either did it automatically, or since I had Monterey installed, it kept what was needed from that. Mr. Macintosh makes reference to this situation in his video here:
In this video, he uses a 2015 MBP, different machine, but same results I had with the iMac.
OCLP doesn't do it - all the patches from previous installation get wiped out.
As far as I know, 0.5.1 supports that machine. It was released yesterday. I don't have that Mac Pro, but it's still the version I used to patch the iMac.
I was expecting to apply them after the upgrade, but after going into post install patcher, it said they were already installed, and the graphics like Dock and menu bar, the display, etc all worked. While the installer was running, yes the graphics were not correct then, and everything was tiny. However on the last reboot into the OS, everything came back normally, and I didn't have to do anything. The only message I got from OCLP after the upgrade was to install to the internal drive vs the USB drive. I came from a natively supported OS to one that needs OCLP. Wonder if that's why I already had the native patches. All I know is the machine didn't need anything else than what I mentioned in my posts.
This is what I saw after checking the root patch status yesterday.
I wanted to update XProtect using SlientKnight on my Mac mini running Monterey. After hitting the update button in the app, the machine rebooted and began to install Ventura without me taking any action. Not quite what I was expecting.
Worth noting that there is a new version of SilentKnight - V2. Check it out.
SilentKnight version 2 is designed for Catalina to Ventura
Provides more details including scans of XProtect Remediator, and a Settings dialog. Documentation now explains how to deal with difficulties updating.
eclecticlight.co
I too had SilentKnight listing XPR as outdated on my 12.6.1 but also Ventura Update was listed. I pressed "Install all updates" in SilentKnight hoping it would update XPR... My Mac began downloading, after 2 Gigs I made a restart because I feared it would update my main disk to ventura.
I hit the "x" to stop Ventura from downloading in System Preferences and it did appear to stop. But somehow it decided to continue without me noticing it and the installation proceeded when I was away from the computer. It's surprising that the system can perform a major update like this without requiring some sort of input from me, like a password at the very least. Anyway, Ventura is running fine on my internal drive now. I was planning to wait and see if some of the remaining bugs were ironed out before upgrading, but here I am. I still have some problems in Ventura with Python libraries that I depend on. Hopefully those will be updated soon.
On my MacBookPro13,1, the UI is overall sluggish and Chrome takes roughly a minute to load completely upon initial launch (i.e. blank window before new tab page appears). This is a clean install of Ventura (clean install of Monterrey followed by OCLP/Ventura). It appears like spotlight is done indexing. Any ideas why this might be? Or is my Skylake dual-core 2.0GHz CPU starting to show its age?
Hey guys, got a strange issue here, and I'm not sure if it's a Ventura issue, or OpenCore issue. Everything is working as expected with the same speed as Monterey (natively supported) Under Ventura though, Chrome, and all Chromium based browsers such as Brave, Edge, etc all load slow. Maybe about 10 to 15 seconds to open to a viewable page. On startup they show a blank window, and then the site and elements load, and then things work normally. Has anyone else experienced this? Safari, and Firefox load normally, and after Chrome, or a Chromium based browser are fully loaded, then they work normally too. Is there a way to fix the slow startup of these browsers under Ventura? Thanks
I'm having the same issue with a late 2015 5K 27" iMac. It's all Chromium based browsers that seem to have the issue. Everything else works fine. Mine was an upgrade over Monterey 12.6.1. This sluggish issue with the said browsers is my only report of problems after installing Ventura.
Installed Ventura on my early 2015 MacBook Air last night, played with it for about an hour or two and it seems to work perfect like Monterey which was supported did, however noticed a strange thing..... when I close the lid, it doesn't seem to put the laptop completely asleep..... maybe it is because it is doing something "behind the scenes" but not sure. Maybe it will act normal and go to sleep when I have completed my 4 hours that I am willing to put into my 8 hour salaried work day. Will have to see then, otherwise why do it not sleep completely?
I upgraded from Monterey 12.6.1 to Ventura on MBP2015 (intel only). After the upgrade root patched to fix the acceleration. No USB involved.
OCLP 0.5.1 with Ventura Beta (build 22C5033e) installed on an Early 2015 13-inch i7 3.1GHz/16GB/1TB MacBook Pro. Everything seems to work smoothly so far.
Thanks to the hard work everyone on the dev team has put to make this a possibility. If I run into any issues I will be happy to feed them back to help improve the overall quality of this installer. Awesome work!
Thanks to the hard work everyone on the dev team has put to make this a possibility. If I run into any issues I will be happy to feed them back to help improve the overall quality of this installer. Awesome work!
i don't have any issues, although i used hibernation mode to save battery due to third party Nvme I've used with my 2015 MBP.