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.2 Supplemental Update With Spectre Fix
- Thread starter MacRumors
- Start date
- Sort by reaction score
There is a reason why the iMac Pro gets a different build number 17C2205 instead of 17C205 which most other macs get.
There are actually 2 different versions of the supplemental update. 1 for most macs except the iMac Pro, and another specifically for the iMac Pro.
Strangely there is no firmware update except for the iMac Pro. Not since 10.10.1 has there been a macos update without an associated firmware update (including other supplementals, security updates and all betas).
There is also no embedded os firmware either for most macs except the iMac Pro.
10.13.2 Supplemental Update for most macs except iMac Pro:
http://swcdn.apple.com/content/down...9wyripp4v22ni/macOSUpd10.13.2Supplemental.pkg
http://swcdn.apple.com/content/down...pp4v22ni/macOSUpd10.13.2SupplementalPatch.pkg
http://swcdn.apple.com/content/down...yagdvc2q89229x9wyripp4v22ni/BridgeOSBrain.pkg
http://swcdn.apple.com/content/down...9229x9wyripp4v22ni/BridgeOSUpdateCustomer.pkg
http://swcdn.apple.com/content/down...dvc2q89229x9wyripp4v22ni/FullBundleUpdate.pkg
http://swcdn.apple.com/content/down...OSUpd10.13.2Supplemental.RecoveryHDUpdate.pkg
10.13.2 supplemental update specifically for the iMac Pro:
(note only the iMac Pro gets the macos brain, and this time only the iMac Pro gets the embedded os firmware and firmware update)
http://swcdn.apple.com/content/down...0hawoeewmv1p41dv9579bnsgmn3d9z/macOSBrain.pkg
http://swcdn.apple.com/content/down...mn3d9z/macOSUpd10.13.2iMacProSupplemental.pkg
http://swcdn.apple.com/content/down...z/macOSUpd10.13.2iMacProSupplementalPatch.pkg
http://swcdn.apple.com/content/down...oeewmv1p41dv9579bnsgmn3d9z/FirmwareUpdate.pkg
http://swcdn.apple.com/content/down...mv1p41dv9579bnsgmn3d9z/EmbeddedOSFirmware.pkg
http://swcdn.apple.com/content/down...ewmv1p41dv9579bnsgmn3d9z/FullBundleUpdate.pkg
http://swcdn.apple.com/content/down....13.2iMacProSupplemental.RecoveryHDUpdate.pkg
And here is a funny trick. Replace the file extension pkg with pkm in these links and download the pkm file for macOSUpd10.13.2Supplemental.pkg and macOSUpd10.13.2iMacProSupplemental.pkg, i.e., macOSUpd10.13.2Supplemental.pkm and macOSUpd10.13.2iMacProSupplemental.pkm and open the pkm files with textedit and you can see the new build numbers somewhere near the top - BEFORE applying the update.
So you can get these pkm files here:
http://swcdn.apple.com/content/down...9wyripp4v22ni/macOSUpd10.13.2Supplemental.pkm
and
http://swcdn.apple.com/content/down...mn3d9z/macOSUpd10.13.2iMacProSupplemental.pkm
It is 17C205 for most macs except the iMac Pro and 17C2205 for the iMac Pro.
safari 11.0.2 for sierra:
http://swcdn.apple.com/content/down...kxko4twuee5e2eyglb7wua/Safari11.0.2Sierra.pkg
safari 11.0.2 for el capitan:
http://swcdn.apple.com/content/down...a1cgip0haqgpvsmsyjw/Safari11.0.2ElCapitan.pkg
EDIT: Apple have now released new links for the supplemental update:
For macs other than iMac Pro: https://support.apple.com/kb/DL1951?viewlocale=en_US&locale=en_US
For iMac Pro: https://support.apple.com/kb/DL1950?viewlocale=en_US&locale=en_US
These should be easier to install than the version previously posted above because they have combined the 6 or 7 installers into a single one.
Last edited:
Leave it and wait... took a while on the new iMac Pro 10 core as well.
I've a very nice (unused) OS X Lion mini usb key I can sell you if you're willing to pay collectors prices for it ;-)
Maybe i don't understand your comment. My 2011 mini is on the obsolete list yet I got the update back in Dec. AND today! So what update should I not have gotten?
Geekbench results for me pre and post update.
Pre Spectre Fix: https://browser.geekbench.com/v4/cpu/6241225
And after fix: https://browser.geekbench.com/v4/cpu/6241845
My scores went up across the board! Both ran on fresh boot with nothing else open.
Pre Spectre Fix: https://browser.geekbench.com/v4/cpu/6241225
And after fix: https://browser.geekbench.com/v4/cpu/6241845
My scores went up across the board! Both ran on fresh boot with nothing else open.
This one can take a while to install, even though the download itself is quite small.
On my Mac mini (2011) it took almost an hour, and most of that time was just sitting at the black screen with silver Apple logo, underneath which there was text along the lines of, “Installation in progress. Calculating time remaining...” For some, it may sit in that state for some time (over half an hour in my case.) So, my advice is to just be patient, leave it alone, and not restart your system, for those that run into the same thing. Otherwise, you will be rebooting in recovery mode and reinstalling macOS, as restarting at that point will most likely put your system in an unusable state.
Took less than 5 minutes to install on my mid2012 15” Unibody MacBook Pro.
(Both systems have SATA3-connected SSDs in them (same model and capacity.) While my MacBook Pro was fresh-installed with 10.13 when it released last fall, the Mac mini has always gone through upgrade steps from Yosemite onwards, including a restore from Time Machine backup when I put the SSD in it. So, maybe that has something to do with it.)
On my Mac mini (2011) it took almost an hour, and most of that time was just sitting at the black screen with silver Apple logo, underneath which there was text along the lines of, “Installation in progress. Calculating time remaining...” For some, it may sit in that state for some time (over half an hour in my case.) So, my advice is to just be patient, leave it alone, and not restart your system, for those that run into the same thing. Otherwise, you will be rebooting in recovery mode and reinstalling macOS, as restarting at that point will most likely put your system in an unusable state.
Took less than 5 minutes to install on my mid2012 15” Unibody MacBook Pro.
(Both systems have SATA3-connected SSDs in them (same model and capacity.) While my MacBook Pro was fresh-installed with 10.13 when it released last fall, the Mac mini has always gone through upgrade steps from Yosemite onwards, including a restore from Time Machine backup when I put the SSD in it. So, maybe that has something to do with it.)
Last edited:
This also installs in HS, but as I understand it, the build number should be (13604.4.7.1.6) but, at least for me it remained at (13604.4.7.1.3).
Lou
Can confirm, if you think it is frozen and not installing, just get up, step away from the desk, grab a beer, and go back 1/2 hour later. It is a SLOW install.
Like my mum says, “ a watched pot never boils.”
Like my mum says, “ a watched pot never boils.”
I did the supplemental update on my 2017 MacBook Pro, using Geekbench 4. It seems like a wash to me, no performance penalties or enhancements. I have been using the laptop for about 3 hours, seems fine to me:
Before:
single core: 4539
multi core: 15527
After:
single core: 4545
multi core: 15522
Before:
single core: 4539
multi core: 15527
After:
single core: 4545
multi core: 15522
That's odd. They got rid of having to reboot the OS for Safari updates some time ago, so I thought things were decoupled from any system-level hijinks by this point.
But I guess I'm more concerned right now with why El Cap and Sierra did not get the Meltdown fixes. They got a lot of other fixes at the same time as High Sierra, but specifically not the Meltdown stuff.
Don't install Safari11.0.2Sierra.pkg into High Sierra. It is only for Sierra. For High Sierra install the Supplemental Update instead. That will update Safari too.
Safari builds are going to be
11604.4.7.1.6 for El Capitan
12604.4.7.1.6 for Sierra
13604.4.7.1.6 for High Sierra for most macs except iMac Pro
13604.4.7.10.6 for High Sierra for iMac Pro.
This information can come from the pkm files obtained in the manner I previously described - even before installing it.
Last edited:
Benchmarks are in on my cMP with X5677. This is versus 10.12.6. Results were ever so slightly up from 10.13.2 pre-supplimental.
Handbrake 1.0.7: 720p convert to 480p (fast): 1% loss in average FPS
Luxmark 3.1 Lobby (CPU C++): 1% decrease in score
Corona 1.3: ~0% change in average Rays/sec
In other words, nothing to see here! Falls under margin-of-error testing.
For what it's worth, the update took about 10 minutes. I have a relatively cheap 120GB SSD for my OS drive.
Handbrake 1.0.7: 720p convert to 480p (fast): 1% loss in average FPS
Luxmark 3.1 Lobby (CPU C++): 1% decrease in score
Corona 1.3: ~0% change in average Rays/sec
In other words, nothing to see here! Falls under margin-of-error testing.
For what it's worth, the update took about 10 minutes. I have a relatively cheap 120GB SSD for my OS drive.
That is just a few background processes triggering under til first one (during single core test; and the other way for the multi-core). So I would call those numbers identical. Geekbench is not that precise.
Did you do a backup before updating?
Apple tell developers to always backup before installing a beta in case things go awry. But I go much further than that. I backup before installing ANYTHING. Even apps.
I know that on the two Mac Pro's I updated today with this supplimental update, that during that black screen, your normal startup apps are UP and running! While it was sitting on the black screen with the "xx minutes remaining", I heard the Outlook new mail sound. As soon as the update was done, I was at the login screen and when I logged in, everything in my startup was already started up.
So somehow, the update logged me in and started all my startup items, but required me to authenticate and login once the update was done.
So somehow, the update logged me in and started all my startup items, but required me to authenticate and login once the update was done.
Mine only took about 10 minutes. This made me curious, so I read through the install log /var/log/install.log - to see yours just open Terminal set it to full screen and hit cmd + a few times until the font is large enough for you to read and then type in a command like: tail -n 2000 /var/log/system.log | more
Reading carefully through that I learn things that will make me do things differently next time. For example, I don't usually use my normal userid to do upgrades as I have a separate admin account for that kind of thing. Well today I found out that it hadn't upgraded my photos or mail libraries because it thought they hadn't been used for a long time, oops.
Anyway, this upgrade updates many app sandboxing configurations, the EFI stuff, the boot and recovery partitions, base system caches and registers some hidden opendirectory nodes, amongst other things. Have a look at the install.log if you're interested.
The upgrading of photos and mail libraries could explain why it's taking so long for some people.
Reading carefully through that I learn things that will make me do things differently next time. For example, I don't usually use my normal userid to do upgrades as I have a separate admin account for that kind of thing. Well today I found out that it hadn't upgraded my photos or mail libraries because it thought they hadn't been used for a long time, oops.
Anyway, this upgrade updates many app sandboxing configurations, the EFI stuff, the boot and recovery partitions, base system caches and registers some hidden opendirectory nodes, amongst other things. Have a look at the install.log if you're interested.
The upgrading of photos and mail libraries could explain why it's taking so long for some people.
Last edited:
It took me almost 30 minutes with a quad i7 late 2012 Mini and SSD. It's slow. It takes a while. Fortunately I did use CCC to clone my startup disk an hour earlier, just in case it bricked.
why yes, spectre is not isolated to either macs nor high sierra, not updating to high sierra because its bug ridden while referring to a single unrelated bug is pretty pretty shortsighted.
If you have everything backed up, as you should, a restart should get you back in the game.
How dare they abandon people with machines more then 8 years old.
I'm not aware of machines that can support Yosemite and cannot support El Capitan or Sierra.
There are a lot of people that cannot upgrade to High Sierra yet because some gear in the pro audio network isn't yet fully optimised to it, gear that is worth much, much more than a Mac that comes with High Sierra out of the box.
Official compatibility and real world stability are two different things in this world, that's why we stay behind one or two versions.
It is not our personal preference that Apple "has" to release a new version each year and we need to have the latest iMessage or whatever features, we would gladly prefer the strategy that was applied in the Tiger/Leopard/Snow Leopard days. We need security and a rock solid system, that's why we buy Apple products in the first place, right?