This problem is reportedly fixed in 10.14 Mojave, but admins who still have 10.12 Sierra or 10.13 High Sierra deployed could benefit from a workaround since it seems Apple won’t be providing a solution. Softwareupdated: Removing local product after found to be incomplete Softwareupdated: SoftwareUpdate: Invalid or incomplete local product 041-31490
#Macbook pro software update failed install
Simply changing the date of macOS on the computer (or virtual machine) by a month between downloading and trying to install an Apple security update will frequently cause failures in my testing with both Sierra and High Sierra.Īpple’s logging is less than helpful when this occurs, simply reporting: No one in the MacAdmins Slack has come up with a conclusive reason for why these updates fail, but they have generally been referred to as “stale.” The behavior can often, but not always, be reproduced by manipulating the Date & Time in macOS. I’ve written a script that works around this behavior, read on if you are interested in the details. This is not a great user experience and has led to some frustration here at the newspaper. However an hour or so later softwareupdate will again detect the update, download it and MSC will prompt the user to logout and install the same update they think they had just installed.
The computer will reboot and the user will find themselves at the login window thinking the update completed successfully. If enough time has passed when the user finally decides to allow the logout / reboot for the update it will silently fail. Munki will invoke softwareupdate to download updates as soon as they are detected but users can defer the installation via MSC indefinitely by default. This is especially apparent to Munki admins who have Managed Software Center (MSC) configured to install Apple updates. For at least a year MacAdmins have been dealing with Apple security updates failing if they are not installed soon after being downloaded.
0 kommentar(er)
