Have you tried to wait? It usually works like that, just wait
[doublepost=1524673006][/doublepost]
They always fix a lot of things, but they didn’t mention anything on changelog
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases macOS High Sierra 10.13.4 Security Update
- Thread starter MacRumors
- Start date
- Sort by reaction score
[doublepost=1524673006][/doublepost]
I have noticed that as well. It's one of those things in the UX that I think Apple has degraded. I would like little progress messages that identify what's being installed now (even if it shows for only a couple of seconds as some things fly by). Complete lack of movement ("progress") on your screen fuels anxiety. Or at least better graphics to show that things are still working and not hung.
And then of course there's the totally black screen while the update is allegedly installing (fashionably black to be sure, but just not informative).
Is there anyone at Apple that actually looks at things from the user's perspective anymore? Seems not.
Sorry what I initially meant is that it installs fine but afterwards my MacBook does not boot anymore. First it got stuck at like 70% every time and then I did one of those combos to do a whatever reset and then the progress bar actually moved to 90% but never finishes even over night. After restoring from a backup it works fine. Interestingly hardware test does not work when that happens either
Mine hung during installation too. I let it sit overnight, and it made zero progress. Had to hard reboot.
I never saw this problem pre-High Sierra. Now, I've seen it on multiple Mac across multiple HS updates.
I never saw this problem pre-High Sierra. Now, I've seen it on multiple Mac across multiple HS updates.
You're right, of course. I'm now at 4 hours on my third attempt, and nothing. SMC reset, and I'm back to where I was. Life goes on.
Then that is really strange. I'm just asking - are you sure it might be SIP? Because I have disabled it.
[doublepost=1524686407][/doublepost]
I don't feel comfortable doing that. From what I've read, that can mess up your Mac even more.
Up to you.
Should work and shouldn't mess up your Mac in any way.
You are just chaining the file permissions on the icon file.
Is there something all that exciting, let alone spectacular, expected when it comes to typical security updates?I don't see nothing spectacular about the latest security update, tbh
Came
[doublepost=1524693686][/doublepost]
Would a security update somehow do something about that?
Same thing with me. Except first update to experience this, Started the update, went through the process, then noticed something weird. Screen was black. The little circle of lines was faint in the lower middle of the display. Seems to change VERY slowly. Let it run overnight. Surprised to see it still there in the morning. Hit the power button a couple times, nothing. Kept checking here and no one seemed to display similar activity. Got concerned. Decided to risk it and power down. Hit the power button again. Seemingly nothing. Then....magic. The Apple appeared and the line beneath it started moving. Then got stuck. More concern. Then, a box showing it was updating. 36 minutes to complete (what?). Few minutes later, 17 minutes to complete. Hmmm. Seconds later BAM - login screen.
Glad the update took and I didn't need to restore from Time Machine. I have the 2017 MBP 15" if that matters.
Anyone that has a Mac would know this because it says near the patch notes not in this thread
On your iMac 2012, does it have a hard drive, a Fusion Drive, or a SSD? If it is running a hard drive, and if you're knowledgeable about such things, head into Console and take a look at what the logs are saying. I've been tracking a handful of 10.13.x performance issues that impact hard drive-based Macs that seem NOT to really bother SSD-based Macs (the performance delta between HD and SSD seems to cover the issue up). Specifically, see if there are tons of sandboxd DENY errors (means the Sandboxing feature of macOS is perhaps incorrectly restricting legitimate file access; bug) or if signpost_notificationd is spitting errors about an invalid connection.
In the case of the signpost_notificationd problem, you can abate it until reboot by firing up Activity Monitor and force quitting the process. It will come back, respawn itself, and that's OK; but the performance issue it causes doesn't. Until you reboot. No one seems quite sure what the heck this goofy daemon even DOES, though there is some indication it has to do with GPU/eGPU things.
Another thing I found "helpful" (as in, "Was is helpful? I dunno… seemed to be." LOL) was both booting into Safe Mode (c'mon, Apple, having me do Windows XP-y garbage is appalling) and using OnyX to run the bevy of Maintenance tasks. I also booted into Recovery, disabled SIP, rebooted, let macOS run for a while, ran OnyX again, re-enabled SIP/rebooted... you get the idea... a TON of stupid stuff. But, performance on one of two HD-based iMacs that I've seen with severe 10.13 performance issues seems to have been helped (and the other I haven't touched yet… I want to figure out what the root cause is, so I need a definitive "tester" to test against). YMMV.
Long reply, but I think it might solve the problem. I posted it on the Apple Support Communities at: https://discussions.apple.com/message/33347385#message33347385
Well folks, I struggled through multiple more reboots that, despite me setting App Store to Hide Update, repeatedly crashed the system to the black screen and mouse cursor.
I finally found a solution that worked for me, after using Console in /Applications/Utilities and searching /private/var/install.log for 2018-001 and then lines before and after this and noticing several like this:
2018-04-27 01:01:33+08 iMac Installer[899]: recoveryPartitionVersionForVolume: could not get recovery version information for mount point /Volumes/Time Machine Backups: Unable to find boot helper partition. (-69737)
Hopefully it will work for some of you as well.
Absolutely no thanks at all to Apple.
1. Following longstanding advice from various parties, I disconnected all connected drives. In my case these were Time Machine backup drives connected by USB and by Ethernet, which I ejected and removed from Time Machine backups respectively.
2. I shut down, then after a few seconds pressed power button and then held left shift key for ages to boot into Safe Mode. This took about 10-15 minutes.
3. I opened Terminal in /Applications/Utilities.
4. Since I had hidden updates in a vain attempt to stop the borked shutdown process, I had to re-enable them. So I typed:
softwareupdate --reset-ignored
5. To list the available updates and check that the 2018-001 was still there, I typed:
softwareupdate -l
which responded after quite a pause with
Software Update Tool
Finding available software
Software Update found the following new or updated software:
* Security Update 2018-001-
Security Update 2018-001 ( ), 506017K [recommended] [restart]
6. Thanks to 9to5Mac's article here: https://9to5mac.com/2017/07/20/how-to-update-mac-using-terminal/
I typed the following variation on the author's last suggestion to run a shell script that would install all updates (the -ia switches) in verbose mode (if it works or not), then if successful reboot:
sudo sh -c "softwareupdate -ia --verbose && reboot"
Make sure that the straight quotes "" do not copy over as curly /smart quotes “” because if they do, that line won't work.
Because you are requesting superuser access, you need to enter the Administrator's password at a prompt:
Password:
Which will show a key symbol. It will not echo any characters you type, nor even bullets to represent each character. Type slowly and carefully. It will let you know if the password is incorrectly typed, in which case try again. In my case I got the following response:
Software Update Tool
Finding available software
Downloaded Security Update 2018-001
Installing Security Update 2018-001
I briefly also got some warning about the need to add a --restart option flash on the screen. I think that was in response to the first part of the shell script - i.e. the softwareupdate -ia --verbose part before the &&.
Anyway, the iMac rebooted, this time NOT sticking at a black screen with mouse cursor, but proceeding after a couple of stages to a normal looking boot screen (Apple logo and progress bar) and then a Software Installation / Update screen (sorry, I don't have a picture) and then another progress bar, for the first time with an estimated time (31 minutes).
In fact, the software update installed much quicker than this.
7. Just to be sure, because this one has caused me - and it seems others, too - so much hassle and wasted time, after booting finished and I logged in, I clicked on the Apple logo and selected About This Mac, then clicked again where it displayed 10.13.4 to reveal the build version (17E202).
8. Running App Store did NOT confirm that the update had installled. However, returning to Terminal and typing:
softwareupdate --history
replied with a long list of updates, most recent first, beginning:
Display Name Version Date
------------ ------- ----
Security Update 2018-001 29/04/2018, 18:46:11
The version being blank for this update - adding to the general sloppy vibe of this particular update.
Whew! What a relief. I think I will try to use command line updates in future for a while. Seems these give you more feedback on what's happening than the App Store disaster area.
Please let others know if this helps or not by replying below.
Last edited:
I have to say, that was about the loooongest installation for a Security Update I've seen. It wasn't hours like some are reporting (those sound like other issues). My Mac Pro took about 30 minutes with 2 reboots and 1 weird screen fade out fade in. The other thing strange I noticed was that while my boot drive is an SSD, during the update the physical hard drives were working overtime for some reason. Indexing? Seemed very strange for a security update. I also had to re-enable "NightPatch" for Night Shift because I'm running an unsupported Mac. I only mention that because the only time I have to do that is when there's a full version update. It would seem like we're running 10.13.4.1 rather than a simple security update.
Bless you! I tried it just now, and it worked perfectly. After 4 downloads, 4 black screens, and 4 build numbers not changing, I am now on Build 17E202. Thank you again!
High Sierra doesn't support booting from RAID!
I have a venerable Tower Mac Pro with 4x 2TB mechanical hard disks in the disk bays as RAID10 i.e. mirrored then striped. My boot device is via two striped SSD's mounted in a Sonnet Tempo Pro Plus PCie card. This monster runs like a dream but it won't upgrade to High Sierra because these disk systems are all "part of an Apple RAID setup"!
Fortunately, I also have a 256GB mSata card installed via a PCie card and I'm able to run High Sierra on this albeit not as responsively. In desperation to discover if HS actually supports booting from RAID, I decided to have one last go at undoing the RAID10 on my mechanical disk set up and rebuilding it under DiskUtil from High Sierra. Result - still no luck installing HS on this HS Raided setup. I then undid the RAID10 AGAIN installed HS on one of the mechanical disks (no RAID which worked), used SuperDuper to copy disk image to another location, recreated the RAID10 and was surprised to find I could copy back the disk image to the RAID10 setup via SuperDuper AND IT EVEN BOOTED!
HOWEVER, before anyone gets too excited. I deliberately installed version 10.13.2 of HS such that I could test the update mechanism to 10.13.4. And guess what? NO-GO exactly the same problem unable to install software because your disks "are part of an Apple RAID setup". Even if you manage to install HS onto a RAID setup it looks as though you won't be able to update it!
Looks like the only way I'm getting this to work is to run HS from a single SSD via the Tempo card and get used to slower performance.
Last edited:
I just checked my Macbook Pro and it does have plenty of both Sandboxd deny and signpost_notificationd errors. So you don't think they're relevant on an SSD? My iMac 2012 has a Fusion Drive, but I replaced it over the weekend with the late 2015 model. That one, also with a fusion drive, has the same errors.
I think the errors happen, but on an SSD-based Mac the performance of the drive is SOOOO much better you, the user, don't feel the pain like on a hard drive-based system.
IMHO, yet another sign that exposes Apple's pettiness in how it treats customers that don't spend up for more their expensive offerings. Their failure to adequately QA test and performance optimize is becoming untenable.