Security Update 2020-004 for Mojave 10.14 & High Sierra 10.13 Released!

19 thoughts on “Security Update 2020-004 for Mojave 10.14 & High Sierra 10.13 Released!”

1. On my Mac Mini 2018, with Mojave 10.14.6 that I own since March 2020, I get this Kernel Crash Report only after using Safari and doing a shutdown and a cold-boot. The newest Security update 2020-004 did not help, as the Security update 2020-003 did not fix this behaviour. I have sent a lot of crash reports to Apple – but they seem not able to fix this. Therefore I stopped using Safari and use Firefox or Chrome in stead. My mainboard was replaced in April after this behaviour appeared the first time, after the Security update 2020-002 – without success.

2. I am running high Sierra. since this update my Mac gets warmer and it drains the battery quicker. I lost at least 2 hours run time. it also drains battery when it is in sleep mode what I never noticed with the previous update. It was still on the same charge percentage overnight when I started the laptop in the morning and now it drops it a lot even after few hours.

   did anyone else notice similar issues?

3. It does not work.
   After update 2020-004, still display as deprected, And also it will back to show the badge after checking update, so it does not work for ignoring Catalina.

   What I did if the badge notif is on, I always doing this in terminal:
   defaults delete com.apple.systempreferences AttentionPrefBundleIDs; killall Dock

4. It works for me after update 2020-004, still display as deprected, but no longer seeing notif badge anymore.

5. After I updated my Mac Mini (Mojave) it always hangs for 30 seconds shortly after I login. Then again everything works fine. Also after a restart or when I boot it always claims that the computer has been shut down due to a problem. Sounds like more bugs and not update.

   1. Yes my Mac Mini (Mojave) have this issue too, already with the first update 003.
      I’m very disappointed, but I’m glad I didn’t buy a new macpro! Now – It’s an apple business, not mine. They are losing customers and better deals. I didn’t find anything on the forums that would help with this issue.
      Next security update? No, thank you very much!

6. Has anyone else noticed that Time Machine backups have significantly slowed down since this security update?

7. I am having problems with this update. After I downloaded the update, and have it installed, my IMAC never restarts, just with the HALT command. I’m using HIGH SIERRA 10.13.6 and what’s saving me is TIME MACHINE. does anyone know how to solve?

   1. On 10.13.6 High Sierra the 2020-004 update caused severe performance loss, spinning beach ball and unresponsive apps and processes on my mid-2010 MacBook Pro i7 and on my 2013 iMac i5.

      Restoring the entire system on the MacBook with TimeMachine to before the 15 July 2020 update got performance back to ‘normal’.

      The iMac also was suffering sector failures in the 1 TB spinner in the Fusion Drive – all the forced restarts I did trying to diagnose the 2020-004 update performance issue made the disk failure much worse. A DriveDX scan finally revealed the disk failure so I’ll be replacing the spinner with a SATA SSD and then upgrading the iMac to Catalina. Currently booting it into Catalina from a USB 3.0 stick and it seems to be working fine.

      2020-004 update to 10.13.6 seems to be broken, at least for my platforms… The old 2010 MacBook is likely to become a Pop!_OS Linux machine in the near future (after a storage upgrade too)!

8. Since I did this update, I have not been able to complete a time machine backup. The console is showing this message over and over again:
   Jul 19 13:52:10 name-MacBook-Air-2 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.02000000-0000-0000-0000-000000000000[10652]): Service exited due to signal: Killed: 9 sent by mds[64]
   Jul 19 13:52:20 name-MacBook-Air-2 com.apple.xpc.launchd[1] (com.apple.powerchime): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

   High Sierra 10.13.6

   Anyone else?

   1. Yes, same problem here. Still investigating. No solution yet.

9. “After installing 2020-004 on 10.14 & 10.13 you can once again block major upgrades (Catalina).
   […]
   NOTE: This change is ONLY for UAMDM (User Approved Mobile Device Management) and Supervised Macs. If your Mac is not Supervised or part of an UAMDM you will not be able to ignore major updates.”

   What does this mean? How can I set my Mac into this “Supervised Macs” state to ignore “macOS Catalina” on Mojave with 2020-004 ?

10. OMG, the 2020-002 bug persists!
    anyone more?

    1. You talk about this GPU restart bug? This sounds not good if this bug is still in there.
       I also had this issue on my MBA with 2020-002 Mojave and thats why I’m still on 2020-001.

       I tried 2020-003 for a too short time to see if there was still this GPU issue. I switched back mainly because I could not use the ignore flag for macOS Catalina any longer.

       And when 2020-004 popped up I ignored it imminently to give it some days to look later at mrmacintosh what this update really changes.

       1. I too. New MacMini Mojave. Is there any way to go back to update 001? I don’t have a backup.

       2. Yes, Waitsnake, the same GPU issue that started after 2020-002 (mojave).

          By the way, I just posted a new comment on the article about the 2020-002 bug here on the Mr Macintosh reporting the updates I got on my case, I’ll be really glad if some of you that experienced (or are still having) the bug go there and reply with your impressions, I’m freaking out with a computer that was working perfectly fine before the update and become a brick after 2020-002 because Apple is now charging me a huge money to “fix” the issue by changing the GPU.

          I’ll be really glad and thankfull if you could help me in any way.

11. Hello,
    I noticed your comment that ignore Catalina was available again after macOS Mojave Security Update 2020-004. I installed the update and ran the command sudo softwareupdate –ignore “macOS Catalina” and it’s not working. It still says that is deprecated?

    Loren

    1. Hello Loren,

       Correct the command is considered “Deprecated” because it will not function anymore on Big Sur. The command will still function fine on 10.13 and 10.14. In Big Sur Updates/Upgrades will only be able to be blocked via MDM for up to 90 days.

       1. I’m running 10.14.6 Mojave. This is what I get when running sudo softwareupdate –ignore “macOS Catalina”
          Ignored updates:
          (
          “macOS Catalina”
          )

          Ignoring software updates is deprecated.
          The ability to ignore individual updates will be removed in a future release of macOS.

Comments are closed.