Apple security update 2018-002 10.13.6 fails on Mac Pro

Hi,


Just tried to update my Mac Pro late 2013 with the newly released Apple security update 2018-002 10.13.6, both via the Mac App Store and by downloading it directly from Apple. The problem I'm having is that just after the restart the screen goes black and then nothing happens. I have tried several times now but the update doesn't start after the restart.


Anyone else having this issue?


/Johnny

Mac Pro, macOS High Sierra (10.13.6)

Posted on Oct 31, 2018 6:42 AM

Reply
Question marked as Top-ranking reply

Posted on Nov 1, 2018 12:49 PM

Hi,

I tried to install this security update both on my Mac Pro 2013 and MacBook Pro 2017 (both 10.13.6).

Mac Pro 2013: after update reboot I got the account screen; after inserting the password the white line went around the end, then I got the white apple black screen with terminal log (I saved a copy) and reboot/switch off options. No way to enter any account; no way to get this repaired thorughout Recovery Partition.

I solved myself by booting my Mac from an external drive with HS 10.13.6 installed and launching Disk Utility S.O.S. from there on my Mac Pro internal SSD.

MacBook Pro 2017: I launched the update. After rebooting I entered my account normally, but App Store is asking for applying the same security update. It seems that it hasn't been installed. Safer to leave it right now.


AppleCare yesterday told me over the phone that there wasn't any issue about this update...

Similar questions

152 replies

Nov 10, 2018 9:41 AM in response to Johnny R.

for macpro5,1 I've solved this issue
if you started the update from Mac App Store and it doesn't install, reboot the system with option key pressed on boot, then select a system volume (Macintosh HD) and boot to system, then download the update as separate installer here Download Security Update 2018-002 (High Sierra)

Install, reboot, wait, then after reboot it works.


Tested on MacPro5,1 2010 with OWC Mercury Accelsior E2 SDD drive as system drive.

Nov 24, 2018 2:51 PM in response to gugy

Did you reboot between terminal commands and software update command?


You might try the steps proposed in post #40 of the following thread from the macrumors forum:

https://forums.macrumors.com/threads/new-high-sierra-security-update-2018-002-10 -13-6-wont-install.2151143/page-2

I don't have the knowledge about these terminal commands, so try at own risk.


Shame on Apple for publishing such a dreadful update!

Nov 25, 2018 9:52 AM in response to gugy

Did you try the method I explained on top of page 9 ?

  1. rm -rf ~/Library/Caches/*
  2. rm -rf ~/Library/Saved\ Application\ State/*
  3. sudo rm -rf /Library/Caches/*
  4. sudo rm -rf /System/Library/Caches/*
  5. atsutil databases -removeUser
  6. sudo atsutil databases -remove
  7. sudo atsutil server -shutdown
  8. sudo atsutil server -ping
  9. sudo rm -rf /var/folders/*

After performing the last Terminal command, Restart. If the update is not automatically restarting during the boot, you may need to have it installed via the AppleStore.

Oct 31, 2018 3:58 PM in response to Johnny R.

Me too - mid 2015 MBP, but came back with an installation failure message - some file permissions failed.

For me, managed to do the Cmd-R and recover back to previous snapshot of the OS, and reboot. Immediately went into App Store Preferences and removed automatic install of system files and security updates, and redid. Safari ok, but it still then tried to automatically apply security update on reboot, which failed again. At least it was consistent. So redid the Cmd-R and recover back to previous snapshot, which blew away my TimeCapsule back up status. Now relatively stable on shutdown/restart, further helped with the Cmd-Opt-P-R clearing of PRAM, but App Store telling me there is an update to do and to restart...not this time matey.

Apple, please fix this? 10.13.6 (17G65), Safari Update (12.0.1) and Security Update 2018-002

Wish I could save the log when the installation fails, but it cannot access the disk so can't.

Nov 2, 2018 12:21 AM in response to Johnny R.

After many tries I had to throw in the towel and updated my Mac Pro to Mojave. I wasn't able to run the updater via MAS because of the issue I had when trying to reboot the Mac. Instead I had to create a USB-installer and booted the Mac via the USB-stick. Now it's up and running again but many of my old apps, such as the ScanSnap from Fujitsu, won't run now.


What a terrible update from Apple! 😠

Nov 4, 2018 8:04 AM in response to EnzoHK

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

Nov 4, 2018 4:39 PM in response to Eau Rouge

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."

Nov 6, 2018 7:26 AM in response to Johnny R.

Yes, I have tired to instal it twice and both times it would look fine after the update was complete but once I restarted it goes to the installer log on boot and says the instal can not be completed. If I click restart the same thing happens over and over and over. It would not even allow a safe boot. I saved the installer log but I am not wise enough to get much from it.


Both times I had to do a recovery from TimeMachine on on an external drive (Thank goodness I had that set up and current). The recovery worked and got me bootable again, and all seems okay so far, but Updater still wants to install the Safari Security Update. I already learned my lesson twice so I will not be trying to instal it a third time. I will use a different browser until Apple has addressed this and released a new update.


Please let me know if you found a fix.

Nov 7, 2018 8:56 AM in response to Niek66

This clears out a different set of directories (the system-wide /Library/Updates/ instead of the per-user ~/Library/Caches). The 'shotgun solution' also rebuilds the 'Launch Services' database which seems likely to play a role in parts of the installation. It also suggest an alternate solution of performing the upgrade as a different user -- perhaps freshly created.

Nov 24, 2018 12:59 PM in response to gugy

I took the dive and followed the steps from chelidon (page 3) to update my MBP 2016.

And it worked!


After the commands via terminal did the reboot followed by

sudo softwareupdate -i -a --verbose

Terminal ended with a notification to immediately reboot. After that the update run for about 10 min.

Another automatic reboot and I could login.


The App Store showed that 2018-002 security update has been applied and Safari is now on version 12.0.1.

Credits to chelidon! Thanks man!


I will do my iMac 27 late 2015 tomorrow.

Nov 25, 2018 8:56 AM in response to Niek66

I did, the computer restarted and the Security update screen came in and updated the whole thing.

the problem persists though. I can only shutdown pressing the power button. Restart is ramdom, with few times working and other not working.


At this point I think the best option is to restore the system using an older version of the software prior of this bad update. I have it on my Time Machine.

Honestly this is a total mess from Apple. I’m hoping they have an update coming soon fixing this issue since it seems is affecting many people.

Thanks

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Apple security update 2018-002 10.13.6 fails on Mac Pro

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.