Problems upgrading to macOS Mojave on MacBook Pro 2018

Which is why I recommend against time machine and prefer a manual restore. Yes I'll make a time machine backup, then then I put the stuff back manually. I've also found that problems from items gone bad are often resolved this way too.

Wow Ann/iFrog - it sure sounds as though the problem has been pinpointed and if the the Apple engineers haven’t taken note of this thread and our various posts from which to develop a patch, then I would wholeheartedly agree with Ann’s earlier statement as to the likelihood of their “official denial.” Really rather sad when you think about it.

Just thought I would post:

I did a clean install of Mojave to my 27" iMac yesterday (late 2015 model.)

I was having a minor issue where I couldn't figure out if it was due to the in place upgrade, or a bug in messages.

Anyway, I reinstalled from the recovery partition, I simply reformatted, and everything is good. Turns out I don't think the bug is Mojave specific, as I've seen it before in older versions of macOS.

The problem was: the "Notify me when my name is mentioned" checkbox wasn't staying selected past messages.app being quit, and re-opened.

I did want to mentioned to anyone here planning on doing a clean install, that Mojave takes about the same time as any other version of the macOS to install. I had my Time machine backup ready to go, and manually grabbed stuff from the correct locations that I needed to restore, and it was mostly done in about 2 to 3 hours. This morning, I've mainly spent the time reinstalling the apps from the App Store, and re-entering serials for my commercial products.

Beyond that, starting off clean for another year with Apple.

Also, wanted to mention to this with a Fusion Drive, as long as it's Apple supplied, you won't have any issues with Mojave, and APFS. My drive erased with no issues, and is identified in Disk Utility as an APFS Fusion Drive.

So, While I haven't found what exactly was causing the issue yet, I DO know, that, it wasn't my install of Mojave.

Good info iFrog. Yup, I agree at this point that it is likely not a DIRECT Mojave issue. That said however, after over 30 years of installing Mac OS upgrades, this issue has never surfaced before - so while perhaps not “direct,” something unique to Mojave may have picked up the OS ghosts of Halloween's past!

Done, not sure this will have any impact though.

It's kind of sad that there are zero updates from Apple that would provide official acknowledgement, guidlines, timelines etc.

At this point I don't even entertain to try it again, given the issues some faced/are facing and the potential hassle trying to revert back to HS in case things do go south.

10.14.1, is out today. Both my machines upgraded without a problem. Was curious if anyone here who hasn't upgraded yet is going to try it, and see if Apple resolved the issues with the initial release.

It's either one. You can either do the delta update though software update, or you can download the whole install app from the App Store. That's how macOS is now. There are also options to download the combo update from apple as you could with previous versions.

I did the update through software update, as I had recently did a clean install of 10.14 to two Macs.

Thanks for sharing. Really appreciated.

Sorry for being lazy, but without going through the thread, may I ask what symptoms you did encounter prior to 10.14.1?

I.e. install failed or install was successful but you had issues afterwards?

And lastly did you have the "bad file" on your machine?

Thanks a lot!

For me, Mojave has been a brick since the Beta process, and through the first release. "Brick meaning, very solid with minimal issues." I did not have sysctl.conf, and the ones who did have it, it was migrated through very old time machine backups. This means, once it's gone, it's gone unless a pice of software designed to create custom network settings ,s run, or someone creates it manually. For this thread, that simply means it won't come back, or won't be present unless like those who had it, came through an old back up, and system that hasn't been cleaned for several years.

10.14.1 doesn't show much difference over 10.14, but still feels rock solid. While it doesn't matter to me personally, has anyone here checked the release notes to see if Apple mentions issues people have been having?

Thanks again.

Sorry, I misinterpreted your statement "Both my machines upgraded without a problem.". I assumed you were in the same boat as I, i.e. you couldn't upgrade from HS to Mojave with the initial 10.14 release but succeeded with 10.14.1.

I will hold off until several folks that had issues with 10.14 were successful with 10.14.1 or once Apple officially confirms root cause and resolution.

Since this is my work computer, I am not in a position to take any risks.

Cheers!

That's OK, I completely understand. I brought up the update so people who had issues with the initial release could start looking into the notes about 10.14.1 to see if Apple had provided a statement, or notes regarding fixes that pertain to the particular issues being experienced.

Hopefully Apple will be able to determine what the universal issues are vs the isolated ones specific to the person's setup soon.

I was one f the early posters on this thread. I had been able initially to upgrade my 2.6GZ 15 inch 2018 MacBook Pro and my 2016 MacBook M5 but unable to upgrade my 2.6GZ 2012 15 inch MacBook Pro. I checked for an update. I was able to finally upgrade my 2012 MacBook Pro to 14.1 but I ran into the same old issues trying to upgrade it to 14.1. I tried three times and gave it. Apple needs to get this straight. This is ridiculous.

For those who might be on an enterprise environment (such as myself). I was able to get the 18 MBP's to update to Mojave by disabling the auto proxies and DNS Servers we had set in place and by, updating the OS via network that was not proxied as well. Was able to update to 10.14.1 with no issue either while at my office. I did not have that file that others have mentioned, but this is what helped my group of Macs to update. Anyone else experience anything similar?

I'm still on High Sierra, and even the Security Update 2018-002 10.13.6 failed to install. I'll try again, but I don't think this will work, and this is not a good sign regarding the Mojave 10.14.1 upgrade either.

(2018 MBP i9 with T2, safe boot, firmware password & FileVault)

Well....

MBP 2018, Touch bar, Filevault on

Tried with the latest update (14.1) with the same outcome. Installation proceeds as advertised until I reach the point where it gets stuck. Boot into safe mode, enter my login and password (Mojave background) and I'm in - everything looks peachy except that I'm in Safe mode. Reboot into normal mode, login successful, screen then changes back to Apple logo on black, sits at 80 percent and.....nothing. Just sits there - exactly what happened with 14.0

Sigh, Time Machine restore now in progress - I don't have the luxury of spending hours and hours trying to resolve the issue.

No Mojave for me it seems