Apple security update 2018-002 10.13.6 fails on Mac Pro

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]

I have been trying for a week or so to push the (High) Sierra security update 01/02 combo update into an almost offline Mac Pro (Mid 2012) hexacore 3.33GHz.

current OS 10.13.6(17G65)

I hav enow used the excellent ex-NSA Kextvwr to remove all non system kexts and extensions, disabled all the hardening tweaks, and persuaded the old Mac Pro to restart in Safe Mode, after SMC reset and PRAM reset.

the 1.815309721GB blob of SecUpd2018-002Sierra.dmg pretends to install, but is unable to restart during the update process and simply sticks at a black screen which flashes white (silent bong) when I touch the 'any' key

very annoying, and potentially damaging depending on how long it can take those intelligent script-kiddies to diff & reverse-engineer the (working) version of (High) Sierra security update 01/02 combo update, if they have made it work.

I had to install it several times on my 6,1. And, strangely, I've had other issues I haven't seen here: random reboots. Closed all programs and went away for 2 days. When I came back, the machine had rebooted.

Also, I tried to reboot before that, and it hung and required me to hold the power button.

This is extremely frustrating to see all these people having problems like this with a "security" update. Clearly adding APFS is not about security.

And, to top this off, my machine at work, a 5,1, was bricked over this. Will try the SMC/PRAM reset when I get into the office.

Sure thing: Re: Apple security update 2018-002 10.13.6 fails on Mac Pro

Looks like it's worked for some other folks, too. Note there's an extra space in one of the lines -- weird glitch, that needs to be removed.

Same issue here, tried twice and issues both times - MacBook Pro Late 2011.

First try installed security update fine, loaded into OSX, however App Store was still showing the security update is required. So rebooted, however it came up with the installation error log after the chime and loading bar was showing. Can’t remember exactly what it said, but I selected the start up disc here. After a couple of reboots it booted into OSX again fine and was still showing the update.

So tried again second time, this time using the link from the Apple website for the security update. Apple site said the update is 411mb but actually 1.8GB file downloads. Again it installed fine and booted into OSX. This time App Store showed the update had installed successfully and no updates required.

So tried to reboot again to check it still boots up ok, and hit the issue this time again, but worse. After the startup chime and loading bar gets half way, it just get a white screen with no entry sign. Option boot wouldn’t show me any other start up discs, only MacHD. So I was left with having to time machine restore. After this the update is still showing as required!

Any ideas what to try next?

Would the sequence of commands posted earlier solve this? When exactly do you run the commands? After the installation has completed successfully, and before you try to reboot manually. Or before you start the installation?

Any help would be appreciated - thanks!

Hi again all... 🙂

I had and have the exact same issue.... but now that black hang screen is happening all the time even when I try and shut down my main computer at night... I now have to Force Power OFF my MacPro 12 Core (Mid 2010) to get it to shut down... I have tried numerous options to try and get the Security Update to install... even from a different account and anything involving a shutdown won't apply as my machine will not now automatically shut down... I have to Force Power OFF and the update never gets applied.

I said... to **** with it and I will just reinstall the macOS using macOS Re-install using Recovery Mode... but that too needs a firmware update and a restart which just does not happen... again the screen just hangs and hangs... so I tried to go all the way and bypass the Security Update altogether and install macOS Mojave... but I find out that also needs a Firmware update... and a Shutdown Restart... and that doesn't happen also... I hard press the Power OFF button and my machine (luckily as it could be alot worse) boots back into my current version of High Sierra 10.13.6 with that bloody Security Update 2018-002 waiting for me again in the App Store Updates section.

Anyone else having this exact same similar issue... and any possible fixes.

Apple tech support haven't a clue... 😟

This is pretty much what happened to me on my 2016 MBP. Fails to boot with "[auth] failed to write <private>". I booted into recovery with ⌘R and checked the drive with Disk Utility. After that came up clean, I reinstalled the OS to the same drive and seem to be back where I started. However, when I boot up now, it doesn't always succeed. Sometimes I get kernel panics, and of course it says I still need the update.

Hi Anthony, my name is Richard and my great great great grandfather was Captain Jasper Travers from Courtmacsherry, Cork, 1811-1881. Nice to meet you 🙂

The fix chelidon posted, and I added a bit to, was to fix our High Sierra Macs hanging while installing the latest Security update 2018 - 002. Neither of us was attempting upgrade to Mojave. If your Mac needs a firmware update, I would strongly recommend you install the firmware update separately before attempting upgrade to Mojave. You should be able to find it here Apple - Support - Downloads

Hi Anthony, I haven't visited there, but hope to some day!

I've never had your exact problem so I'm reluctant to advise further. QuietMacFan kindly offered to help if you post your logs, so I suggest you take him up on his offer.

Cheers,

Richard

I totally agree Parky50, but no one is listening... I have been chasing a solution to this since last week and nothing.... I'm stuck with a MacPro 12 Core (Mid 2010) that cannot now be shutdown by the OS... only a hard force Power OFF... a total disaster... I purchased a new Sapphaire PULSE RX580 which I have installed in my MacPro... working perfectly... except I can't update to macOS Mojave either as first my computer needs a new Firmware update and to do that my MacPro must shutdown and restart and it's unable to do so over this totally crappy Apple Security Update 2018-002... I have an Apple Tech Support guy assisting me with this issue... well hopefully he can... I will report back if I get any updates or solutions.

I’m a little surprised too that Apple has not addressed this more expediently. Clearly there’s a widespread issue that needs to be addresse. In my 25+ years on Mac computers I’ve never had some like this happen to me. I too had to restore from Time Machine overnight to get back to work. I was an Apple trainer for a few years and always told people to backup to TM before doing any updates. I think of all the times we helped trainees update from the App Store without incident. This is quite unusual so you think they’d be quick to fix it.

Hello again chelidon...

I just wanted to thank you again for all your help with my issue. This morning I decided to take the plunge and go for it in relation to using your Terminal code fix to resolve my screen hanging and force Power Off issues... and it worked perfectly... a few scary running code moments that freaked me out... but within a few mins I was back to HIgh Sierra and inside the App Store I could visibly see that the Security Update had been indeed applied. So thank you so so so much.

I then decided as things were going well to go and install macOS Mojave... all looked good as I was able to install the Firmware Update successfully.... but then as the more main part of the install started to progress I repeatedly encountered a "macOS Installation resources not available" error... I performed a PR RAM reset plus a Disk First Aid plus switched over to a guest account where the macOS Mojave update started to install successfully... after about 45 mins... a few scary black screens, white screens and hanging progress bars up came macOS Mojave and no issues since.

It's like having a new computer... this upgrade to the Sapphire PULSE RX580 Graphics Card plus the new macOS Mojave enhancements makes my vintage MacPro 12 Core (Mid 2010) with 64GB RAM and 500GB SSD, feel like a 2018 machine all over again. Actually, it still feels way faster than my recent purchase of a maxed out MacBook Pro 2017 with Touchbar and 16GB RAM.

I think I will squeeze another 1-2 years out of this now until the new offering of the MacPro 2019 with Standalone Monitor finally arrives.

Thank you again chelidon... 🙂

I had a similar issue (posted earlier in the thread). No working solution found so far.

First time I tried installation failed. Showed the logs on boot up and after changing the start up disk from installer to normal it booted fine and showed the update still in ap store.

Tried again and it updated fine and logged back into OS X and App Store showed update as successful. Shut down and then on reboot the loading bar just gets stuck half way and then shows a no entry sign. Had to do a time machine restore.

Not experience the issue with shutdown / reboot that had been mentioned a fair bit in this thread.

Holding off trying to do the update again until I find someone who has had some success to this type of issue

On my iMac i went from having a 2018-002 security update a safari update to a combo safari and 2018-002 and now that has been replaced by a combo safari and 2018-003 so it looks like the 003 supercedes the 002. Not touching it !

I gave 2018-003 a try on my iMac late 2010 after having reinstalled because of previous update problems. It went into some kind of verbose error log and I had to recover using time machine. I might try again to save the log details, but the error output was the length of a novel and did not make much sense to me.