security update 2018-02 10.13.6 installation log loop

I had the same problem on a MacPro 17 (2012), on HighSierra.

After a number of trials, here are the various cleaning actions I ran on Terminal (but I don't know for sure which of these commands really wiped away the problem, it is only affecting caches functions, anyway), please type them in a Terminal session, one-by-one :

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.

Hi,

I just tried to update my Mac Pro (late 2013) with 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.

/Johnny

Same for me. After manual ShutDown/Restart, the AppleStore shows this update as 'Intalled' but also as 'Restart required' really weird.

In addition I noticed that the SHUTDOWN function from the Toolbar () is corrupted since I installed this update. If I need to SHUTDOWN, I have to use the Keyboard command.

I'am waiting a reaction from Apple assistance supervisor team

First time ever an update borked any Mac we own. This and the Safari 12.0.1 update appeared. I clicked to update all. Both downloaded and installed. And yet, when I was back at the desktop, the App Store said the security update needed to be downloaded and installed. I knew that was wrong since I watched it download that 1.8 GB file the first time and go through the whole installation restart and such.

I clicked to install anyway just to clear it. Sure enough, it downloaded the entire thing again. Only this time when the Mac was supposed to restart back to the desktop, I got something similar to the desktop background of Recovery Mode, a window filled with log errors, and a box with choices to shut down, restart and a couple of others. I restarted and ended up back at the same place.

Good thing for backups. I booted to another partition I have High Sierra on and saved my updated email from the non-bootable drive, then restored my very recent clone backup with Super Duper!. This time, I only allowed the App Store to install the Safari update. I downloaded the security update separately.

Download Security Update 2018-002 (High Sierra)

That worked without issue.

Safe Boot from the HD, (holding Shift key down at bootup), does the problem occur in Safe Mode?

Then, instead of using the App Store, download it directly...

https://support.apple.com/kb/DL1997?locale=en_US

Then install it while in Safe Mode.

I am thinking that although this is not the last update my MacBook Pro will support there is little point in continuing with faulty updates. This one (security update 2018-2) took five attempts to boot up before it succeeded. It now appears to be running fine, but there are two good reasons for not doing further updates:

1. The next one may crash permenantly rendering my laptop dead and a lot of important data lost. Yes I do back up but this is just asking for trouble.
2. My iMac is now “frozen” on High Sierra with no support from next April (?). I want the two machines to be compatible - ie swap files properly and talk to each other without having to spend time “fixing it”.

So I think, unless someone knows better - I’m stepping updates here.

I'm in the exactly same boat and also got my MacBook Pro (Late 2011) to boot again after selecting the start drive manually – was not the first try though...

Anyway, tossed and turned in bed and finally decided to restore the OS from a TimeMachine backup. Crazy, no problems updating since Lion and then this...

002 Secuirity update is on hold for now. However, does anybody know if it would have been save to use the mac after the installation log loop?

I also had this issue with my mid-2010 MacBook Pro after starting the 10.13.6 2018-002 security update from the app store. My fix was to go into recovery mode, select 'Startup Disk' from the dropdown menu to boot from my main drive to skip the reboot installation loop. There is also an ongoing discussion here:

New High Sierra Security Update 2018-002 10.13.6 Won't Install | MacRumors Forums

Hello All,

I'm having the same issue I have a late 2009 iMac running 10.13.6

Model Name: iMac

Model Identifier: iMac10,1

Processor Name: Intel Core 2 Duo

Processor Speed: 3.06 GHz

Number of Processors: 1

Total Number of Cores: 2

L2 Cache: 3 MB

Memory: 12 GB

Boot ROM Version: IM101.00D0.B00

SMC Version (system): 1.52f9

I get stuck in the restart loop. I used the method above to revert back to before the update and got back up and running. Apple, PLEASE fix this. This is a bug for sure.

Thanks!

Does this mean my already downloaded bad update will get re-written/downloaded and it will be safe to install after they re-release it .... or .... Do i have to go in and find the download and delete it now and wait for the new one?

In looking through all the threads it seems to me that many people who are reporting this same problem are running Mac Book Pros. I am wondering if this issue is localized to just this device or if people running desktops are experiencing the same issue. When I performed the Safari 12.0.1 update on a MBP, the update seemed to to take. In fact it shows it as Installed on Nov 1, 2018. However, when the updated Mac Book Pro was started this morning, the Installer and crash log launched with the same error message. Tried to do a restart to finish the supposed installation with the same error being reported. Sent the error log to Apple and I was able to use the Start Up Disk Utility to select my Mac HD that has the original Mac OS on it and restarted the device. There is also now another Security Update 2018-002 10.13.6 which may address this issue. Running a security scan though - just to be safe.

I'm running a late 2015 5k iMac and had the same issue. It appeared to install fine day before yesterday, used the computer throughout the day. Shut it down that night and when I started it yesterday morning, it went into the same crashing install loop described here. I booted in recovery mode and reinstalled 10.13.6 and it's been fine since. Update still appears in the App store, but I'm holding off on installing...

Glad to hear that it worked for you Kurt. Can I ask if you a question though?

After you installed the security update from the App Store which requires a restart, did you shut the device down and then did a fresh reboot? Some people have reported that the install went well at first. But then the problem only appeared after the device was shut down for a period of time and then restarted later in the day or the next morning. We have two other devices (1 desktop and 1 laptop) requiring this update and just wanted to know that you were successful at shutting down and restarting your device without any errors. Would appreciate your reply before we initiate the update.

That is an excellent question. Something I hadn't yet verified. After everything worked as expected, I updated my SuperDuper! clone backup and went back to getting work done.

I just now shut my 2010 Mac Pro down and let it sit for 20 seconds before powering back up. No issue. It came up to the High Sierra desktop as expected.

I had the same issue yesterday, now the second time, with my MacBook Pro 17'' late 2018. My MacBook did not boot again. It showed the Apple logo and fully filled progress bar and then a black screen and no further reaction.

After first failed installation two weeks ago, I contacted apple support and they told they are not aware of any issues with the update 2018-02 10.13.6 . Now again. I tried to reinstall High Sierra without success. I had to install from Time-Machine backup, which is still running.

Did anybody successfully installed this security update on a MacBook Pro like mine?