macOS Catalina install error

dmw3
Contributor III

Just running upgrades on test computers for macOS Catalina and have had multiple errors as in the Screenshot.5c154a86bb7d4a3c9430d63b7cac446d
Click "OK" the install fails and goes away, resulting in the installer needs downloading again.

20 REPLIES 20

vanschip-gerard
Contributor

Yup, same here on 2 machines. Tried 3 times now.

whitebeer
Contributor

Confirmed, same problem for me - tried it 3 times now.
Do you have any restriction concerning software update deferral in place?

whitebeer
Contributor

Downloaded the RecoveryHDMetaDMG.pkg manually from the SUC, opened that with Suspicious Package and it seems that the following script fails for some reason:

fd2b627d34144fbcbd840cddec92a09d

And least now I know why the Installer is always missing after the Install fails 🀨

run_on_failure() {
    echo "Script failed. Printing diagnostic information"
    /usr/bin/shasum -a 256 "${PACKAGE_PATH}"
    /bin/ls -la@O "${PACKAGE_PATH}"
    echo "Script failed. Unlinking ${TARGET_INSTALLER_PATH}"
    /bin/rm -rf "${TARGET_INSTALLER_PATH}"
}

mschroder
Valued Contributor

How I love the installers that in case of a failure remove all traces, so that you have no chance to find out what might have gone wrong :(

jamf_rixi
New Contributor II

We have noticed that bash-scripts seem to fail after the update to catalina. Could the reason be that zsh is now the default/standard interactive shell?

mschroder
Valued Contributor

There should be no reason for bash-scripts to fail if you use a proper '#!/bin/bash'. If on the other hand you simply assume that your script will use bash without using the shebang than your scripts will now run in zsh, and all elements that are bash specific will make the script fail.

gabester
Contributor III

On a related note, short of dissecting Apple's installers ourselves, is there anywhere to go to find exactly what and how an OS install or upgrade should be working? There are so many different packages that need to run and on so many different levels...

Boo indeed on developers who delete their logs and installers after they fail... Borders on malware. :-)

whitebeer
Contributor

I got the update working for me - forgot my machine is one of the tests with Microsoft Defender ATP. When I disabled it the update worked fine, so check again with disabled AV ...

dmw3
Contributor III

We can confirm that disabling Microsoft Defender ATP allows the update to occur. Tested this with a local admin account, now looking for a non-admin user for testing as all our non-admin are AD accounts.

Will report back the results.

seann
Contributor

Does /var/log/install.log reveal anything?

whitebeer
Contributor

good to hear, @dmw3 !
But I can't understand why - Defender doesn't seem to block anything, nor alerted.
Seems like we have to bring some exclusions in place for future updates πŸ™ˆ
MAU just came up with an application update for Defender ATP, maybe that could help.

tylerwince
New Contributor

Anyone else having this problem without Microsoft Defender ATP installed? I am seeing this same error but am not running the mentioned apps.

JarvisUno
Contributor III

Same here as of today trying to upgrade my test machine to Catalina brand new install don't have MSO Defender installed but do have TrendMicro that has never stopped an update in the past and shows 0 blocks in the Console.

MrDohertyScienc
New Contributor

I am also having the same problem without Microsoft Defender installed, nor the previously mentioned apps.

troyewebster
New Contributor III

I'm seeing exactly the same thing. We do have TrendMicro running ... I got an unistaller pkg from Trend and ran that ... was finally able to complete the upgrade to Catalina without the script error.

JarvisUno
Contributor III

@troyewebster We have WFBS TrendMicro and are now exhibiting this error as well even though trend has never stopped an Apple installation ever, have you tried upgrading a different way or was that your solution to turn "OFF" the AV?
ae7a1523776d46778c5789602f3b582e

bayareaautomato
New Contributor II

No fixes for users without AV?

PCDoc
New Contributor

Same error message with no AV.

JarvisUno
Contributor III

Anyone ever find a solution to this still having some machines pop up with this random error now from Mojave to Catalina.

ysaludes
New Contributor

Hi There, We've encountered the same issue for a while and FINALLY found out what was blocking us.
We had a MacOS device policy that was preventing the opening of DMG files.
Profiles > Restrictions > Media > Disk Images
The checkbox was left unchecked, therefore we could not open (actually) any other DMG file from the user's end.

I hope this will help other users.