After security update 2021-007 for catalina MAMP isn't working, Graphics kernel error: 0xfffffffb

Last macos catalina update fix this and other problems.

I also think it is sad that Apple stops to support old equipment. I switched from much newer Windows laptop to my daughter old MacPro Mid 2012 and honestly I loved it. I added max RAM and it fulfill all my needs.

Anyway, I have just re-installed Catalina (option-command-R) and Security Update 006. I assumed I don't need older Security updates prior 006. Everything gets back to normal. Apps which didn't work like FreeCad and others now works again.

As our colleague previously stated, it took approx 2 hours.

Thanks for having this thread which helps me to make the right decision (at least for myself). Time will tell what might happen with missing Security Update 007.

I have Pacifist, I think I'll give this a try, I can open the 2021-006 pkg file and it has an option to install selected files on their intended locations. Knowing what to search for, I found 1 kext and 3 bundle files related to this video driver so let's see what happens if I ask Pacifist to install just them...

ba91241, your post makes sense. Computers do not work optimally forever. I should know, we are still using here a 2008 iMac, 2010 MacBook Air, 2013 MacBook Air, 2016 iMac, and several 2019 MacBook Pros.

The 2008-2013 Macs I have cannot do many things that newer computers can do. And the 2016 iMac COULD in principle go to Monterey and APFS with its 5400 rpm mechanical drive (currently HFS+), but it would be unusable then. Should I sue Apple for selling us a computer just 5 years ago that now is not usable if I apply the latest upgrade that Apple offers it? What about the 4 GB memory that these 2008 and 2010 Macs have -- many capabilities now require more than 4 GB to work. No I don't plan to sue anyone. All Macs 2013 and earlier are "obsolete," and their hardware is no longer supported by Apple. So those of us still wanting to keep these machines working have to be creative and find third party vendors for parts when needed (as I have done for most of these older models).

But what about this latest Security Update that has reduced functionality of these 2012 Macs? Personally, I think Apple should not have made that update even available to those Macs. But Apple did -- and we don't know if this was unintentional, or if there was in fact a security issue that was serious enough that it had to be closed off, even if functionality was reduced. We don't know. But I do know that over time, all my older Macs have been losing functionality, steadily. Even the 2019 MacBook Pro cannot do some things that the newer M1 Macs can do with Monterey, so it's even started there as well.

The 2012 MacBook Pro is a remarkable model and machine, very versatile, one of Apple's best, and I do hope that either Apple or a third party vendor comes up with a solution soon to restore the limitations that have been imposed by the Security Update.

frombossier city wrote:

... the majority of users don’t back up their computer ... everything i need is backed up in the cloud

I respectfully disagree with that. And I don't blame you for what has happened, this latest Security Update seems to have been quite crippling for 2012 MacBook Pros. I consider that an oversight by Apple that Apple should address. If an update doesn't work on a specific model, then Apple should not offer (or even allow) it. But I think the majority of users do back up their computers, Apple has made it so easy, all you do (for Catalina) is buy an external drive "for Mac" and it is already formatted for Catalina Time Machine, you connect it and it does Time Machine backups quietly in the background.

The majority of people I know using Macs do backups. Many don't even understand Time Machine, but when they replace their current Mac with a new one, they bring their Time Machine drive in and after someone does the migration for them, everything is just there like it was with the old one. I have done this myself for many friends and family members. It takes an hour or so.

One key reason to do these backups is to guard against an update that does not go well for your Mac. Even Apple knows this can happen:

https://support.apple.com/en-us/HT211683 "Make a backup. Before installing any upgrade, it’s a good idea to back up your Mac. Time Machine makes it simple, and other backup methods are also available."

Even though this was an UPDATE not an UPGRADE, I still make sure I have multiple backups before an update, security updates in particular have been taking a long time, with multiple reboots, and sometimes firmware updates as well. So I play it safe.

By the way, you might check the above Apple Support link as it shows how to obtain the Catalina installer. If that installer does not include the problematic Security Update, you can wipe the disk, install Catalina, and then not apply the problematic Security Update. Then restore your files (you do say they are backed up in the cloud). Or make a Time Machine backup first, then erase and reinstall (either from the above link or from Recovery Mode), then migrate files only over. I did this once on an earlier MacOS and back then (with High Sierra) after the clean install I was prompted to apply a slew of updates. So avoiding this problematic Security Update might be possible. It might be possible to test this on an external drive. Or if this doesn't work, maybe try first with Mojave and perhaps the upgrade to Catalina won't include the problematic update.

I agree that these acrobatics should not be necessary but just trying to explore some things that might enable folks to start using their Macs the way they want again.

After installing the update, I can no longer run Google Earth, Stellarium, Topaz Video Enhance AI, as well as Street View Google Maps via browser. I purchased my Mac Mini in 2014. It's not super fast like the newer models but it serves my needs. I just filed a support incident with Apple Support.

The issues I had are fixed with the new security update. :-))

Now WebGL-Pages can be loaded with Firefox again.

Since I had not a single problem with the experimental Safari option "WebGL via Metal", I leave this switched ON.

Regards - Matthias

Brothers, our prayers were heard!

Now I've got update and Google Earth is working as before without any reinstallations.

Check yours!

Best regards!

Denz