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 Mojave 10.14.6 Supplemental Update 2
- Thread starter MacRumors
- Start date
- Sort by reaction score
Best part is that you still get to update annually because it's all relative!
This also factors into when I buy a new Mac now. There may be a 16" MacBook Pro released next month but do I want to break all my 32-bit apps, and deal with all the frustration... I'll wait to make that purchase until the OS it ships with is stable (whether that's March, July or September of next year).
Last edited:
I think that was a joke given the emoji reference. But maybe not.
Yes it is. Two in august of this year (august 1st and august 26th) and now this one. First supplemental update gave version number: 18G87 and the next update later that august yielded version number 18G95.
DuckDuckGo Search
Last week I created a bootable Mojave installation thumb drive* in case I have to revert to Mojave from Catalina if I buy a new Mac that comes with Catalina (mainly due to 32-bit apps that work perfectly and will never be converted to 64-bit)). I had assumed there would be no more updates to Mojave. But then again, I assume Apple will continue issuing security updates for Mojave after Catalina is released.
* https://www.imore.com/how-make-bootable-installer-drive-downgrade
I had Safari 13 as a separate update a while back, not long but recently like the last week maybe. I also had another one today not sure what it was, then this 1.25GB one as well.
I'd rather ask, why not drop 10? By now it looks really ridiculous. Then it would be 14.8.2.
Considering that Windows Vista reported its version as 6.0, Windows 7 as 6.1, Windows 8 as 6.2, and Windows 8.1 as 6.3 it isn't just Apple's problem.
Umm... care to tell us where you saw that? If I'm not mistaken the full installer on the MAS has NOT been updated.
LOL! When Apple Inc. begins to make equipment worthy of the premium they charge AND the use case is compelling for my business, I will.
I've upgraded my money and so far Apple is still incompatible with it.
Yes - I don't normally use MAS to download current macOS installers. I use the python script "installinstallmacos.py" from github. There's a couple of different versions, and I use this one.
I ran that today, and noticed that 10.14.6 was updated today, with a new build number.
For those who might be nervous about using a non-Apple source for system installers, that's not really what happens here. It's just a script that goes to Apple's download servers, and gets whatever is current directly from Apple. Makes a simple process to keep my set of OS X/macOS installers up-to-date.
I dearly miss the days when Apple's Support Downloads page wasn't lobotimized, and one could easily find and download the appropriate installer without a second thought.
It turns out that the link to the update page downloads v2, but one can't be sure when the main browser page entry is dated August 26th, the item page post date is dated September 26th, and there is no mention of "2" anywhere.
(And let's not get into the ridiculousness that this is actually the third "supplemental update" that has been posted.)
One has to divine from the post date that they could be on the right path, but not until the file is download, mounted, and the file dates scrutinized to be doubly sure.
These are not difficult things to correct, and the lack of clarity is doubly important when Apple has already pulled the original post, replaced it, and now there is a third version with nary a way to easily tell them apart at a glance.
Users who don't wish to get into the minutiae can simply use the Software Update pref pane; no problem with that. But at least acknowledge that those who seek out the installer package files do have a greater sense of awareness, and don't make things harder for them.
It turns out that the link to the update page downloads v2, but one can't be sure when the main browser page entry is dated August 26th, the item page post date is dated September 26th, and there is no mention of "2" anywhere.
(And let's not get into the ridiculousness that this is actually the third "supplemental update" that has been posted.)
One has to divine from the post date that they could be on the right path, but not until the file is download, mounted, and the file dates scrutinized to be doubly sure.
These are not difficult things to correct, and the lack of clarity is doubly important when Apple has already pulled the original post, replaced it, and now there is a third version with nary a way to easily tell them apart at a glance.
Users who don't wish to get into the minutiae can simply use the Software Update pref pane; no problem with that. But at least acknowledge that those who seek out the installer package files do have a greater sense of awareness, and don't make things harder for them.
Safari 13.0.1 is also available to download. Not sure why MR hasn’t covered Safari 13’s release
Interesting. My system doesn't see the update.
When I downloaded the installer for the update, it won't allow it to be installed because it says it is not installable on this drive as it can only install it on drives that are APFS-formatted.
But my drive in question is that way because it is a fusion drive and they never managed to get APFS going on fusion drives last I heard.
So - what now?
Update: I get it. My internal drive is running APFS but my external SSD I've been using to boot the system lately is HFS+ because I used superduper to duplicate my internal drive. Doesn't seem like I can do a duplicate of the internal drive APFS to APFS.
When I downloaded the installer for the update, it won't allow it to be installed because it says it is not installable on this drive as it can only install it on drives that are APFS-formatted.
But my drive in question is that way because it is a fusion drive and they never managed to get APFS going on fusion drives last I heard.
So - what now?
Update: I get it. My internal drive is running APFS but my external SSD I've been using to boot the system lately is HFS+ because I used superduper to duplicate my internal drive. Doesn't seem like I can do a duplicate of the internal drive APFS to APFS.
Last edited:
Even more interesting - there may be video driver issues with this update - my 5k iMac turned the display into a square with a weird rectangle in the upper right hand corner flashing millions of lines of code or the like. That may have been a mistake to update. Comes back after successive reboots. Doesn't effect my Boot Camp partition. I'll see about my other SSD boot drive.