macOS 12 Monterey on Unsupported Macs Thread

[deeveedee]

After upgrading to Safari Version 15.6.1 (17613.3.9.1.16) in Monterey 12.6.4 (and now 12.6.5), I am finding that I am unable to "Remove All" Website Data. "Safari > Preferences > Privacy > Manage Website Data > Remove All" does not remove all data. I have tried without success to remove the directory contents mentioned here. Is anyone else observing this in Safari? Does anyone have suggestions for fixing this and/or removing Website Data? Thank you.

 

[TimmuJapan]

I'm not certain and I don't have your config.plist to inspect, but it may be that your OC config.plist needs to be revised. Look at OCLP-Version (highlighted below) in your config.plist. Make sure that it matches the OCLP version that you are using to install post-install patches. I have only had to update this value each time I updated OCLP in order to get rid of the pop-up screen that you observed.

View attachment 2187788

I appreciate your advice, but I solved this via other means.

@sinbad21 nailed it in post #8,623.

 

[deeveedee]

@TimmuJapan For those who are not uninstalling OCLP from their rigs, other approaches to eliminate the pop-up window are necessary. We're all fortunate that there are multiple ways to solve our issues and that we're all sharing what we've learned.

 

[TimmuJapan]

@TimmuJapan For those who are not uninstalling OCLP from their rigs, other approaches to eliminate the pop-up window are necessary. We're all fortunate that there are multiple ways to solve our issues and that we're all sharing what we've learned.

True true, but actually I am not uninstalling OCLP from my rig….. I just don’t need OCLP in the quasi hidden applications support folder (which causes that pop up) to use it the way I need to, so @sinbad21 ’s advice was most suitable for me…. Thanks for your input too, though.

 

[deeveedee]

@TimmuJapan The pop-up is caused when the installed version of OCLP is newer than the OCLP-Version string in config.plist. Glad you found another way to "fix" this.

EDIT: I actually think that the pop-up message is misleading. I never would have guessed the OCLP-Version string from the pop-up message and am only relaying what was taught to me.

 

[sinbad21]

I give more information: if you patch your system with OCLP, the patcher installs a copy of OCLP in the /Library/Application Support/Dortania folder. It also creates the file /Library/LaunchAgents/com.dortania.opencore-legacy-patcher.auto-patch.plist.

Every time you boot your system, this process is started and performs the check that your OCLP version in EFI is not lower than the version that was used to patch the system.

 

[quarkysg]

I give more information: if you patch your system with OCLP, the patcher installs a copy of OCLP in the /Library/Application Support/Dortania folder. It also creates the file /Library/LaunchAgents/com.dortania.opencore-legacy-patcher.auto-patch.plist.

Every time you boot your system, this process is started and performs the check that your OCLP version in EFI is not lower than the version that was used to patch the system.

I have the same understanding as what you wrote. So what I understood of the process is that there could be a problem if the bootloader (i.e. EFI) is of a lower version compared to the drivers installed in the OS partition. I suppose higher version in the bootloader with a lower version of patched drivers in the OS partition is OK, as usually higher version should support lower version, but not vice-versa.

But I would think it should be good to use the same versions of both bootloader and patched drivers, as those are at least tested by the developers.

 

[aesnau1]

Yes, catastrophic. Patch fails, impossible to create a new snapshot. Safari bugs as reported above. Wait before doing this update!
edit : solved, it was a specific problem.

Successfully built new kernel cache
2023-03-28 14:06:17,009 - sys_patch.py (350): - Creating new APFS snapshot
2023-03-28 14:06:17,043 - sys_patch.py (359): - Unable to create new snapshot
2023-03-28 14:06:17,060 - sys_patch.py (360): Reason for snapshot failure:
2023-03-28 14:06:17,079 - sys_patch.py (361): Can't use last-sealed-snapshot or create-snapshot on non system volume

2023-03-28 14:06:17,096 - sys_patch.py (363): - This is an APFS bug with Monterey and newer! Perform a clean installation to ensure your APFS volume is built correctly

Hi can you tell me what you did to fix this? I did see your other post but I don't know what to do. hope you can help?
Thank you.

 

[aesnau1]

After 2 days of research, I found a solution, by replacing in sys_patch.py the path for mounting the system volume in r/w.

Instead of :

/System/Volumes/Update/mnt1

I chose a custom mount point :

/Users/myuser/Downloads/mnt1

edit: finally, I understood the origin of the problem: normally, this /System/Volumes/Update/mnt1 folder is empty when nothing is mounted on it. In my case, there was a whole system, I deleted everything and the problem is solved.

Can you share how you fix the issue? Thanks

 

[sinbad21]

Can you share how you fix the issue? Thanks

OCLP failed to patch my system because my /System/Volumes/Update/mnt1 folder was not empty. First I found a solution by choosing another mount point but there was a much easier solution : to trash all the content of this folder. After that OCLP had no problem to patch the system.

 

[surszki]

imac 2008 monterey works fast (I was surprised), but sometimes the screen freezes and only hard power off helps.

 

[deeveedee]

After upgrading to Safari Version 15.6.1 (17613.3.9.1.16) in Monterey 12.6.4 (and now 12.6.5), I am finding that I am unable to "Remove All" Website Data. "Safari > Preferences > Privacy > Manage Website Data > Remove All" does not remove all data. I have tried without success to remove the directory contents mentioned here. Is anyone else observing this in Safari? Does anyone have suggestions for fixing this and/or removing Website Data? Thank you.

I noticed that I had a Safari Update notification for Safari 16.4.1. I applied the update (still running Monterey 12.6.5) and the tracking cookies disappeared. "Safari > Preferences > Privacy > Manage Website Data > Remove All" is working normally now. My only guess is that my previous Safari update did not apply properly and I'll chalk this one up to user error.

 

[Giovamille959]

For my MBP 2011 I was looking forward the OCLP 0.6.3 to fix the Safari rendering problem. As soon as it was formally available I run it to upgrade OTA the OS to 12.6.5 and Safari to 16.4.1. Everything was smooth and 0.6.3 was able to fix the rendering problem. It seems I can also use "google maps" with Safari ... can you believe it? Thank you to the incredible development team!

 

[lkar]

I have a 2014 15" MBP, do I have to install Monterey first to update my stock SSD with the new firmware (in case I want to get a new thirdparty SSD in the future, because third party SSDs only work with a firmware update that only gets installed into the computer if I install Monetery on a stock SSD)

or

can I jump from Big Sur to Ventura (or even later in the future) and still have that firmware updated on my computer (I am assuming anything firmware related Monetery does, Ventura will do to my computer as well), for what I want to get a bigger capacity new SSD in the future? Does this thinking make sense?

 

[mwidjaya]

I have a 2014 15" MBP

That MBP11,3 goes up to Big Sur only, without OCLP. The firmware update(if any) is "integrated" into Big Sur updates.

So even if you have replaced SSD with third party one, you will need to have a volume/partition running Big Sur to "catch" firmware update(s) going forward.

I keep a small volume (50GB) of Big Sur for that very purpose. This will not be needed once Apple stops updating Big Sur completely.

 

[lkar]

That MBP11,3 goes up to Big Sur only, without OCLP. The firmware update(if any) is "integrated" into Big Sur updates.

So even if you have replaced SSD with third party one, you will need to have a volume/partition running Big Sur to "catch" firmware update(s) going forward.

I keep a small volume (50GB) of Big Sur for that very purpose. This will not be needed once Apple stops updating Big Sur completely.

I don't plan to update to monetery via OCLP for at least another year, so it will stay Big Sur for a while, by the time then there will be no more future mid year Big Sur updates.

But when I do update to a newer OS, my questions still stands, will I need to do a small jump to Monetery, or skip it all together and go to Ventura (or later) and still get the benefit of the SSD firmware update that came with Monetery?

 

[mwidjaya]

get the benefit of the SSD firmware update that came with Monetery?

What is this SSD related update? Please elaborate. Is this related to power regulation (hibernation)? Why do you think it is Monterey specific?

AFAIK, firmware updates are consistent with all currently supported macOS, i.e. across Ventura, Monterey, Big Sur.

So if your Big Sur is up-to-date, you would have gotten firmware update related to third party SSD.

 

[lkar]

What is this SSD related update? Please elaborate. Is this related to power regulation (hibernation)? Why do you think it is Monterey specific?

AFAIK, firmware updates are consistent with all currently supported macOS, i.e. across Ventura, Monterey, Big Sur.

So if your Big Sur is up-to-date, you would have gotten firmware update related to third party SSD.

https://forums.macrumors.com/threads/ssd-not-supported-to-install-monterey-how-can-i-update-firmware.2343841/?post=32090938#post-32090938

So what is your answer now in light of this new info?

 

[mwidjaya]

Nothing new. Known problem and also answered in that thread itself.

In some cases, installing macOS fails if it does not "see" an Apple disk.

This is why some people proceed in a certain manner when upgrading to third party SSD; they connect the new SSD externally and install macOS, do data migration (in effect cloning the current SSD). Physically replacing the SSD is the last step.

 

[lkar]

Nothing new. Known problem and also answered in that thread itself.

In some cases, installing macOS fails if it does not "see" an Apple disk.

This is why some people proceed in a certain manner when upgrading to third party SSD; they connect the new SSD externally and install macOS, do data migration (in effect cloning the current SSD). Physically replacing the SSD is the last step.

In the future, when I want to upgrade from my current OS (big sur) + a new third party SSD, to a ventura and up:

do i have to install monetery onto my original Apple SSD first (via OCLP) [which will also update the firmware on my mac!] and then switch to the third party SSD and do a data migration, and then upgrade again to ventura? (this requires TWO OS installs + a data migration)

or

can I install ventura onto my original Apple SSD first (via OCLP) and then switch to the third party SSD and do a data migration? (this way skips a monterey OS install, but i still have to do a data migration)

or

can I install ventura (via OCLP) directly onto the third party SSD? (best and fastest way)

=

Do you understand what I am getting at? I think my original post was not clear enough, I hope this is better, I am trying to save time by not doing unneeded OS installs and migrations.

 

[mwidjaya]

In the future, when I want to upgrade from my current OS (big sur) + a new third party SSD, to a ventura and up:

- accessing the SSD port/connector in 2014 MBP is easy
- macOS install is also not hard
- recommended OCLP method is also clean install and fresh start with manual data migration

With above in mind, you can try the most direct route first:
- prep OCLP installer usb stick, swap SSD, boot usb stick and install Ventura

If that doesn't work, you can fallback to more circuitous method(s).

Edit: One last thing, messing around with OCLP, you have to accept "wasting" time because it is not perfect and sometimes you just have to redo from scratch.

 

[lkar]

- accessing the SSD port/connector in 2014 MBP is easy
- macOS install is also not hard
- recommended OCLP method is also clean install and fresh start with manual data migration

With above in mind, you can try the most direct route first:
- prep OCLP installer usb stick, swap SSD, boot usb stick and install Ventura

If that doesn't work, you can fallback to more circuitous method(s).

Ok, so you don't know the answer, that is fine. I am interested if anyone else has tried what I am suggesting above and what did or didn't work?

 

[makra]

Ok, so you don't know the answer, that is fine. I am interested if anyone else has tried what I am suggesting above and what did or didn't work?

Clean install is just fine, but bare in mind that you might miss a possible firmware update on your 2014 machine between now and late summer, when Big Sur updates stop. But that's relates to all your suggested ways to upgrade.

 

[lkar]

Clean install is just fine, but bear in mind that you might miss a possible firmware update on your 2014 machine between now and late summer, when Big Sur updates stop. But that's relates to all your suggested ways to upgrade.

So are you saying, when I said: "can I install ventura (via OCLP) directly onto the third party SSD? (best and fastest way)" will work? That means (I am assuming), any firmware updates that ventura has, monetery also has?

But that doesn't make sense since you said: "you might miss a possible firmware update on your 2014 machine between now and late summer, when Big Sur updates stop"

So can you clarify? Thanks.

 

[mwidjaya]

So can you clarify?

Seems like you are chasing your own tail re. firmware updates.

1. The 2014 MBP latest supported macOS is Big Sur. Running that and applying software updates will get you firmware updates (if any).

2. Running OCLP (Monterey or Ventura) will NOT get you firmware updates for your 2014 MBP. OCLP is spoof-less, so software updates can "see" your underlying HW model does not qualify for the firmware updates.

3. If you have a volume running Big Sur on your SSD, you can reset NVRAM (bypass OCLP), boot into Big Sur and run software updates to get any firmware updates.

4. The above applies whether you run on Apple SSD or third party SSD (this is separate issue/complication to work around).