Apple security update 2018-002 10.13.6 fails on Mac Pro

This fix (removing ~/Library/Caches, running lsregister, killall Dock and mdutil -E /) also worked for. In addition, I decided to take it in stage, first applying the Safari 12.0.1 fix from the App Store, rebooting, and running through all the steps again before running softwareupdate from the command line to apply the security update. The first time I waited several hours for the spotlight database to rebuild after running mdutil, but the second time I just rebooted.

I have a vague feeling I ran into something like this before since I had installed Onyx (and then forgot about it), and it has a maintenance option to rebuild LaunchServices (possibly just a way of invoking lsregister from a GUI). I thought perhaps my apparent hang was just the update automatically performing one or more of these steps but with no feedback, but none of the commands took a long time to run (a minute or two).

I did get lots of -10811 errors from lsregister, but this seems to a warning if lsregister finds something that is not an application but tries to register it anyway.

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.

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.

David, I had the exact same issues with a very similar configuration (cMP 5,1 octocore 3.46Ghz), and followed almost the exact same steps. I posted the sequence that eventually solved it for me earlier in this thread. Good luck!

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.

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!

I've been burned too many times after upgrading to a 10.x.y where y is less than 4. But, I may have to do it this time.

But, for software developers (one of the machines I'm having issues with is at work), it's not an option. We need to support older versions of macOS. That puts us in a bind. Apple really hurt us with this one.

Did anybody try the following solution? It seems a bit like the 'shotgun solution' as mentioned before.

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

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.

So, is this an issue only if there is an old software update that hasn't been applied yet? Just wondering why Apple hasn't addressed, or maybe it's a very specific issue. I remember in the old days when a "version 2" would come out for an update causing issues.

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.

I had to restore to Time Machine backup after attempting to install this update. After updating, the iMac froze on startup, progress bar not moving. Hours later I finally restored it. I have an iMac Retina 5K, 27-inch, 2017.

Also ran into major problems attempting to upgrade to Mojave last week. It thoroughly corrupted one of the profiles on this machine (my wife's unfortunately). Had to restore from Time Machine then, too.

Sloppy work by Apple. and very poor customer service. I would not buy another Mac.

Hi Kokomorbt.... and greetings from Ireland... 🙂

I have had an awful experience also with that whole Security Update 2018-002... actually, I'm now stuck in a ridiculous situation that I can't even use Recovery Mode to fix the issue as my MacPro 12 Core (Mid 2010) is now incapable of automatically restarting or shutting itself down so I can't even get it to Re-Install High Sierra or upgrade the Firmware to go all the way to macOS Mojave.

I have never used Terminal to fix an issue... but I'm tempted and terrified at the same time to try out your solution... is it just a matter of copy and pasting your steps into the Terminal and that's it... problem solved ?

I have been speaking with multiple Apple Tech Support people and no one has a clue how to resolve this and a Terminal-based solution was never ever ever even been mentioned.

Did it 100% work for you... and what did you do... go back to High Sierra as you were before the update appeared or go all out macOS Mojave... I have a new Sapphire PULSE RX580 Graphics Card good to go and all my workflow apps are 100% macOS Mojave compatible... so I can go Mojave if that helps get me back on track and up to date again, and 100% up to date with my Apple OS software.

Please advise and revert when you get an opportunity.

Hi Anthony, my ancestors are from Cork 🙂

Yes it's simply copy and paste the commands in order. Remove the space in the word "framework" (neither chelidon nor I was able to remove it from our posts). The first command that begins with "sudo" is one very long line and will result in a password prompt in the terminal. Type your Mac password, which won't appear as you type, then hit enter. To be clear, the numerals at the beginning of each line are not to be typed - they just make order clear. Also, the word "Reboot" is instruction to you, not to be typed. After the last reboot our problem was 100% solved, and I can see at least three others apparently had good result. I started and ended with High Sierra. I haven't upgraded to Mojave.

Hopefully that works for you. If it does, please be sure to thank chelidon as well because he is the original author of the fix!

For others reading this, the two posts with the fix are at the bottom of page 3 of the comments.