update mac os mojave 10.14.6

Hello cora148,

Thank you for using Apple Support Communities.

I understand that you are having issues updating your Mac to macOS Mojave 10.14.6. Without knowing how you are trying to update, I have a couple of support articles for two different ways to update the macOS. Depending on the way you used that failed, try the other way.

How to update the software on your Mac - Apple Support

Download macOS Mojave 10.14.6 Update - Apple Support

If neither works for you, post back with more information about what happens when you try and we can go from there to get the update installed.

Best regards.

If it seems like something is blocking it as you say, restart in Safe Mode and then try to download 10.14.6.

Use safe mode to isolate issues with your Mac - Apple Support

https://support.apple.com/kb/DL2010?viewlocale=en_US&locale=en_US

Well, I think you can apply this...

https://support.apple.com/kb/DL2010?locale=en_US

If you modify the version.plist...

https://x704.net/bbs/viewtopic.php?f=12&t=8726&p=114612#p114612

Maybe 10.14.5 18F132 ???

https://en.wikipedia.org/wiki/MacOS_Mojave

Have a clone or good backup first.

I have the same issue

To attempt a second install

I deleted /Library/Updates/_ManualUpdate/macOS*

Now I get:

sudo softwareupdate --dump-state -i -a -R

Password:

Software Update Tool

Finding available software

Downloading macOS Mojave 10.14.6 Supplemental Update

Downloaded macOS Mojave 10.14.6 Supplemental Update

Preparing macOS Mojave 10.14.6 Supplemental Update

Error downloading macOS Mojave 10.14.6 Supplemental Update: An error occurred installing the update.

Done.

Error downloading updates.

The Log shows:

2019-09-02 22:25:35-04 elma3 softwareupdated[444]: SUBridgeOSUpdateManager: bridgeOS update prepare complete for 061-06469

2019-09-02 22:25:35-04 elma3 softwareupdated[444]: SUBridgeOSUpdateManager: bridgeOS update prepare for 061-06469 failed: Error Domain=BOSErrorDomain Code=204 "An error occurred during preflight." UserInfo={NSLocalizedDescription=An error occurred during preflight., NSUnderlyingError=0x7ffb91b42b60 {Error Domain=BridgeOSSoftwareUpdateError Code=19 "MSU - 2 (Failed to personalize with options.);MSU - 2 (Could not personalize boot/firmware bundle.);MSU - 7 (Failed to load AP ticket from '/private/var/MobileSoftwareUpdate/softwareupdate.259/target/boot/amai/apimg4ticket.der');" UserInfo={NSLocalizedDescription=MSU - 2 (Failed to personalize with options.);MSU - 2 (Could not personalize boot/firmware bundle.);MSU - 7 (Failed to load AP ticket from '/private/var/MobileSoftwareUpdate/softwareupdate.259/target/boot/amai/apimg4ticket.der');, MSUErrorDescription=Failed to personalize with options., MSUErrorCode=2}}}

2019-09-02 22:25:35-04 elma3 softwareupdated[444]: Changing status (foreground bridgeOS prepare failed) for key 061-06469 from "preparing bridgeOS update" to "download error"

2019-09-02 22:25:35-04 elma3 softwareupdated[444]: SUUpdateSession: Personalizing macOS update (foreground = 1)

2019-09-02 22:25:35-04 elma3 softwareupdated[444]: SUUpdateSession: Skipping personalizing macOS update because download for product 061-06469 failed or was cancelled (status: 061-06469 (a=0xf): download error (1619798723 of 1619798723) 50.0% -1.0s (error: Error Domain=SUErrorDomain Code=602 "An error occurred installing the update." UserInfo={NSLocalizedRecoverySuggestion=You can try again to complete the installation., NSLocalizedDescription=An error occurred installing the update., NSUnderlyingError=0x7ffb8b85fd70 {Error Domain=BOSErrorDomain Code=204 "An error occurred during preflight." UserInfo={NSLocalizedDescription=An error occurred during preflight., NSUnderlyingError=0x7ffb91b42b60 {Error Domain=BridgeOSSoftwareUpdateError Code=19 "MSU - 2 (Failed to personalize with options.);MSU - 2 (Could not personalize boot/firmware bundle.);MSU - 7 (Failed to load AP ticket from '/private/var/MobileSoftwareUpdate/softwareupdate.259/target/boot/amai/apimg4ticket.der');" UserInfo={NSLocalizedDescription=MSU - 2 (Failed to personalize with options.);MSU - 2 (Could not personalize boot/firmware bundle.);MSU - 7 (Failed to load AP ticket from '/private/var/MobileSoftwareUpdate/softwareupdate.259/target/boot/amai/apimg4ticket.der');, MSUErrorDescription=Failed to personalize with options., MSUErrorCode=2}}}}}))

2019-09-02 22:25:35-04 elma3 softwareupdated[444]: Stopping transaction with ID [0x2]

2019-09-02 22:25:35-04 elma3 softwareupdated[444]: SoftwareUpdate: Removed foreground transaction [0x2]

2019-09-02 22:25:35-04 elma3 softwareupdated[444]: Stopping transaction with ID [0x1]

2019-09-02 22:25:35-04 elma3 softwareupdated[444]: SoftwareUpdate: Removed foreground transaction [0x1]

2019-09-02 22:25:35-04 elma3 softwareupdated[444]: Running session-idle tasks.

2019-09-02 22:25:35-04 elma3 softwareupdated[444]: Checking for inapplicable local products remaining on disk for cleanup

2019-09-02 22:25:35-04 elma3 softwareupdated[444]: Removing client SUUpdateServiceClient pid=554, uid=0, installAuth=YES rights=(system.install.apple-software, system.install.apple-software.standard-user, system.install.software, com.apple.SoftwareUpdate.modify-settings), transactions=0 (/usr/sbin/softwareupdate)

Any help. My guess is I have to reinstall the full OS. :-(

Tried using a second admin account on the box and using Safe mode in BOTH accounts BEFORE the cleaning of the /Library/Updates/ folder, but received the same error.

My last step is to disable SIP, clean out the /Library/Updates/

With SIP still disabled try to install in Safe mode.

Since I also need to work this will take another day or two to get to.

Followed the directions from this page (still have to disable SIP first):

https://www.jamf.com/jamf-nation/discussions/30061/macos-updates-fail-to-install-potential-workaround-resolution

I still have the same error using my admin only account. I tried running this both with SIP disabled and enabled. Same error

> sudo softwareupdate --clear-catalog

Changed catalog to Apple production

> sudo softwareupdate -i -a -R

Software Update Tool

Finding available software

Downloading macOS Mojave 10.14.6 Supplemental Update

Downloaded macOS Mojave 10.14.6 Supplemental Update

Preparing macOS Mojave 10.14.6 Supplemental Update

Error downloading macOS Mojave 10.14.6 Supplemental Update: An error occurred installing the update.

Done.

Error downloading updates.

So now I'm left with a reinstall of the OS or wait for 10.14.7 in the hopes that that Combo updater will work.

Alas still no joy.

sudo softwareupdate -i -R -a

Password:

Software Update Tool

Finding available software

Downloaded macOS Mojave 10.14.6 Supplemental Update 2

Installing macOS Mojave 10.14.6 Supplemental Update 2

Done.

Error installing updates.

My next step is a backup and reinstall.

I reinstalled using the recovery menu. It worked fine and I didn't need to restore anything. Then I tried to run the security update and it failed again

2019-11-14 09:34:47-05 elma softwareupdated[1169]: SoftwareUpdate: error on install of 061-27901: Error Domain=SUErrorDomain Code=700 "Unable to verify software update." UserInfo={NSLocalizedRecoverySuggestion=You can try again to complete the installation., NSLocalizedDescription=Unable to verify software update., NSUnderlyingError=0x7fded5edc1d0 {Error Domain=OSPErrorDomain Code=302 "The signed AP ticket could not be found." UserInfo={NSLocalizedDescription=The signed AP ticket could not be found.}}}. Reporting statistics.

2019-11-14 09:34:47-05 elma softwareupdated[1169]: SUStatistics: Respecting user Data and Usage policy - Not reporting for category: SU Installs before reboot (success = 1)

#sad

The "trick" of changing the SystemVersion.plist worked with the installer, but a very similar error happened.

It looks like my system lost some cert or token that verifies Apple Updates.

As I said a reinstall of the OS to 10.14.6 via Recovery mode did NOT help this. I'm going to open up a formal ticket, but unless a security chip is bad, would guess I need to wipe the box and start again. I do have a complete backup at least.

Details below...

2019-11-14 20:16:07-05 elma softwareupdated[513]: SoftwareUpdate: Could not personalize manual product at /var/folders/zz/zyxvpxvq6csfxvn_n00000s0000068/C/softwareupdated/com.apple.SoftwareUpdate/localhost/AdoptedManual/macOSUpdCombo10.14.6.pkg

2019-11-14 20:16:07-05 elma softwareupdated[513]: Manual product is nil, therefore an error occured, stashing token will NOT be created...

2019-11-14 20:16:07-05 elma Installer[604]: ManualAdoption: Error adopting /Volumes/macOS 10.14.6 Update/macOSUpdCombo10.14.6.pkg: Error Domain=SUErrorDomain Code=700 "Unable to verify software update." UserInfo={NSUnderlyingError=0x600003cc06f0 {Error Domain=OSPErrorDomain Code=302 "The signed AP ticket could not be found." UserInfo={NSLocalizedDescription=The signed AP ticket could not be found.}}, NSLocalizedRecoverySuggestion=You can try again to complete the installation., NSLocalizedDescription=Unable to verify software update.}

2019-11-14 20:16:07-05 elma Installer[604]: ManualAdoption: stashToken is Nil, softwareupdated did not authorize a token, stashing has failed!

2019-11-14 20:16:07-05 elma Installer[604]: Failed to adopt update: Unable to verify software update.

Solved! at least for me.

The Key was

"The signed AP ticket could not be found" - # with "quotes"

https://forums.macrumors.com/threads/unable-to-do-incremental-macos-update.2183540/

My new MBP had a time-machine restore and it brought my old:

/etc/hosts

file which had this line at the end to fix some apple update issue from 2014

74.208.10.249 gs.apple.com

This broke the T2 chip contacting the apple server to verify ANY update. This error applies to any Mac with the T2 chip which needs an internet connection to update.

Finally! Thank you all for your help. The answer was out there, but I couldn't ask Uncle Google well enough.

I should add I separately download the Update pkg and the Combo Update pkg as stand alone dmg files and had the same issue.

Also try downloading in another admin user account.

Forgot to add, also tried the update in Safe Mode. Same Error.

I will give that a try, and report back, but it is the security update that is failing. (18G1012)

The 2019-001 update, then I'd set it to 10.14.6 build 18G103, the one just before that update.