Same problems with latest security update

[TomH TX]

Seems like a repeat of the same problem with the security update of a couple of months ago, about which there were some threads. I installed the update yesterday, computer restarted, and then tonight I get the same update available. Really???? WTH is going on with Apple's software updates?

 

[Mejoco_LC475]

I was hoping this latest update 2019-001 for High Sierra was going to sort the recent issues many users have reported across multiple threads/sites. I had to restore to a Time Machine back-up following 2018-002, I purposely avoided 2018-003.

Currently running 10.13.6 (17G65) without issue, think I'll hold off on 2019-001 too.

 

[TomH TX]

I relented and ran 2019-001 AGAIN last night (2nd time). Again, it rebooted, and showed the update under installed updates. NO groundhog day repeat or available update message yet today, so MAYBE this time it installed correctly.

 

[AlanC3]

The problems are slightly more drastic here...

The update apparently runs OK from the AppStore, but when the machine reboots it gets stuck in a loop of trying to install the update, crashing out and showing the grey desktop with the options to restart the update or shut down. Restarting just causes it to crash again:

Jan 24 16:53:51 MacBook-Pro OSInstaller[554]: Install will be automated.
Jan 24 16:53:51 MacBook-Pro OSInstaller[554]: Install will be a InstallInfo.plist install.
Jan 24 16:53:51 MacBook-Pro OSInstaller[554]: Installer Info install requested but we're not dmg booted
Jan 24 16:53:51 MacBook-Pro OSInstaller[554]: The main OS Installer distribution (/Volumes/High Sierra/Library/Updates/AtomicUpdates/041-31490/041-31490.English.dist) did not load with error: The file doesn’t exist.
Jan 24 16:53:51 MacBook-Pro storagekitd[555]: Removing client connection <SKDaemonConnection: 0x7fd4eff015d0>
Jan 24 16:53:51 MacBook-Pro Language Chooser[536]: Child process exited 11
Jan 24 16:53:51 MacBook-Pro storagekitd[555]: No more connections, storagekitd will exit...
Jan 24 16:53:51 MacBook-Pro Unknown[559]: Launching the Installer Crash Log Viewer

Round and round we go, until I boot into recovery mode and reinstall the OS. Just like the last security update.

 

[flowrider]

so MAYBE this time it installed correctly.

You can check by going to the Apple and clicking on "About This Mac". Click on Version 10.13.6 and notice the build no. If the update installed it will be (17G5019). Like this:

Lou

 

[simonsi]

Took two attempts to install on my 2011 MBP, no warnings, crashes or anything on the first try, it just seemed to complete normally but hadn't installed, MAS immediately identified the update as still required, second attempt installed correctly.

Now downloading for the second time on my 2011 iMac - same results with first install attempt.

Update - second attempt worked as expected so it seems consistent at least...

 

[TomH TX]

Thanks Lou. Correct build number confirmed.

 

[mj_]

Took two attempts to install on my 2011 MBP, no warnings, crashes or anything on the first try, it just seemed to complete normally but hadn't installed, MAS immediately identified the update as still required, second attempt installed correctly.

Same behavior on my 2017 MacBook but not on my 2017 iMac. The latter installed immediately, the former required two attempts.