Problems upgrading to macOS Mojave on MacBook Pro 2018

I downloaded the package using my normal WiFi, and while installing it on my MacBook Pro 2018, I connected it using my iPhone’s internet. I don’t think it took much data. Plus I used the same package that I downloaded in my Pro to install Mojave in my MacBook Air, so the installation package was not specifically made for my particular Pro.

dmauch: I have some instructions here for you to do some investigation on that file.

1. In Finder from the Go menu: select Go to Folder

2. In the box type /etc

3.click OK

4. In the folder locate the file you renamed that was sysctl.conf

5. Open the file with TextEdit

6. If need be, drag the file to your Desktop, you may be prompted to enter your administer password for permission to move the file.

Look for anything regarding networking in that file. Since it's not on any of my stock installs that Apple does by default, it sounds very strange, and possibly like it shouldn't exist.

I would look at the file myself, but wasn't sure if you knew how to share files, either with google drive, or dropbox.

FINALLY!! The following enabled me to successfully upgrade to Mojave (10.14.1) from High Sierra and resolved all issues on my 2017 27” iMac (no WIFI hardware found, sluggish, lag, spinning beachball).

If you can log in (even if slow), or you're still on High Sierra, and have not yet upgraded, follow these instructions:

1. Start the Terminal app from Applications/Utilities

2. Check if the file exists, by typing

ls -l /etc/sysctl.conf

If this returns a result like the following, then the file exists. If it does not, then your issues are caused by something else

-rw-r--r-- 1 root wheel 136 24 Nov 2013 /etc/sysctl.conf

3. Rename the file by typing:

sudo mv /etc/sysctl.conf /etc/sysctl.conf.ba

(You’ll be promoted for your password; type in you password)

4. Restart your computer, and you should be all set, or if you've rolled back to High Sierra, you should be good to attempt the upgrade to Mohave again.

Thanks to dmauch for posting/finding the fix!

OK, I finally decided to give 10.14.1 a try on my 2018 13" MBP with Touch Bar.

I actually wanted to wait until Apple officially addresses this but since I wasn't even able to apply the latest security patch for 10.13.6, I did more research and found that for some on company Macs the Proxy settings mentioned here earlier might be the culprit.

Disabled "Auto Proxy Discovery" and the security patch went through, so I decided to try the Mojave upgrade as well.

Everything went really smooth with the upgrade itself, and so far after a few hours everything seems to work fine.

No issues at all but I will keep an eye on it and post an update here a little later after using it for a few days at work.

See above:

Exact same symptom when connected to corporate network (AD)

At least I appear to have narrowed it down to something to do with FileVault.

Rolling back to High Sierra now, Security Policies dictate that FileVault must be switched on.

Digging a bit further, I realised that FileVault is probably being enforced by McAfee EPO (don't ask), since I get the 'deferred enablement' message when checking via 'sudo fdesetup status' - going to try to disable that and then install again.

Hi,

Had the same problem, but for me it worked by

• removing all DNS search domains
• untick the automatic proxy configuration

for the Wifi adapter.

good luck.

Try my solution of using a wired connection and turning the WiFi off, it should work. The installer is not able to connect to the Apple Servers using WiFi. But it is using USB tethering.

GoolamZA: check out this thread: Issue while installing Mojave

They recommend disabling FileVault to do the upgrade. You can then re-enable it.

Reset of SMC worked for me as well.

https://support.apple.com/nl-be/HT201295

I found this other thread where resetting the SMC was suggested:

https://discussions.apple.com/thread/8551923?answerId=33919786022#33919786022

That fixed it for me - after resetting the SMC and running the installer again it successfully installed and I didn't get the error message again.

Suggestions here have included SMC reset, starting in Safe Mode to clear caches etc, but I would also boot into Recovery (Cmd+R), go into disk utility and run disk First Aid on the hard disk, maybe more than once for good measure.

Another finger pointing at the T2 chip. I get the "An error occurred installing macOS" failure early on in the Mojave upgrade process. In the console I found several log lines such as the following:

Operations failed with error: Error Domain=BOSErrorDomain Code=204 "An error occurred during preflight." UserInfo={NSLocalizedDescription=An error occurred during preflight., NSUnderlyingError=0x7f9102a7b900 {Error Domain=BridgeOSSoftwareUpdateError Code=25 "[/BuildRoot/Library/Caches/com.apple.xbs/Sources/BridgeOSSoftwareUpdateControl ler/BridgeOSSoftwareUpdateController-16.70.3/bridgeOSUpdateProxy/BridgeOSUpdateF irmwareUpdateInfo.m:77][_get_SEPersonalizationInfo_framework] SE not ready: state == 3" UserInfo={NSLocalizedDescription=[/BuildRoot/Library/Caches/com.apple.xbs/Sourc es/BridgeOSSoftwareUpdateController/BridgeOSSoftwareUpdateController-16.70.3/bri dgeOSUpdateProxy/BridgeOSUpdateFirmwareUpdateInfo.m:77][_get_SEPersonalizationIn fo_framework] SE not ready: state == 3}}}

BridgeOS is related to the T2 chip AFAIK. I am having some other odd issues (Messages taking 1-3 minutes to start up, and the Wallet and Apple Pay Preference pane failing to load and work correctly) which also may have T2 related causes... Not sure if it's a hardware issue or software bugs around the new security chip or what....

T2 chip is the problem, I have just spoken to an engineer from Apple who confirmed my suspicions. They are now aware of the issue, I am just going to wait until a fix is issued. They have asked me to run some tests which I will do tomorrow. Like most I have tried everything on this forum, however I should have realised earlier that if you cannot install a fresh copy of High Sierra from recovery mode then you are not going to have much luck with Mojave. It had to be something to do with an MBP 2018. Wasted a couple of days..oh well.

I wanted to post an update, I found a problem with the new App Store yesterday, and while it's not guaranteed to affect everyone, here is what happened, and what I did to fix it.

I'm posting this here because the problem seems to have come from upgrading, so if people here do manage to upgrade, watch out for this issue.

The Problem

App Store doesn't see any updates, even though they are available.

Solution:

Use an uninstall app such as AppCleaner, App Delete, or iTrash

Drag the App Store icon to the uninstaller app Icon, or select App Store with the uninstall app's search function.

Let the uninstaller app find and display the list of all associated files.

From that list, uncheck App Store

uncheck /Library/Application Support/AppStore

everything else is either user specific settings, or caches, so they can be deleted.

After deleting, empty trash, and reboot the Mac.

On restart, open the App Store, and log back in, and you should be good to go.

Hope this helps someone, and it's the only major issue I have encountered since the upgrade. Though in the past, it seems like damaged App Store cache and settings can happen from time to time.

Hopefully this will save someone time from a clean install just by resetting the problem apps.

Quote: "According to the providers we contacted, users looking to upgrade to Mojave should back up data in entirety using Time Machine, then attempt to install Mojave. If the installation fails, users should boot to the restore partition, by holding down Command-R on startup.

Following the boot to the restore partition, users should format the drive using Disk Utility prior to installation, and connect to a wired network to install the Mojave system software rather than connect to Wi-Fi. Following successful installation, data can be moved to the volume using the Migration Assistant in the Utilities folder."

From an article at AI: Some 2018 MacBook Pro owners are running into errors installing macOS Mojave

No, I'm sure as h3ll not going to wipe my boot volume just to install a system upgrade. I want Apple to release an installer "that just works".