Network Initialization Failed

StephenB13

Junior Member
Hi everyone.

I haven't managed to find any threads with anyone having this same problem. I just downlaoded Parallels Lite to try out running an older version of MacOS to test some things. Whenever I launch a VM I immediately get a message saying: "Network Initialization Failed. Your virtual machine will continue working normally but will have no network connection."

This happens long before the OS loads (or in the case just now after trying again, even before the OS has been installed). I've tried all of the suggested network troubleshooting option but most don't apply (I'm not running windows and the problem seems to be in Parallels not in the OS itself), and none of the others work.

I have selected "shared networking." But I have also noticed that I don't even have the option to choose bridged, and when I look at my network options it doesn't even list any of my network hardware.

I'm at a loss for what to do. I've restarted my Mac, I've uninstalled and reinstalled Parallels. I've installed parallels tools. Again the problem seems to be in parallels itself (or something in my host OS), not in the OS that's being hosted.

I'v attached a few screenshots of what I'm seeing. Please let me know if you have any questions or need any further information.

I'm running MacOS High Sierra updated to the latest version (though obviously I haven't installed Mojave yet). on my host computer. It's a 2017 5k iMac. 24GB of RAM.

Any suggestions?
 

Attachments

  • Screenshot 2018-10-06 12.05.33.png
    Screenshot 2018-10-06 12.05.33.png
    167.2 KB · Views: 84
  • Screenshot 2018-10-06 12.12.22.png
    Screenshot 2018-10-06 12.12.22.png
    344.6 KB · Views: 78
Hey all, I have this issue also :)

macOS Big Sur
Version 11.0 Beta (20A5364e)

MacBook Pro (Retina, 13-inch, Early 2015)

Posting so I hopefully hear about a solution :D
 
Same problem here, latest Big Sur Beta, build 20A5364e... Submitted report ID 349602612.

What's interesting is that the problem seems to be common to both the VMware Fusion Tech Preview and Parallels 16.0.1, so it's clearly something that's recently changed in Big Sur. I actually decided to give Parallels a try because I was having this problem in VMware -- although honestly I'm liking what I'm seeing in Parallels so far, so it might be time to make the switch... although it might come down to whoever gets this problem solved first :D:)
 
It works with root user with Big Sur and Parallels 16
It seems to be fixed in VMware 12

Could you please advise how to run Parallels Desktop 16 as a root user? And where you found a solution for VMware 12 (I've searched their forum and can't find anything there regarding a workaround for this issue).
Thank you!
 
Hello, guys, as a workaround please run the following command in Terminal while Parallels Desktop was not started:

sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd

Please let us know the results.
 
Back
Top