Apple security update 2018-002 10.13.6 fails on Mac Pro

Just to clarify, my problem was hanging before the restart, not a failure to boot after applying the restart and update. I am not eager to repeat the experiment because it takes so long to restore from Time Machine, but I don't think there was a "MacOS Installer" disk present as a choice for "restore from Time Machine". I didn't keep as good records as markfug, but at one point I did explicitly choose a boot disk when exiting from a recovery mode boot where I did not either reinstall or restore.

Also, I note that the file name does not include the words "high" in it at all. System Requirements are 10.13, not 10.13.6. Probably another overbite, but I've read others having issues installing the update and hoping this isn't another sign of a glitch in the file being posted to SU.

My 13" Mid 2012 MBP had similar issues. Upon restart I got an Unable to Install message that takes me to the Installer Log. Tried a few times to restart, but no luck. Reimaged drive from Time Machine backup overnight. All things are back to normal by morning. Won't be installing this update!

My 2011 mop 17" crashes while booted from a RAM disk.

It launches "Installer Crash Log Viewer" which produces "Installer Log 3-Nov-2018.txt".

It lets me set the boot disk and it boots just fine without the update installed.

No need for any recovery or safe boot.

I got my first crash when rebooting for a "Little Snitch" update to 4.2.2

The crash log is 725 lines long.

Here are 56 lines:

Nov 4 04:50:21 PeterBlackPC OSInstaller[578]: client 0x7ff0a6e224f0: phaseName = "OS Installer"

Nov 4 04:50:21 PeterBlackPC OSInstaller[578]: Mutable product: Looking for automation file at /Volumes/MountainLion/macOS Install Data/minstallconfig.xml

Nov 4 04:50:21 PeterBlackPC OSInstaller[578]: Looking for automation file at /Volumes/MountainLion/macOS Install Data/minstallconfig.xml

Nov 4 04:50:21 PeterBlackPC OSInstaller[578]: Allowing automation file because it has passed point of no return.

Nov 4 04:50:21 PeterBlackPC OSInstaller[578]: Found target disk by UUID: FA4DE0EC-7A45-38E9-B75B-AD4CD3A0B735

Nov 4 04:50:21 PeterBlackPC OSInstaller[578]: Install will be automated.

Nov 4 04:50:21 PeterBlackPC OSInstaller[578]: Install will be a InstallInfo.plist install.

Nov 4 04:50:21 PeterBlackPC OSInstaller[578]: Installer Info install requested but we're not dmg booted

Nov 4 04:50:21 PeterBlackPC OSInstaller[578]: The main OS Installer distribution (/Volumes/MountainLion/Library/Updates/AtomicUpdates/041-18191/041-18191.Englis h.dist) did not load with error: The file doesn’t exist.

Nov 4 04:50:21 PeterBlackPC Language Chooser[555]: Child process exited 11

Nov 4 04:50:21 PeterBlackPC storagekitd[579]: Removing client connection <SKDaemonConnection: 0x7fd4a0602120>

Nov 4 04:50:21 PeterBlackPC storagekitd[579]: No more connections, storagekitd will exit...

Nov 4 04:50:21 PeterBlackPC Unknown[583]: Launching the Installer Crash Log Viewer

Nov 4 04:50:21 PeterBlackPC Viewer[584]: Creating connection

Nov 4 04:50:21 PeterBlackPC Viewer[584]: Connection = 0x7fd466d279e0, callers = (

"<IASUPCaller: 0x7fd466d28540>"

)

Nov 4 04:50:21 PeterBlackPC Viewer[584]: Registering the connection

Nov 4 04:50:21 PeterBlackPC Viewer[584]: client 0x7fd466d207e0: phaseName = Installer Crash Catcher

Nov 4 04:50:21 PeterBlackPC Viewer[584]: client 0x7fd466d207e0: phaseName = "Installer Crash Catcher"

Nov 4 04:50:21 PeterBlackPC Viewer[584]: ISAP: hide progress UI called

Nov 4 04:50:21 PeterBlackPC Viewer[584]: ISAP: hide progress UI called

Nov 4 04:50:21 PeterBlackPC Viewer[584]: client 0x7fd466d207e0: phaseName = Installer Crash Catcher

Nov 4 04:50:21 PeterBlackPC Viewer[584]: Releasing Connection

Nov 4 04:50:21 PeterBlackPC Installer Progress[180]: Hiding Progress UI

Nov 4 04:50:21 PeterBlackPC Installer Progress[180]: Setting window alpha values to 0.0

Nov 4 04:50:22 PeterBlackPC Installer Progress[180]: Ordering windows out

Nov 4 04:50:24 PeterBlackPC opendirectoryd[186]: [session] Processing a network change notification

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Process: macOS Installer [578]

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Path: /System/Installation/CDIS/macOS Installer.app/Contents/MacOS/macOS Installer

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Identifier: com.apple.macOS-Installer

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Version: 1.0 (1006)

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Build Info: OSInstaller-1006000000000000~88

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Code Type: X86-64 (Native)

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Parent Process: ??? [555]

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Responsible: macOS Installer [578]

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: User ID: 0

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]:

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Date/Time: 2018-11-03 21:50:22.487 -0700

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: OS Version: Mac OS X 10.13.6 (17G3025)

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Report Version: 12

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Anonymous UUID: 9E53A887-A383-4B38-BF86-5CB52A566F7A

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]:

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]:

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Time Awake Since Boot: 91 seconds

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]:

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: System Integrity Protection: disabled

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]:

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]:

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Exception Note: EXC_CORPSE_NOTIFY

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]:

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Termination Signal: Segmentation fault: 11

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Termination Reason: Namespace SIGNAL, Code 0xb

Nov 4 04:50:35 PeterBlackPC ReportCrash[582]: Terminating Process: exc handler [0]

MBP 2018. Same issue. I caved in and upgrade to Mojave now that all my apps are compliant.

No more issues, but very worrying handling and lack of response on the part of apple for botching a security update...

Hope they get their stuff together again. Not installing security updates is not an acceptable option in a business context.

I finally got both my iMac Late 2015 and my MacBook Pro 2016 booting properly again. I had done the security update 2018-002 10.13.6 via App Store yesterday (Nov. 3rd). On both machines the update seemed to work fine and first booted with login screen. I would otherwise not have done the other machine...

However, this morning both Macs booted very slowly and ended with a "Installer Crash Log Viewer", indicating the update hadn't completed.

I managed to reinstall High Sierra from Recovery mode. Here is part of the crashreport:

Nov 4 12:20:51 iMac ReportCrash[553]: Process: macOS Installer [548]

Nov 4 12:20:51 iMac ReportCrash[553]: Path: /System/Installation/CDIS/macOS Installer.app/Contents/MacOS/macOS Installer

Nov 4 12:20:51 iMac ReportCrash[553]: Identifier: com.apple.macOS-Installer

Nov 4 12:20:51 iMac ReportCrash[553]: Version: 1.0 (1006)

Nov 4 12:20:51 iMac ReportCrash[553]: Build Info: OSInstaller-1006000000000000~88

Nov 4 12:20:51 iMac ReportCrash[553]: Code Type: X86-64 (Native)

Nov 4 12:20:51 iMac ReportCrash[553]: Parent Process: ??? [529]

Nov 4 12:20:51 iMac ReportCrash[553]: Responsible: macOS Installer [548]

Nov 4 12:20:51 iMac ReportCrash[553]: User ID: 0

Nov 4 12:20:51 iMac ReportCrash[553]:

Nov 4 12:20:51 iMac ReportCrash[553]: Date/Time: 2018-11-04 04:20:40.624 -0800

Nov 4 12:20:51 iMac ReportCrash[553]: OS Version: Mac OS X 10.13.6 (17G3025)

Nov 4 12:20:51 iMac ReportCrash[553]: Report Version: 12

Nov 4 12:20:51 iMac ReportCrash[553]: Anonymous UUID: D48F6FF9-68BF-4982-B2F4-C86878B1C02A

Nov 4 12:20:51 iMac ReportCrash[553]:

Nov 4 12:20:51 iMac ReportCrash[553]:

Nov 4 12:20:51 iMac ReportCrash[553]: Time Awake Since Boot: 150 seconds

Nov 4 12:20:51 iMac ReportCrash[553]:

Nov 4 12:20:51 iMac ReportCrash[553]: System Integrity Protection: disabled

Nov 4 12:20:51 iMac ReportCrash[553]:

Nov 4 12:20:51 iMac ReportCrash[553]: Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Nov 4 12:20:51 iMac ReportCrash[553]:

Nov 4 12:20:51 iMac ReportCrash[553]: Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Nov 4 12:20:51 iMac ReportCrash[553]: Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018

Nov 4 12:20:51 iMac ReportCrash[553]: Exception Note: EXC_CORPSE_NOTIFY

Nov 4 12:20:51 iMac ReportCrash[553]:

Nov 4 12:20:51 iMac ReportCrash[553]: Termination Signal: Segmentation fault: 11

Nov 4 12:20:51 iMac ReportCrash[553]: Termination Reason: Namespace SIGNAL, Code 0xb

Nov 4 12:20:51 iMac ReportCrash[553]: Terminating Process: exc handler [0]

Nov 4 12:20:51 iMac ReportCrash[553]:

Nov 4 12:20:51 iMac ReportCrash[553]: VM Regions Near 0x18:

Nov 4 12:20:51 iMac ReportCrash[553]: -->

Nov 4 12:20:51 iMac ReportCrash[553]: __TEXT 00000001017fa000-0000000101811000 [ 92K] r-x/rwx SM=COW /System/Installation/CDIS/macOS Installer.app/Contents/MacOS/macOS Installer

Nov 4 12:20:51 iMac ReportCrash[553]:

Nov 4 12:20:51 iMac ReportCrash[553]: Application Specific Information:

Nov 4 12:20:51 iMac ReportCrash[553]: objc_msgSend() selector name: release

Nov 4 12:20:51 iMac ReportCrash[553]:

Nov 4 12:20:51 iMac ReportCrash[553]:

Nov 4 12:20:51 iMac ReportCrash[553]: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

Nov 4 12:20:51 iMac ReportCrash[553]: 0 libobjc.A.dylib 0x000000010291ae9d objc_msgSend + 29

Nov 4 12:20:51 iMac ReportCrash[553]: 1 com.apple.macOS-Installer 0x00000001017fc840 0x1017fa000 + 10304

Nov 4 12:20:51 iMac ReportCrash[553]: 2 libdispatch.dylib 0x00000001075525fa _dispatch_call_block_and_release + 12

Nov 4 12:20:51 iMac ReportCrash[553]: 3 libdispatch.dylib 0x000000010754adb8 _dispatch_client_callout + 8

Nov 4 12:20:51 iMac ReportCrash[553]: 4 libdispatch.dylib 0x0000000107556395 _dispatch_main_queue_callback_4CF + 1148

Nov 4 12:20:51 iMac ReportCrash[553]: 5 com.apple.CoreFoundation 0x0000000104833d49 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9

Nov 4 12:20:51 iMac ReportCrash[553]: 6 com.apple.CoreFoundation 0x00000001047f651a __CFRunLoopRun + 2586

Nov 4 12:20:51 iMac ReportCrash[553]: 7 com.apple.CoreFoundation 0x00000001047f5867 CFRunLoopRunSpecific + 487

Nov 4 12:20:51 iMac ReportCrash[553]: 8 com.apple.HIToolbox 0x000000010d587d96 RunCurrentEventLoopInMode + 286

Nov 4 12:20:51 iMac ReportCrash[553]: 9 com.apple.HIToolbox 0x000000010d587b06 ReceiveNextEventCommon + 613

Nov 4 12:20:51 iMac ReportCrash[553]: 10 com.apple.HIToolbox 0x000000010d587884 _BlockUntilNextEventMatchingListInModeWithFilter + 64

Nov 4 12:20:51 iMac ReportCrash[553]: 11 com.apple.AppKit 0x0000000102ef7a73 _DPSNextEvent + 2085

Nov 4 12:20:51 iMac ReportCrash[553]: 12 com.apple.AppKit 0x000000010368de34 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044

Nov 4 12:20:51 iMac ReportCrash[553]: 13 com.apple.AppKit 0x0000000102eec885 -[NSApplication run] + 764

Nov 4 12:20:51 iMac ReportCrash[553]: 14 com.apple.AppKit 0x0000000102ebba72 NSApplicationMain + 804

Nov 4 12:20:51 iMac ReportCrash[553]: 15 com.apple.macOS-Installer 0x00000001017fc0ef 0x1017fa000 + 8431

Nov 4 12:20:51 iMac ReportCrash[553]: 16 libdyld.dylib 0x00000001075be015 start + 1

I am having the same stupid problem. I have a MacBook Pro 2017, 13 inch. After installing this last update my Mac wouldn’t boot up and start up. A pop up screen said that there was an error with my macOS High Sierra. Thanks Apple, what a great was to sabotage people’s work so we’re forced to update to Mojave.

I am writing this as this is the first time in 20 years that I have had a near brick situation with installing macOS updates. Equipment: 2017 MBP. OS Software: 10.13.6. Waiting to install Mojave, as being a first adopter burned deep with High Sierra. Updates shown in App Store was Safari 12.0.1 and Security Update 2018-002. Download file size was 1.88GB.

After download, install progress bar commenced and was very erratic and screen went black multiple times. Then after 10 min or so, "The macOS installation couldn't be completed" message with an Installation Log window in the background. There was a retry button so I tried and the same screen showed up and this time I saved the log to my root drive. There was also a Startup Disk button and I chose that to reveal my startup disk and chose that and restarted. It rebooted fine and noticed that Safari 12.0.1 was installed, but Security Update 2018-002 was still showing needed to be installed. There was some stray installer files in my main disk, but ignored and retried the update through App Store. This time it showed the download size was 1.8GB. After download, install progress bar commenced and was very erratic (not just forward, but jumped backward) and the screen went black multiple times. (Multiple restarts during the installation process usually indicates a firmware update.) After 10 min or so, booted up to my account. All seems ok for now (still testing).

I then checked my firmware through System Information and it showed: Boot ROM Version: 185.0.0.0.0. (This will be different for different Mac models. My Mac identifier is MacBookPro14,3.) This number is not the same as it was before, and it has a different numbering system as before. So I did an EFI verification through a Terminal command and my EFI version showed as: MBP142.88Z.F000.B00.1809280842. These two numbers (without the date code at the end) were both the same before this update, but now they are different, so Apple has now done something different with their firmware identification system. Here is a link to a page on how to do an EFI verification and the Boot ROM Versions you should have with your specific Mac model: https://eclecticlight.co/2018/10/31/which-efi-firmware-should-your-mac-be-using- version-3/. The reason I am mentioning this, is because I also had a very erratic update install with one of the earlier versions of High Sierra, and I noticed that there was a firmware update with that update also. Apple has been bundling their firmware updates with software updates which I think is a mistake. Please anyone who can verify their firmware being updated, please let me know, so I can further troubleshoot this issue.

ALSO, I noticed that the download file for the Security Update 2018-002 on the Apple website is only 421.1 MB. Please can anyone explain why the App Store update is almost 5 times larger than the website update?

Thanks all for furthering this issue.

It may say 421Mbs but it is actually 1.82 Gbs if you try to download it. It is just further evidence of Apples poor quality control. also if you choose to download it you will notice it downloads as SecUpd2018-002Sierra.dmg. It does install though.

Thanks for that update on the website download. And yes I read somewhere else about the wrong title to the updater file (yikes), but I never had to download. Also, the name of the updater on their Apple Security Updates webpage HT201222 used to say "Security Update 2018-001" instead of 002. They corrected it yesterday...

Just FYI for all, the Updater crash log that I was able to save noted:

"The main OS Installer distribution (/Volumes/LBS SSD/Library/Updates/AtomicUpdates/041-18191/041-18191.English.dist) did not load with error: The file doesn’t exist."

Glad it helped! I noticed the extra space at the time I posted (and was absolutely sure I had not inserted a space there), tried several times to edit and delete it, it would not be removed...sorry.

...just noticed your post also includes the extra space...bizarre!

Similar entry also existed in my crash report:

"OSInstaller[548]: The main OS Installer distribution (/Volumes/Macintosh HD/Library/Updates/AtomicUpdates/041-18191/041-18191.Dutch.dist) did not load with error: The file doesn’t exist."

In my earlier post I only inserted the ReportCrash log entries. The above message was just before that as part of the OSInstaller process logging, followed by:

"Language Chooser[529]: Child process exited 11"

Is someone at Apple awake?

I had this problem on a MacBook Air (13-inch, Mid 2012).

I hope Apple is working on an update to the Safari and/or Security Update updates but meanwhile it seems that booting in Recovery Mode and reselecting the startup disk again fixes it.

I've update a bunch of machines so far, ranging from Minis, Airs, Non-Retina and Retina MBPs, and they have all failed on the first install of Security Update 2018-002. The only one that succeeded in one try was a 2014 Mac Mini (The others were 2013 or earlier).

Fortunately, at least in my case, all of them booted successfully after the first install failure, and succeeded to install it on the second attempt. Be aware, these updates take flippin' forever to install, most around half an hour. So, don't get impatient and force a shutdown just because you see a black screen for a few minutes, or a progress bar not move for a while. I was panicking on the first couple because I had promised I'd get the computer back to the user within an hour, and after an hour I was still doing the second attempt on them.

BTW, you can easily tell that the first try failed because there is a "macOS Install Data" folder at the root of the volume.

It may be your case pre2014, but there are several people on this site and other sites that are having issues with post 2014 machines. Have you checked your firmware versions with your 2015 MBP as I noted in my first post. Just curious for my own troubleshooting.