Fusion 10.0 on macOS 10.13 -- Cannot find a valid peer process to connect to and Network settings greyed out

[bscully]

Hi,

Thanks for taking the time to read this.

Although I wish there was an was easy fix (I've tired a bunch in this forum and elsewehere), with a fresh install of macOS 10:13 followed by Fusion 10.0 yields new and existing VMs with the error:  Cannot find a valid peer process to connect to.  I've also noticed that the Network settings are greyed out.

and

FYI, I've created a case with Support, escalated the case, but no resolution.  I've tried tried adjusting the extended attributes, creating new users, multiple uninstalls (manual and assisted with cleaners), reboots, power offs, etc.

If there are others out there, I feel your pain.

Bill

[louistaljaard]

After doing all of the above I clicked that Allow button under System Prefs -> Security & Privacy a few more times (it wouldn't disappear even if I clicked it) and suddenly it started to work for me. I can now start my VM's just fine. Go figure. VMWare should issue a slicker fix for this, at the moment it's just luck if you get it to work.

[louistaljaard]

I didn't do these steps in the end, it just randomly started working for me (just posted more details, see my previous post).

[bscully]

I hear ya, but I was desperate and didn't like the idea of a newly-minted install of High Sierra with 2 obsolete versions of Fusions, a new version of Fusion, remnants scattered who knows where, and having to disable run my Mac with SIP disabled under the promise that Support would get back to me.  I'm much happier with 2 fresh installs -- macOS and Fusion -- and moving on!

Disabling SIP is still an option, if you have to get up and running.  I couldn't wait any longer.

Best of luck.

[bscully]

Guys, in full disclosure and I was not aware of this, I was in the process of enabling TFTP on my Mac and noticed that csrutil was disabled.  So, I enabled it and after a reboot and then running Fusion 10, for the very first time I was prompted to allow access in Security & Privacy.  I guess disabling csrutil with the previous install must have carried over.  I don't think having it disabled this time made a difference (fresh OS and Fusion install), but I just wanted to be clear about the whole not getting the Security & Privacy prompt-thing.  Everything still works, thankfully.

[MPoxon]

I am actually considering the same on mine so good to hear that a clean install is known to fix the issue. May I ask when you did a clean install which file system did you end up going with the new APFS or HFS+

[MPoxon]

I have been running my Mac with SIP disabled for a week or so which gets Fusion up and running. I have recently installed the latest update of macOS 10.13 (17A405) and disabled SIP. This has worked for me in resolving the issue.

[ShawnBakhtiar]

Basically same thing.
Clean out of the box mini running OS X 10.13. Installed VMWare and got the:

System Extension Blocked

A program tried to load new system extension(s) signed by VMware, Inc.. If you want to enable these extensions, open Security & Privacy System Preferences.

Which is documented here as KB 2151770:https://kb.vmware.com/s/article/2151770

VMware Knowledge Base

Following those instructions did not help at all. No matter how many times I clicked the allow button nothing happened. I tried deleting and re-installing as well. This did not solve the problem.

The only way I was able to get it to work was booting into recovery mode, launching the terminal, execute the command "csrutil disable" and rebooting.

Once I did that, I was able to launch the Windows 10 Virtual Machine which started installing Windows 10.

[YukinoriSagara]

I encountered the similar problem after I updated macOS High Sierra to 10.13.3. My VMware version is VMware Fusion 10 Pro 10.1.1 (7520154).

In my case, no notification message found in 'System Preferences -> Security & Privacy', so I could not push the 'Allow' button.

I could fixed my environment with the following steps. Do not need to disable SIP.

1. To check the VMware Developer ID, run the following command in Terminal
   $ sqlite3 /private/var/db/SystemPolicyConfiguration/KextPolicy '.dump kext_policy'
   PRAGMA foreign_keys=OFF;
   BEGIN TRANSACTION;
   CREATE TABLE kext_policy ( team_id TEXT, bundle_id TEXT, allowed BOOLEAN, developer_name TEXT, flags INTEGER, PRIMARY KEY (team_id, bundle_id) );
   INSERT INTO kext_policy VALUES('EG7KH642X6','com.vmware.kext.vmci',1,'VMware, Inc.',1);
   INSERT INTO kext_policy VALUES('EG7KH642X6','com.vmware.kext.vmnet',1,'VMware, Inc.',1);
   INSERT INTO kext_policy VALUES('EG7KH642X6','com.vmware.kext.vmx86',1,'VMware, Inc.',1);
   INSERT INTO kext_policy VALUES('EG7KH642X6','com.vmware.kext.vmioplug.17.1.3',1,'VMware, Inc.',1);
   COMMIT;
   
   'EG7KH642X6' is the ID.
2. Shut down the macOS, and enter in Recovery mode
3. Open the Terminal, and run the following command
   $ spctl kext-consent add EG7KH642X6
4. Exit Recovery mode, and reboot the macOS

After the steps above, you should be able to access the disabled feature again.

[gillinator]

THANK YOU for a solution for this issue that works and doesn't require a clean OS install! Thank you so much, it worked like a charm, even with Fusion 8.5 on High Sierra.

[DaveMesser]

Let me add my thanks. I encountered this same problem with the latest versions of MacOS and Fusion. This simple procedure worked like a charm to clear the obstacle.