WiFi: No Hardware Installed after Mojave upgrade

Oh you mean factory reset

My experience is the same on a late 2015 iMac. I tried the same things as you did and it does not work. I created a new user, and new network locations as well. No joy. My hardware is there and works when booting into Recovery. Applecare's solution was to roll back. Hopefully an update is forthcoming.

Mac Book Pro late 2013 16 gig memory I 7 processor. I have the same problem and did all the same reboots. I had the apple store clean sweep my hard drive and reload Mojave. Mojave ran fine until i did a time machine reload. I then had the same problem. I had to go back to the Apple Store and have them reload High Sierra. then I reloaded my time machine back up and All was good. I will not try Mojave again until Apple figures out what is wrong.

Once bitten, twice shy!

Frankly I would not even touch the 10.14.1 or 10.14.1000 ...

I am creating an external startup disk with Mojave on it (USB 32GB stick).

My plan is to boot from it, leaving my internal drive intact, so I can see if Mojave runs on my MBP.

If it does then I "might" try 10.14.1 if it ever shows up but I will keep my Time Machine B/U going as insurance.

Making a bootable drive is easy.

1. Download Mojave from App Store. When it goes into install mode just quit.

2. Mojave Installer will show up in your Applications Folder.

3. You have to make sure your external drive (USB or whatever) is formatted as APFS which can be done using Disk Utility (Applications: Utilities:Disk Utility).

4. Run Mojave Installer from within Applications.

5. Select "Show All Disks" and select your external drive (USB stick)

6. Install. It should take about 10 min or less.

I'll provide feedback when I am done.

Installed Mojave (and nothing else) on an external 32GB USB drive and set it up as the startup drive.

My MBP started fine, got WiFi, connected to the router and worked fine BUT response to movements is slow- maybe it was still configuring the user parameters. But overall it works.

I wonder if all these issues might have to do with the file system on older Macs.

In any case something for Apple Engineers to think about.

I had the same issue with my MBP mid 2012. I did and upgrade, clean install with a migrate during the process and finally a clean install and when it was stable I migrated my files. With all three I either had no ethernet/wifi, very, very slow or a flat gray screen with the login icons, which didn't allow me to log in. I finally just restored back to High Sierra. It works just fine that way.

1. Try the original command to rename (rather than remove) the file: sudo mv /etc/sysctl.conf /etc/sysctl.conf.bak

2. You can also try the -f flag with your rm command to see if it works: rm -rf /etc/sysctl.conf

3. One other option:

I have a 5K as well, tried reinstalling update - didn't help. Recommendation must be to reload from time machine. I had hoped that waiting to install would protect me a bit. One should not have to do a clean install - thats for windows users.

If you look back at a few post, in this thread, you may see the solution. It appears that the file sysctl.conf is the culprit. For me, renaming that file solved the problem. I don’t know how to copy and paste a link to a post, at least on my phone.

Regards,

Roy

Not being a Mac tech, just a user, I had to go to the apple store to have HS reinstalled. We tried reloading Mohave first. that worked until I did my time machine reload. I have no idea where to get HS other than there.

I too had all of the wifi and bluetooth issues after my first attempt to upgrade to Mojave 10.14. I then downgraded back to High Sierra after much cursing. I never had to use Safe Boot and do an Internet Recovery before.

I just ran terminal and found that sysctl.conf file. Mine was dated 2006. I will try the upgrade to 10.14.1 tonight and report back.

Thanks

I backed up my internal drive before wiping it (in addition to the time machine and offsite backups) and did a clean install (i.e. like new, no migration or upgrading the OS). It didn’t help.

It worked! The user is having to set everything up again (iCloud, etc., etc.) but she's online and using High Sierra.

So now we wait for Apple to figure this out, I guess.

This worked for me too! Just had to rename that file! Thanks !!!!