Today, Apple released the following updates
macOS Catalina 10.15.5 Update
Security Update for Mojave 2020-003
Security Update for High Sierra 2020-003
Patch & Security information, Download Links, Version info + size for BridgeOS, Combo, Delta, Full Installer app included in the links below!
And in the news you're going to love category, after installing Catalina 10.15.5, or the 2020-003 Security Update for Mojave or High Sierra, the
softwareupdate tool will no longer recognize the
--ignore flag to hide "major new releases of macOS". We knew it was coming for 10.15.5, but adding it to the Security Update for High Sierra and Mojave is a rude middle-finger to Mac Admins from Apple.
@atomczynski > Does adding Install macOS Catalina.app to disallowed list still work?
Yes, blacklisting app works, but action happens after user download full installations image, opens app. And it doesn't not prevent System Update messages "Update is available, install it". Expect more support calls...
I am getting error in few macs like this:
To install these updates, your computer must shut down. Your computer will automatically start up to finish installation. Installation will not complete successfully if you choose to restart your computer instead of shutting down. Please call halt(8) or select Shut Down from the Apple menu. To automate the shutdown process with softwareupdate(8), use --restart.
Any idea about this?
@Rohitds14 I have tried to use the Execute Command option in a policy, but am getting errors on a few. Any success?
Executing Policy Run Apple Updates
Running command softwareupdate -i -a --restart...
Result of command:
Software Update Tool
Finding available software
Downloading macOS Catalina 10.15.5 Supplemental Update
Downloaded macOS Catalina 10.15.5 Supplemental Update
Preparing macOS Catalina 10.15.5 Supplemental Update
Installing macOS Catalina 10.15.5 Supplemental Update
Error installing updates.
Has anyone noticed a change in behaviour relating to recovery keys? I'm starting to see users who's recovery keys were generated "today" all over. It seems to replace the existing entry with the same key, like the same key's just been re-sent.
With the test I did, the key was "re-sent" on boot. No inventory scan or anything, just on boot from a deep(?) sleep. I imagine it would be the same whether the MBP had been off.