Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Clicking for info or the Mojave SU 005 download link gives you web errors.

No explanations either, it's like literally the littlest amount of effort; they didn't even bother updating the web page itself.

"The Page You're Looking For Doesn't Exist"

The 005 update for High Sierra and 10.15.7, all flavors, continue to work as normal.

Hopefully they will put in a fixed installer, although I bet they won't even say what got fixed.
 
I agree with those who are concluding that it is Safari 14 that is the main problem. On my 2017 MacBook Air I installed Safari 14 nearly two weeks ago, but hadn't gotten around to the security update 2020-005. When I run 'softwareupdate -l' I see the message about conflicting frameworks and undefined behavior; I also see that RAM usage instantly goes up to claim nearly all RAM immediately after boot; so far I haven't had any overtly weird behavior other than a bit of sluggishness. So it looks like I'll be re-installing Mojave over my current boot disk, and then avoiding Safari 14.
 
I just checked and both Safari 14 and Security Update 2020-005 are no longer listed as updates. I guess Apple got the message finally.

Indeed!!! Thanks for this infos. I'll quickly download Safari 13.1.2 .pkg (which is back on the Mac App Store update tab if you have any previous version too).
 
Last edited:
Clicking for info or the Mojave SU 005 download link gives you web errors.

No explanations either, it's like literally the littlest amount of effort; they didn't even bother updating the web page itself.

"The Page You're Looking For Doesn't Exist"

The 005 update for High Sierra and 10.15.7, all flavors, continue to work as normal.

Hopefully they will put in a fixed installer, although I bet they won't even say what got fixed.
I don’t have any issues (as far as I can see) with Safari 14.0. (without SU 005).
 
I don’t have any issues (as far as I can see) with Safari 14.0. (without SU 005).

Sadly, there is a high probability that problems will come if, knowing that Safari 14 is installed on your system (Mojave I guess), you upgrade with the Security Update (any of them, so 005 as well).
 
Originally Safari 14 was available same time as SU 004.
Security features enhanced on it.... :)
 
I agree with those who are concluding that it is Safari 14 that is the main problem. On my 2017 MacBook Air I installed Safari 14 nearly two weeks ago, but hadn't gotten around to the security update 2020-005. When I run 'softwareupdate -l' I see the message about conflicting frameworks and undefined behavior; I also see that RAM usage instantly goes up to claim nearly all RAM immediately after boot; so far I haven't had any overtly weird behavior other than a bit of sluggishness. So it looks like I'll be re-installing Mojave over my current boot disk, and then avoiding Safari 14.

Definitely Safari 14 I think is the main culprit as I did not install Security Update 2020-005 but have the exact same issues and even worse now with my late 2015 Imac not even recognizing my Time Machine Backup 5TB drive(cannot be mounted even in terminal) , along with other weird stuff that's all gradually been happening since installing Safari 14. The huge active memory allocation was the first sign of issues to me . I don't use safari at all so never really tied the problems to going to Safari 14.

I restored to a time machine backup (the backup was still after the safari 14 install) and now after my first reboot since applying the restore is when I lost access to my Time Machine backup drive.

My restored system is completely unstable and I'm now in salvage mode trying to see if I can find a way to rescue the other backups off the TM Backup drive and restore one prior to Safari 14 install.

My Imac main disk being APSs now thanks to going Mojave a month ago(from High Sierra) , this external disk is still HFS+ . I'm wondering if there's any chance i've created a scenario never tested by Apple that's caused my TM backup drive to bollocks up.

Once I am back to stable, no way IN HELL am I updating any Apple provided software application and/or Operating System component. I am a Software consultant (ERP). We would be shot if we allowed something to go live that could do this carnage!!!
 
Maybe this issue doesn’t affect cMP’s....?
With MacOS and maybe Mail and Activity Monitor running....25%(of 32gb) ram usage, tiny bit more if I open Safari 14.
 
I'm running (and writing this) on Safari 14, with which I have had no problems. similarly with the update - no problems. I'm using an iMac 2019 with SIP disabled. My wife, on her Mac Mini, has problems - she has SIP enabled. I still think that's more than chance.

Good news that Apple seemed to have listened, not the least thanks to everyone here who have battled away to get 'em to listen.
 
I'm sure it's more than just us.. there's a lot of enterprise clients, studios, labs, all still running Mojave, for reasons of still having to run 32-bit apps that will likely never be updated to 64-bit.

Stuff like this doesn't bode well for the Apple Sillycon Macs.. if they can't get things right for OSes that have been in release for years, how are they going to guarantee that new OS releases won't be just as buggy?

At least it looks like they're at least aware of the issue.
 
I just checked and both Safari 14 and Security Update 2020-005 are no longer listed as updates. I guess Apple got the message finally.

I've been keeping an eye on this as the update has made my MBP sluggish. I don't want to do a fresh install of Mojave or anything like that (I'd probably run into problems or mess it up) so, for people that did the update straight away, will Apple likely fix this soon? I can still use my MBP (I am now), but it's just frustrating with everything lagging and taking longer to open/close/respond etc. Things like this irritate me!
 
Before every Security Update, (after waiting a few weeks, for people to discover any problems.... 🤪), I ALWAYS update my offline clone first, just incase.
 
Maybe this issue doesn’t affect cMP’s....?
With MacOS and maybe Mail and Activity Monitor running....25%(of 32gb) ram usage, tiny bit more if I open Safari 14.

It definitely affected my Mac Pro 5,1. On that machine I installed Safari 14, and some time later system update 2020-005. I haven't tried hooking up any external disks yet, but RAM was showing 30GB used out of 32GB, never seen it that high before.
 
  • Like
Reactions: bernuli
I always used to wait a while to see if there were any problems but until this update I'd not experienced any issues with any updates to my Mac or iPhones, I guess I'd been lucky. I'll wait a few weeks in future I think!
 
My wife and I would both agree with you on that one. I've long ago realised that it's not a good idea to rush into new OS's - witness my catastrophic upgrade to Catalina - now back on Mojave. We shall now be equally cautious with updates. Mind you, if everyone waited for everyone else to update…!
 
Maybe this issue doesn’t affect cMP’s....?
With MacOS and maybe Mail and Activity Monitor running....25%(of 32gb) ram usage, tiny bit more if I open Safari 14.

It certainly affected my Mac Pro 5,1. I had to reinstall Mojave and then update to 2020-004 and Safari 13.1.2. Everything is now stable again.
 
It definitely affected my Mac Pro 5,1. On that machine I installed Safari 14, and some time later system update 2020-005. I haven't tried hooking up any external disks yet, but RAM was showing 30GB used out of 32GB, never seen it that high before.
That’s bizarre, I am only seeing ~8gb used.
It sounds like the combination of SU5 and S14.
 
  • Like
Reactions: katbel
I was able to manually remove Safari 14, then install Safari 13.1.2. Mojave (18G6032) then went back to normal. Memory usage returned to normal. Users and Groups sys pref pane went back to normal functioning (can add users with no issue). And softwareupdate -l will run without error. There may be other things that Safari 14 broke but those are the 3 items that I picked up on.
 
Last edited:
The only issue I had was slow response after waking up my Mac Mini.
Reinstalled Mojave and updated (to Safari 13.1.2). Since security update 005 and Safari 14 were no longer available, it works great now.

Funny thing is on my MBP 2018 15", I installed Safari 14 first as it was available before security update 005. Then installed security update 005. I have no issues with MBP.
 
They pulled the updates! :eek:

Hopefully we will get a fix soon!

The fix might only really be for users who have not installed the 14 or the security updates.

This would leave anyone that installed the previous update in trouble. I've archived both installers, so I will be able to test this out.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.