Problems upgrading to macOS Mojave on MacBook Pro 2018

I was thinking back to earlier in the thread where references to Microsoft were made referring to the documents problem with the October update. Seems like they pulled the update preventing anymore problems and fixed it, plus other problems. It's still not re-released yet, as they are still fixing things they keep finding before re-releasing it. Sometimes it feels like Apple and Microsoft are switching places. In Apple's situation with Mojave, I'm sure if it was bad enough to recall, they would have. As it stands it looks like people with issues are just going to have to wait for the upgrade.

What a mistake to try Mojave! I so regret downloading it onto my MBP. Fortunately I had the forethought to do a Time Machine backup just before kicking off the install process. Whew! However I had all sorts of issues trying to get it into recovery mode. It just kept on rebooting no matter what keys I pressed. After an hour of trying it suddenly allowed me do do an internet recovery into safe mode. I then gratefully plugged in my Time Machine and it is happily chugging away - only 3hrs 20mins to go, it says. Fingers crossed it will boot back again into High Sierra.

You do wonder if anyone does any serious testing at Apple before releasing and hyping up OS upgrades.

I've been a lifelong Apple fan. Bought my first Apple II at Christmas 1978. I even worked for Apple for 10 years both as a reseller and an employee. My feeling is that they have lost sight of their values of quality and innovation. I'm seriously looking at a Microsoft Surface Pro for my next laptop. Gosh, wash my mouth out with soap and water! Has it really come to this?

The infamous file was not on my new 2018 MBP until I had used it for a week and installed a few new apps and done a very abbreviated Migration Assistant run from my 2015 MBP (I stopped Migration Assistant when I realized I couldn't pick and choose from my documents and apps--it just wanted to bring the whole kit and caboodle, which I did not want to do). By that time, the infamous file had shown up.

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.

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.

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.

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

Just a couple of things to clarify regarding the fix:

1) Make sure your spacing is correct when inserting into the Terminal “ls -l /etc/sysctl.conf,” a space between ls and -l and another space between l and /etc

2) The l is a lower case ell and not an upper case eye.