Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The update installed without issue on my work 2012 Mac Pro and 2013 MacBook Pro. I will be installing it on my personal systems when I get home.

EDIT: the update installed without issue on my 2018 as well as 2014 mini. It felt like it took longer than a security update normally does, but lucky I had other devices to update to keep me busy.
 
Last edited:
Thanks both for the info. I've downloaded the update from Apple Downloads page as I like to keep a copy and always disconnect from the internet before applying any update. I will take the plunge later after I've cloned my HD.
 
Did anyone of you tried to see in terminal if you can still stop Catalina or other updates from nagging continuously ?
The Security Update 2020-03 broke that possibility but with a trick you could go back.
Has Apple fixed that? The command was

sudo softwareupdate --ignore "macOS Catalina"

then if you need to go back

sudo softwareupdate --reset-ignored

Thanks if you can tell me if it works
 
Did anyone of you tried to see in terminal if you can still stop Catalina or other updates from nagging continuously ?
The Security Update 2020-03 broke that possibility but with a trick you could go back.
Has Apple fixed that? The command was

sudo softwareupdate --ignore "macOS Catalina"

then if you need to go back

sudo softwareupdate --reset-ignored

Thanks if you can tell me if it works

Still getting the following when the above command is ran:

Ignoring software updates is deprecated.

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


And does not hide the update, although, I did not restart (for some reason I thought that was a requirement).
 
Still getting the following when the above command is ran:

Ignoring software updates is deprecated.

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


And does not hide the update, although, I did not restart (for some reason I thought that was a requirement).
Thanks so much for trying it! We are loosing our freedom ..for now I'm not 😉
 
Did anyone of you tried to see in terminal if you can still stop Catalina or other updates from nagging continuously ?
The Security Update 2020-03 broke that possibility but with a trick you could go back.
Has Apple fixed that? The command was

sudo softwareupdate --ignore "macOS Catalina"
Still works for me, but I do not use sudo, and I do not get the deprecated future ignored message either. The only thing bothersome is that Apple has been releasing the "Security Update 2020-xxx-(10.14.6)" in various syntaxes. Sometimes with a dash between the 00x and the version, sometimes not, sometimes with the version inside parentheses, sometimes not, several variations. You have to ignore each one. When you do softwareupdate -l, ignore the line with the asterisk.
 
Has anyone seen extended UI freeze (no mouse movement, keyboard inputs ignored) since updating to this release? It would be stuck like that for 1-2 minutes but eventually unfreezes and the pending keypresses will be processed.

I have encountered this on two machines (MBA 2015, Mini 2014) with 256 GB SSD, where each of the SSDs are about 92% full. They each have 8GB RAM.
 
Has anyone seen extended UI freeze (no mouse movement, keyboard inputs ignored) since updating to this release? It would be stuck like that for 1-2 minutes but eventually unfreezes and the pending keypresses will be processed.

I have encountered this on two machines (MBA 2015, Mini 2014) with 256 GB SSD, where each of the SSDs are about 92% full. They each have 8GB RAM.
I am having same issue.
 
  • Like
Reactions: Zwhaler
about 92% full.

This may be the source of your problem. It is generally recommended to use only about 75% of your SSD's capacity. It has to do with how it writes to the drive. If there is enough free space, it writes all the data in a single block, very quickly. If space is limited, it has to write a portion to one block, do some calculating and write to another block, etc.
 
This may be the source of your problem. It is generally recommended to use only about 75% of your SSD's capacity. It has to do with how it writes to the drive. If there is enough free space, it writes all the data in a single block, very quickly. If space is limited, it has to write a portion to one block, do some calculating and write to another block, etc.
My MacBook Pro retina (early 2015) 13” has 128 GB SSD drive & free space around 35 GB.
 
This update messed up my Mac Pro a bit. It freezes after booting to the desktop (clock is stuck but mouse pointer can move but not click or selct anything) then it refreshes a minute or so later and then freezes again. This repeats for a couple minutes then it's fine. The computer had no issues before installing this update (there was one other update too at the same time but I don't remember what it is).
 
I suggest you visit support.apple.com/downloads and grab the standalone Mojave Security Update 2020-004 installer and try that. I believe these are cumulative updaters like a Combo Updater. I always use the standalone installer for these updates.

If that doesn't work, it's probably time to download a full copy of Mojave, put it on a bootable USB thumb drive and reinstall Mojave from that over your existing installation.

The second update was Safari 13.1.2 for Mojave. Since I use the standalone security update installer, I still had to download Safari separately from Software Update (Apple no longer delivers Safari as standalone installers).
 
After balking initially, my Mini seems to have recovered from the security update disease, whatever it was. I bailed out of the restart generated by the download after more than 10 minutes. Finally, another attempt to restart succeeded in about that same amount of time. Now, it restarts like before the update, as if nothing happened.
 
The second update was Safari 13.1.2 for Mojave. Since I use the standalone security update installer, I still had to download Safari separately from Software Update (Apple no longer delivers Safari as standalone installers).

You can obtain the Safari update in .pkg format by using Terminal and the softwareupdate utility. softwareupdate -d "pkg name" downloads it only, and you will find it in /Library/Updates. Then use the .pkg file for multiple Mojave machines. You will need to run softwareupdate -l first to get the exact name of the file to use as the target to download. Best to use quotes around the target name.
 
  • Love
Reactions: camelia
I suggest you visit support.apple.com/downloads and grab the standalone Mojave Security Update 2020-004 installer and try that. I believe these are cumulative updaters like a Combo Updater. I always use the standalone installer for these updates.

If that doesn't work, it's probably time to download a full copy of Mojave, put it on a bootable USB thumb drive and reinstall Mojave from that over your existing installation.

The second update was Safari 13.1.2 for Mojave. Since I use the standalone security update installer, I still had to download Safari separately from Software Update (Apple no longer delivers Safari as standalone installers).
I also used the standalone Mojave Security Update 2020-004 installer, but then used SilentKnight by The Eclectic Light Company to check for updates (Xprotect etc.) and to my surprise it updated Safari. That is great 'cause it doesn't trigger the return of the "Red Badge" on the System Preferences icon pestering the user to update to La Catalina!
 
I also used the standalone Mojave Security Update 2020-004 installer, but then used SilentKnight by The Eclectic Light Company to check for updates (Xprotect etc.) and to my surprise it updated Safari. That is great 'cause it doesn't trigger the return of the "Red Badge" on the System Preferences icon pestering the user to update to La Catalina!
I checked on a friend's computer where he updated to the latest Mojave Security Update 2020-004 with the standalone installer downloaded from Apple , and the older SoftwareUpdate n.6 is still in the system after updating to the latest (I did the changes on his computer as someone #28 suggested), but I do not know if he will be nagged to install Catalina and now Catalina upgrade is visible if you open Software update, before it wasn't .

Solved:
Since I updated following this #18,689 tip everything works again without Catalina upgrade! Thanks to alphascorp
 
Last edited:
Still freezing after booting to desktop and then refreshes after a minute or so (then does it again). Anyone else?
 
  • Like
Reactions: Brian33
Hi, i've this issue. Freeze after logging for 30/50 seconds. Refresh and freeze again for 20/30 seconds. After that all is ok until the next restart. I'm an UAD user and i found that removing UA Mixer Engine and UAD Meter Launcher from session starting fix my issues
 
Has anyone seen extended UI freeze (no mouse movement, keyboard inputs ignored) since updating to this release? It would be stuck like that for 1-2 minutes but eventually unfreezes and the pending keypresses will be processed.

Still freezing after booting to desktop and then refreshes after a minute or so (then does it again). Anyone else?

Yes I've seen it again since updating to 2020-004. It was gone in 003, but now it's back for me...
 
Do you have a fusion drive?
No, boot drive is SATA SSD and bays 2-4 are HDD
[automerge]1595454004[/automerge]
Hi, i've this issue. Freeze after logging for 30/50 seconds. Refresh and freeze again for 20/30 seconds. After that all is ok until the next restart. I'm an UAD user and i found that removing UA Mixer Engine and UAD Meter Launcher from session starting fix my issues
Interesting thanks for sharing I can give this a try.
 
I definitely think it's something related to the UAD stuff. I removed UA Mixer and Meter from login items and restated. It worked fine! My Apollo was on when I restarted. But then I switched the Apollo off, and the freezing happened right after. So it seems to be related to the Universal Audio software.
 
I am also experiencing these freezes on my 2010 Mac Pro since the security update. I get several freezes each day, each lasting a minute or two. I have noticed a bunch of logs like this in system.log:

Code:
Jul 24 16:38:04 Sun com.apple.xpc.launchd[1] (com.apple.tccd.system[2066]): Service exited due to SIGABRT
Jul 24 16:38:04 Sun com.apple.xpc.launchd[1] (com.apple.tccd.system[37551]): Service exited due to SIGABRT
Jul 24 16:38:04 Sun com.apple.xpc.launchd[1] (com.apple.tccd.system[37552]): Service exited due to SIGABRT
Jul 24 16:38:04 Sun com.apple.xpc.launchd[1] (com.apple.tccd.system): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Jul 24 16:38:14 Sun com.apple.xpc.launchd[1] (com.apple.tccd.system[37556]): Service exited due to SIGABRT
Jul 24 16:38:14 Sun com.apple.xpc.launchd[1] (com.apple.tccd.system): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Jul 24 16:38:24 Sun com.apple.xpc.launchd[1] (com.apple.tccd.system[37558]): Service exited due to SIGABRT
which seem to coincide with the timing of the freeze.

I have over 160 crash logs for the tccd process and they start on July 15th which was the day the update was released. Anyone else noticing something similar?

Code:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSFileManager fileSystemRepresentationWithPath:]: nil or empty path argument'
terminating with uncaught exception of type NSException
 
  • Like
Reactions: Brian33
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.