I will give it a try then. That's exactly what Dortania's guide instructs when installing MacOS 13 on Skylake - spoofing the Skylake GPU to a Kabylake GPU.
UPDATE: Tried and the computer stopped booting.
Last edited:
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
UPDATE: Tried and the computer stopped booting.
Update 13.3.1 (see #4745 above) offered in Software Update of MBP11,4/14,3. I undid the root patch, restarted, performed the update (about 1.3 Gb), restarted, applied root patch, restarted. Everything working.
Last edited:
Upgrade OTA from Ventura 13.3 to Ventura 13.3.1 on my iMac 27" mid 2011 + AMD WX4130 (Dell) + BCM 94360CD , all is ok:
That's helpful. Actually I think, that all those incidents could be MacFuse-related, because I use it alongside Cryptomator on all my machines. So at least I know now, when I should be extra careful - if we could find a way to stop the update process. But for now I won't use Crytomator...
Preview issue solved by today's OCLP nightly build and macOS 13.3.1.
I am sorry, you lost me. Preview in Finder? I didn't have any problems before. I don't, still. Preview works here.
Updated from Monterey to Ventura 13.3 for my iMac11,2 M5100. All is good except for one extra menu icon for which I've never seen before. Any ideal?
Add: Preview works, including for jpeg/png photos, together with "Remove Background" feature. And the latest OCLP 063n (root patches) has fixed my Kepler iMac12,2 Preview issue running 13.3. However, the "Remove Background" feature and "Live Text" capture are still not working on the Kepler iMac12,2.
Add: Preview works, including for jpeg/png photos, together with "Remove Background" feature. And the latest OCLP 063n (root patches) has fixed my Kepler iMac12,2 Preview issue running 13.3. However, the "Remove Background" feature and "Live Text" capture are still not working on the Kepler iMac12,2.
Last edited:
Agree. But it never showed up in Monterey and there is no such slot in this iMac.
not worried, only a bit annoyed though 😅
Add: This iMac11,2 has an upgraded Xeon CPU. I suspect OCLP may have spoofed to something else which may lead to this extra icon. Will have a more closer look later.
Looks good for me OCLP 0.6.3 Build from command Line
HP Probook 650 G1 Intel HD 4600
Thanks All Dev's
HP Probook 650 G1 Intel HD 4600
Thanks All Dev's
Sorry I guess I didn't makebmy self clea enough, In 13.3 png files would show as grey image in the Preview app, dos tha still happen in 13.3.1?
That has been posted many times, use the search function for this thread. or See Post #4736
Last edited:
OpenCore-Patcher app: I notice it resides in Library>Application Support>Dortania
I also have it in Applications.
Do I need both? Same version, same dates. 703MB x 2...
I also have it in Applications.
Do I need both? Same version, same dates. 703MB x 2...
Ah cool. Hopefully Apple are fixing their share of the 13.3 bugs. I commend you brave souls who are installing 13.3.1
Personally I've decided to wait until the dust clears, and the OCLP devs have had time to address the issues raised by the new code. I'm betting good money there will be more changes to come, probably for the better, stability-wise.
Patience is usually a virtue.
Personally I've decided to wait until the dust clears, and the OCLP devs have had time to address the issues raised by the new code. I'm betting good money there will be more changes to come, probably for the better, stability-wise.
Patience is usually a virtue.
Last edited:
The one in the Applications folder should be an alias. If it is a real application, you can delete it and make an alias from the one in the Library/Application Support/Dortania folder by holding down the Option+Command keys and drag to the Applications folder. I have even seen cases where there were two aliases in my Application folder, but not recently.
Last edited:
Interesting, it seems odd for an app to be in the support folder. Usually application "items" are in that folder.
The one in my Apps folder is not an alias. I put it there manually each time, not realizing until today that the support version existed. Somehow... It must auto-generate or something.
Out of curiosity, I checked and yes, there is a copy of the patcher in the Applications Support folder, same version (modified 02.04.2073), same size (~704Mb), but different 'Date Modified' (03.04.2023 (App. Support) vs 07.04.2023 (Applications Folder)). I think that indicates that the last changes made to 0.6.3n were on 02 April. If there is no pressing space need, I suggest you leave both be.
Last edited:
I have done an experiment:
Earlier today I rebuilt OpenCore and applied the patches using the latest nightly as of today, while remaining on 13.2.1 (since reports for 13.3.1 were positive, I was getting ready).
Right now I deleted both copies of the patcher and redownloaded it. It's in my Downloads folder, of course.
Normally I would then move it to Applications but for now I will run it as-is and see what happens.
Upon launch it verifies, then opens but does not replicate itself anywhere.
Same after moving to Applications.
I bet if I were to Build and Install OpenCore again, the patcher would replicate to Application Support, but since I already did that earlier, I won't do it again right now. And perhaps because I did exactly this earlier, that's where the same-date/same-version copy came from.
It is always best to use the "release" versions (now 0.6.2) if that is sufficient for the hardware/os version concerned, as that version will have most of the bugs in OCLP itself worked out. However, given the many bugs found in the latest Ventura OS versions, the nightly versions are often able to cope with that fluid situation. An example is the Preview bugs showing their ugly heads recently. The latest nightly (see post 4736) has some of that under control.
Therefore, it may well be best to delete both of those different older versions of OCLP, and install the latest nightly.
Of course, as it is a nightly beta version, don't ask the devs for help if you get in trouble, simply revert back to the release version and carry on.
I was happily running Monterey on my 2011 MBA 4.2 13" with OCLP 0.6.1 when Safari began to play up telling me I needed WebGL to continue listening to Radio Garden.
I decided it was opportune to go to OCLP 0.6.2 and load Ventura 13.3.
This has presented a Safari problem. When I open a website, I might get a single header and the rest of the page is white. If I click on another app I have open like Disk Utility then the safari page becomes normal, but when I click anywhere on that safari page again, after a couple of seconds it goes back to white.
I upgraded to 13.3.1 but there is no difference.
Anyone else had this?
I decided it was opportune to go to OCLP 0.6.2 and load Ventura 13.3.
This has presented a Safari problem. When I open a website, I might get a single header and the rest of the page is white. If I click on another app I have open like Disk Utility then the safari page becomes normal, but when I click anywhere on that safari page again, after a couple of seconds it goes back to white.
I upgraded to 13.3.1 but there is no difference.
Anyone else had this?
Right now I am running 13.2.1 but with the latest nightly OpenCore and post-patches, and all seems well (except for weird Safari Tech preview stuff, but that was already happening with the 0.6.2 release).
FF and Chrome work just fine.
I will wait until the final release of 0.6.3 before moving to 13.3.1
I'm on a 2013 MBA and having Safari issues, no matter which version I use. I keep intending to abandon Safari but I like its look and feel...
On supported Macs, Safari is just fine. And it was on this unsupported MBA until the last Tech preview update (the Preview was my workaround because the regular version behaved so badly for awhile now).
Pages won't fully load (or load at all), typing is weird, etc. I ran today's nightly to see if it would help, but no, at least not while on 13.2.1
So if you're having these issues with no resolution, use another browser until whatever the issue is is addressed.
