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.
Security Update 2020-003 10.14.6 : any problems?
- Thread starter strawbale
- Start date
- Sort by reaction score
Totally hear you. But I have numerous software horizons that dictate I need to get on to the present OS. I have a Mojave clone standing by. And what happens when 10.16 comes along? I will then have to wait at least until .4 release which is sometime in 2021. At some point I have to work around the mess that is macOS. At least I don't have a T2 chip!! 🤞 🤞
Apple must have found something they didn't like about "Security Update 2020-003" -- because there's now a "Security Update 2020-004 Beta" up for download...
Came here hoping for answers . Ive got a Mac Pro 5.1 that is on OSX 10.14.6
I've tried to do the 'Security Update 2020-003' patch that it keeps nagging me about.
When I click 'update', the machine appears to start installing, then just reboots (after a lot of trying) & tells me that the installation failed due to 'insufficient resources' or something along those lines.
I've tried it a few times & still no dice.
Anybody more Tech savvy than me have any idea what to do? I was hoping this would be the final update for the old thing..
It's a stock 5.1 machine with an SSD, a clean Mojave Install, Radeon RX580 & 32GB Ram
[automerge]1591123414[/automerge]
I've tried to do the 'Security Update 2020-003' patch that it keeps nagging me about.
When I click 'update', the machine appears to start installing, then just reboots (after a lot of trying) & tells me that the installation failed due to 'insufficient resources' or something along those lines.
I've tried it a few times & still no dice.
Anybody more Tech savvy than me have any idea what to do? I was hoping this would be the final update for the old thing..
It's a stock 5.1 machine with an SSD, a clean Mojave Install, Radeon RX580 & 32GB Ram
[automerge]1591123414[/automerge]
Last edited:
In case anyone else has the same problem, this solution worked. Disconnect the other three drives in the bays 2, 3 & 4.
'macOS could not be installed on your computer' error when installing Mojave on Hackintosh - BarTechTV
This page contains affiliate links. As an Amazon Associate I earn from qualifying purchases. Introduction Now that the final version of macOS 10.14 Mojave, has [...]
bartechtv.com
It's not a matter of "not liking." This will fix a different set of security issues than 2020-003 which corresponds to what gets fixed in 10.15.6.
Running 10.14.6, I installed the Security Update this morning. After a successful install, both of the Thunderbolt 2 ports on my MacBook Pro 2015 were unresponsive. After coming across news of a security concern with Thunderbolt ports https://www.macworld.com/article/3542683/thunderbolt-security-flaw-in-macs-and-pcs.html I’m suspicious that this update is the cause. Anyone else experiencing this?
So, I finally reinstalled 10.14.6 which seems to have included update 2020-002 but NOT 2020-003 and sure enough Safari is once again working. I have disabled auto updates for now, expecting that 2020-003 might have been my problem, maybe in a month or two I will retry it.
Did anyone have issues with their AMD cards and 003 update? After installing this update I would get kernel panic every few boots with AMD kext.
First install had kexts in backtrace: com.apple.iokit.IOAcceleratorFamily2 and com.apple.kext.AMDRadeonX4000.
Second install would have the following kexts in backtrace: com.apple.kext.AMDSupport and com.apple.kext.AMD7000Controller
I've verified that 003 is the culprit by re-installing 10.14.6 several time. Without 003 I can boot just fine and enter recovery. If I install 003 update, ever 3rd or so boot KP's but after reboot it boots fine.
Looks like similar AMD driver issues as this blog post explains https://objective-see.com/blog/blog_0x27.html
Would appreciate if someone else with AMD card tests this. I run Mac Pro 5,1 and 7970 AMD card. Try entering recovery mode for a test.
First install had kexts in backtrace: com.apple.iokit.IOAcceleratorFamily2 and com.apple.kext.AMDRadeonX4000.
Second install would have the following kexts in backtrace: com.apple.kext.AMDSupport and com.apple.kext.AMD7000Controller
I've verified that 003 is the culprit by re-installing 10.14.6 several time. Without 003 I can boot just fine and enter recovery. If I install 003 update, ever 3rd or so boot KP's but after reboot it boots fine.
Looks like similar AMD driver issues as this blog post explains https://objective-see.com/blog/blog_0x27.html
Would appreciate if someone else with AMD card tests this. I run Mac Pro 5,1 and 7970 AMD card. Try entering recovery mode for a test.
I don't have the AMD card but since I updated to Mojave I got already 3 KP for different reasons
I never had one since ages ago, maybe on system 8 or 9 .
I guess it has to do with the APFS. After I check the iMac with disk utility it shows no issues
Just the first KernePanic did some damage but I was testing Mojave installed on a Crucial external SSD
What is stunning me is the cause of why it happens. Silly tasks not a corrupted software or system like in the past.
Apple is going downhill
. Someone postedan interesting article how the apple developer work
It is 7/2 now, I have not been offered this update (2020-003) on either of my macbook pros yet (I checked, the latest installed update was 2020-002). Is there any reason why this updated would not be showing up on System Preferences -> Software Update ?
EDIT: both of them are on Mojave 10.14.6
EDIT: both of them are on Mojave 10.14.6
The security update can be found in System preferences , Software Update, at least for Mojave
I have an Early 2015 13" Macbook Pro. it uses Intel Iris Graphics 6100. I had all sorts of problems with update 2020-002 and VMWare version Version 10.1.6. Search for my previous posts.
Everything has been fine since the 003 update. The specific problem I had involved "gpurestart". That's from memory, check my older posts for the exact spelling. That problem went away with 003.
If you see that problem in your logs (once again see my older posts for log location) then it should be fixed in 003. If those crash reports don't appear in your logs, then I have no idea if 003 will help you.