Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

10.14.3

harriska2 said:
I'm on 10.14.1. Anyone with a 2018 Mac mini can confirm it doesn't break basic things like booting, external usb3 drives, Photos, etc.?
Click to expand...

In 99.9% of cases it won't break anything. The problem is no one can guarantee you won't be one of the unlucky one's where some voodoo happens and it ****s everything up.

So ... the rule is, before any update, use carbon copy cloner to image everything on your boot drive exactly as it is right before the update. Then go ahead and update! At that point you have no worries if the update somehow (unlikely) causes an issue.
 
  • Like
Reactions: MSastre
Updating went fine...Actual install took about 27 minutes...
Haven't noticed a decrease in start-up time but the beach balling seems a lot less...
Now in the process of making its 1st TM back-up...(preparing back-up)
Will check back later or tomorrow...
 
Did this ever hit the front page of MacRumors? I always see updates about the beta versions, but now that the actual update hit, they didn't report it??!
 
This may be a stupid question, and I am likely missing something simple, but I cannot for the life of me get the combo update to install. Every time I get to the destination drive, which is Macintosh HD on 10.14.2, it says that it can't be installed on this disk because it does not meet the requirements for this update.

Guess I'll just do what I normally do, which is boot into the recovery partition and reinstall OS directly onto the computer....
 
internetrando said:
This may be a stupid question, and I am likely missing something simple, but I cannot for the life of me get the combo update to install. Every time I get to the destination drive, which is Macintosh HD on 10.14.2, it says that it can't be installed on this disk because it does not meet the requirements for this update.

Guess I'll just do what I normally do, which is boot into the recovery partition and reinstall OS directly onto the computer....
Click to expand...

You're not doing anything wrong, this is a known issue. Try installing the delta update instead, it should work.
 
  • Like
Reactions: internetrando
inarush said:
You're not doing anything wrong, this is a known issue. Try installing the delta update instead, it should work.
Click to expand...

I skipped the delta update this time. I had a terrible experience with a delta failure and avoid them like the plague.

Since Apple replaced that computer, due to the update failure and related hardware failures, I have always done a full reinstall from recovery partition - downloading a fresh copy of the OS. This effectively copies the same update sequence that the iPhone and other iOS devices use when updated through iTunes...so I was told.

I was hoping the combo update would save me the time - or at least cut down on it.
 
  • Like
Reactions: inarush
internetrando said:
I skipped the delta update this time. I had a terrible experience with a delta failure and avoid them like the plague. Since Apple replaced that computer, due to the update failure and related hardware failures, I have always done a full reinstall from recovery partition - downloading a fresh copy of the OS. This effectively copies the same update sequence that the iPhone and other iOS devices use when updated through iTunes...so I was told. I was hoping the combo update would save me the time - or at least cut down on it.
Click to expand...
That’s interesting. I wonder if this is a “best practice” for doing Mac OS updates? I am dealing with a problem that might, hoping against hope, clean up with a combo update this time around. I normally do ordinary delta updates.
 
  • Like
Reactions: internetrando
I just upgraded my 2017 iMac from 10.14.2 via SysPrefs. Perhaps because it's not got a T2 chip, it didn't require multiple reboots this time, probably an indication that no firmware upgrade was involved. Anyway, it went very smoothly and finished in 11 minutes. That doesn't include download time as the files were served from Content Cache.

NB: A Gatekeeper Configuration Data update was installed automatically this morning, before I upgraded to 10.14.3.
 
madmin said:
I just upgraded my 2017 iMac from 10.14.2 via SysPrefs. Perhaps because it's not got a T2 chip, it didn't require multiple reboots this time, probably an indication that no firmware upgrade was involved. Anyway, it went very smoothly and finished in 11 minutes. That doesn't include download time as the files were served from Content Cache.

NB: A Gatekeeper Configuration Data update was installed automatically this morning, before I upgraded to 10.14.3.
Click to expand...
I have a 2017 iMac and used the delta update. it rebooted twice i believe, may have been once though as I had to take a call so could have missed one reboot, but still the machine shut down and rebooted at least once and it took longer than 11 minutes. The iMac has a 1TB SSD with an i7, and it seems to be running just fine.
 
Easttime said:
That’s interesting. I wonder if this is a “best practice” for doing Mac OS updates? I am dealing with a problem that might, hoping against hope, clean up with a combo update this time around. I normally do ordinary delta updates.
Click to expand...

Give it a try and see how it works out for you. It may be a placebo, but it has always served me well since they told me to install updates that way.

It just downloads an entire new copy of the newest operating system and installs in place of the old one, leaving all your data in place. The biggest downside is time - it can take an hour or more to download depending on your internet speed and then you have install times on top of it.
 
Last edited:
Easttime said:
That’s interesting. I wonder if this is a “best practice” for doing Mac OS updates? I am dealing with a problem that might, hoping against hope, clean up with a combo update this time around. I normally do ordinary delta updates.
Click to expand...
I've been updating hundreds of Macs for years, and never use the combo updater to do so, unless it's required because an interim version was skipped.
 
2013 nMP was a 1.79G download and the 2018 mini was a 2.3G D/l . 11 Min. 2 secs to install on the mini. All working properly.
 
Last edited:
Installed 10.4.3 to my "mule drive" (APFS) last night.

This morning, used CarbonCopyCloner to clone it to my Mojave SSD test drive, it's now up and running under the HFS+ file system, no problems.
 
Anyone else having problems with the noscript extension in Firefox causing occasional pauses in web browsing since updating to 10.14.3?

Once I disable noscript, everything works fine. With it active, Firefox will occationally just keep trying to load a site for a few minutes, then start working again.
 
Last edited:
internetrando said:
This may be a stupid question, and I am likely missing something simple, but I cannot for the life of me get the combo update to install. Every time I get to the destination drive, which is Macintosh HD on 10.14.2, it says that it can't be installed on this disk because it does not meet the requirements for this update.

Guess I'll just do what I normally do, which is boot into the recovery partition and reinstall OS directly onto the computer....
Click to expand...
The Combo update has a problem with the Volume check portion of the Distribution file which is part of the installation package.
One section of the Volume check, checks the Macs operating system Build Numbers of your Mac (each version of macOS has a unique build number 10.14.3 is 18D42), there is an array it refers to, if your Build Number is not on the list then the installation will stop with the error notice people are experiencing. I noticed this list in the Volume check only contains nine Build Numbers compared to what is usually significantly more, for example the previous 10.14.2 Combo has 32 different Build Numbers in its array. This will be correct as the Combo needs to be able to update earlier versions of the OS, and this includes Beta builds.
Out of interest I looked at the distribution file contained in the Delta update, and it has many more Build Numbers, so I wonder if Apple mixed the two up.
I inserted the Build Number of my Mac into the Build Number array, saved the Distribution file, repackaged the Combo folder. Clicked the new modified package and the Combo installed.
 
  • Like
Reactions: getrealbro, dogslobber, inarush and 1 other person
L Caputo said:
The Combo update has a problem with the Volume check portion of the Distribution file which is part of the installation package.
One section of the Volume check, checks the Macs operating system Build Numbers of your Mac (each version of macOS has a unique build number 10.14.3 is 18D42), there is an array it refers to, if your Build Number is not on the list then the installation will stop with the error notice people are experiencing. I noticed this list in the Volume check only contains nine Build Numbers compared to what is usually significantly more, for example the previous 10.14.2 Combo has 32 different Build Numbers in its array. This will be correct as the Combo needs to be able to update earlier versions of the OS, and this includes Beta builds.
Out of interest I looked at the distribution file contained in the Delta update, and it has many more Build Numbers, so I wonder if Apple mixed the two up.
I inserted the Build Number of my Mac into the Build Number array, saved the Distribution file, repackaged the Combo folder. Clicked the new modified package and the Combo installed.
Click to expand...
This is very interesting and thanks for root causing. Makes me glad Apple QA is as good as you are at finding these bugs and making sure they're fixed.
 
Sad story but true, I have at least temporarily reverted back to 10.14.2.
Originally I thought 10.14.3 was all working good but then I started having BT problems with my keyboard and magic trackpad.
First they were intermittent but that quickly changed to totally unworkable.
Booted from a 10.14.2 cloned backup and all is good again.

MacPro 3,1
macOS Mojave, HFS partition.
 
that's odd. I had BT problems with 10.14.0 and 10.14.2 (even numbers) but with 10.14.1 and 10.14.3 (odd numbers), my BT has been working perfectly.
 
jbarley said:
Sad story but true, I have at least temporarily reverted back to 10.14.2.
Originally I thought 10.14.3 was all working good but then I started having BT problems with my keyboard and magic trackpad.
First they were intermittent but that quickly changed to totally unworkable.
Booted from a 10.14.2 cloned backup and all is good again.

MacPro 3,1
macOS Mojave, HFS partition.
Click to expand...

yukari said:
that's odd. I had BT problems with 10.14.0 and 10.14.2 (even numbers) but with 10.14.1 and 10.14.3 (odd numbers), my BT has been working perfectly.
Click to expand...

Have you guys tried resetting the BT module? Try that by holding down the Shift+Option keys and then clicking on the Bluetooth menu item to reveal the hidden Debug menu.
 
inarush said:
Have you guys tried resetting the BT module? Try that by holding down the Shift+Option keys and then clicking on the Bluetooth menu item to reveal the hidden Debug menu.
Click to expand...
Haven't had my morning coffee yet so bear with me here...
Just which "Bluetooth menu" are you referring to?
 
Macwinman has posted on Apple Releases MacOS Mojave 10.14.3

#97
Apple has re-released the combo updater with an updated distribution list of compatible builds -- now includes 18C54 so it will run on 10.14.2.

var buildNumbersArray = '18A384a,18A389,18A391,18A2063,18B45d,18B50c,18B57c,18B67a,18B73a,18B75,18B2084,18B2103,18B2107,18B3094,18C31g,18C38b,18C48a,18C52a,18C54,18D21c,18D32a,18D38a,18D39a,18D42,18D43'.split(',');
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back