Problems upgrading to macOS Mojave on MacBook Pro 2018

Well that’s just great Allan. Kind of like playing the lottery, uh? We all shell out the money and for some of us, we win, and others, we lose. Great business model - don’t you think? It’s completely unacceptable and after buying Apple products now for over 3 decades, it looks as though the High Sierra’s will be my last journey before dying of thIt’s in their Mohave.

We have one more day of the Weekend to get through, then by next week hopefully people will hear something more from apple. Typically in the past, when there are real genuine issues, Apple has been usually quick to get something out to people as a fix.

The only macs with the T2 chip are the iMac Pro and both the 13” and 15” 2018 touchbar MacBook Pros. The 2016 and 2017 touchbar MBPs have the T1. None of the base MBPs with function keys have nor will have these chips. It is for the touchbar, Touch ID, Apple Pay and the T2 also controls the NVMe SSDs as well.

I have a Late 2016 15” touchbar and I installed Mojave over my 10.13.6 installation. I did a regular upgrade proceeding as soon as I downloaded the Mojave.app installer from the Mac App Store.

If you or anyone has a problem installing Mojave or having it work normally on any 2016-2018 MBP then the problem is your specific machine or a conflict with software you have installed or if you modified something on the system that is causing a conflict. Maybe a Boot camp partition or something like this. No one should have a problem upgrading to Mojave on the latest macs.

I repeat Mojave IS NOT BROKEN!!!

Please open disk utility when booting the Mac by holding command+R. Then select the volume which should say “Macintosh HD” and click on First Aid. This should repair any errors you may have.

If you have FileVault turned on you will have to mount the SSD and enter your password to mount it.

Your confidence level in your statement is mind boggling.

This is not my first rodeo. I have done this and cleaned out my MBP etc etc. I have done updates to the Mac os many times and never have I been stumped as with Mojave.

Clean Install with erasure of SSD, you name it I tried it. Hours spent trying to do something that should be simple.

This is nuts

Yes, the same as picklebreath - except three times - all back to normal with 10.13.6 So please stop telling us that the problem lies with our machines. The problem is with Mohave and its ADVERSE EFFECTS on our machines. Plain and simple.

Not necessarly.

Your installation of software and documents on your machine is unique.

There is NO mass failures of installation of mojave out there only a handful.

Have you done the inbuilt hardware test ?

Is all the ram modules original apple ?

Robin, you have a valid point, and what you are saying is totally correct, when it comes to unique setups, installations, etc.

What I think you have overlooked here is, some of these people complaining, have erased their internal storage, be it SSD, or Fusion Drive, and still had the installation fail. Since I haven't personally gotten my hands on a newer Mac e.g. 2016+ MacBook / pro with the new ports, and chipsets, I really can't comment here. My best experience here would be to assess anyone having issues with a 2015, or older Mac having problems, simply because I don't have the hands on experience with the newer hardware. I forgot to mention last night that, another friend from my main online community also is part of Macadmins, I'm not really familiar with it, but he said there's been quite a few issues reported there as well. However, because they're more of a private community, I've been told Google is kept out of there, so search results don't really show anything.

There is one more method I would personally try, if I was having issues, but its's up to the individuals here to try, as it would be a bit time consuming based on specific setups. Note, this isn't limited to Mojave, either. The process of which I'm referring to is creating a master install to a drive, then cloning that install to the internal drive of the said Mac. This is how Apple ships the os on new Macs. They create a master install, and image it to the Macs at the manufacturing plant. Otherwise it would take to long to run the installer each time a new machine is produced.

Performed the suggested inbuilt Hardware Test - ”No Issues.” Checked RAM on Activity Monitor - 3.62/8.0. DVDGenie, perhaps some individuals hereon are sufficiently adventuresome to create a master install to a drive and then cloning. Bit I would ask, why on earth should the average Mac user have to go through this. I found your statement, “Google has been kept out...search results don’t really show up” quite compelling.

Maybe its something in the boot sector.

What I would suggest is to do a fresh install after having erased and reformatted the HD in correct type.

Then do an install using the option command R method this will do an internet install to latest OS.

If this does not work then make a genius appointment.

Ok good

The only caveat I would say on hardware test is if one of the ram modules is borderline.

It might show ok in that but could fail on OS install. ( I had exactly that on an iMac a few years ago)

Removing said modules fixed the problem

Perhaps an appointment with genius.

There is still no mass cries of foul out there on mojave install.

I am not equipped to try this however as you said like others I have wiped my SSD clean and proceeded with install.

On one occasion after skipping the part of install where you get to choose where to get your data to import ( my case TM) chose to import later I actually had Mojave installed. Having to go through process of setting up accounts etc.

Thought I was on my way. Proceeded to use Migration Assistant and all went for a crap.No activity from my NAS where the TM is. Tried booting to safe mode and reinstall Mojave and install locked up.

This was on my first attempt. The other 3 attempts where a straight upgrade including a clean install and choosing to use TM for data transfer during the install process.

All 4 times a clean install of High Sierra and TM data transfer during install worked the way its supposed to.

I am willing to accept that I am the one that has an issue but where to go from here. My MBP works like a champ under High Sierra so what is so different with Mojave that my machine goes for a crap. That is why I and others believe the issue lies with Mojave.

Heck I've been wrong before, but .....

To answer your first question, clone an install bypasses any issues the installer might have. 2, it usually saves time, especially when cloning an install where everything is setup.

To answer your other question about why the average Mac user should bother with this, because I grew up with an Apple community where your average Mac user, was also a professional of some kind, and they commonly knew how to take care of their computers and perform technical stuff as needed. Because of this, that's the genetical expectation I've developed for any Mac user now, and while every single person may not know a lot of tech stuff, it's a good thing to learn.

The only thing I would say is installing TM from NAS can be very time consuming.

Though a keep a NAS backup I have always done backup from a USB 3 HD.

Also when it asks what you want transferred from your account let it populate all the fields with files/apps/network settings before proceeding.

You will only get a partial restore if you do not wait until calculation has finished.

Yes I have have waited for it it to complete and wired to NAS and like I said works like a charm with High Sierra and worked like a charm when I went from Sierra to HS.

So where is the difference = Mojave

Robin,

One thing I'd like to add here, when I've used migration assistant in the past, I haven't been happy with the results.

There for, wile I do keep a TM backup on a usb drive, I manually copy things back to the new install. It can be a bit more time consuming, but the end result is usually more reliable, and the fact is, there isn't that much I really need to hunt and peck for.