I wasn't able to to give permissions to the installer via the "allow" dialog due to corporate policy, so I cancelled out of the installer. I've since been given access to system preferences, but no matter what I do I can't get the installer to prompt me again. If I run the installer after following these instructions .. I was able to build and boot a win10 vm, which is great. However, I can't leave it in this mode. I re-enabled it and vmware is broken again. How should I proceed?
This solved may problem.
The kext file was not loaded successfully.
1. Open Fusion
2. Open terminal and input kextstat | grep vmware
There should be 4 kext running.
If not, please got System Preferences > Security & Privacy > General tab,
press the allow button if there it is.
This works perfectly fine for me. Thanks a lot!
had the same symptom on a brand new iMac install (still on High Sierra though) and with a newly registered Fusion 11.
all i did to solve it was to hammer that "Allow" button in the Security pane... for some reason it would not go away when clicking it once! Hammering it like 30 times in probably 10 to 15sec would take care of it and my VM would start even without having to restart Fusion or even the iMac.
"kextstat | grep vmware" returned nothing but i saw 4 lines in About this mac > System report > Software > Disabled Software.
These four lines are now gone and everything seems fine - till when though!?
Forgive my ignorance. I followed your suggestion, and it appears that I did not "allow" upon initial startup.
Would you be able to give me some additional information regarding removing the Fusion contents
Anyway, if the kext couldn't be load and you got no chance to press it. Please remove all Fusion contents and reinstall it.
Nix this request, I was missing the critical step of making sure that Fusion was exited/quit, in order to see the "allow" button. Thanks for all of the good info!
I saw the same issue. Security settings all look good in Settings. Only rebooting the mac did the trick. Ugh.
FWIW, I've been using VMware for years now, but ever since the jump to v10 things became unpleasant. I used to always get "could not find valid peer process" errors, and never really got to the bottom of it. As far as I could tell, VMware did not have proper integration w/ newer security models in High Sierra. I recently updated to Mojave & Fusion v11 and that problem seemed to go away, but now this problem! (worst part is... I *KNEW* updating was a bad idea). Meanwhile, I've been using VirtualBox for the last year for other purposes and find it to be a more stable platform. It's not as sophisticated as VMware w/ its host integration (particularly with USB ports), but it's never once stranded my VM and required me to reboot my mac or call customer service.
Fusion team - please work this out.
The problem is over.
get solved~ ^^
I am facing the same issue on Mojave
When i used this command
kextstat | grep vmware
then, there are only 2 instance running vmci and vmnet
Can you please help?
Same Problem here. Nothing of the above fixes does work for me.
I am no longer able to use fusion.
Same issue here, Macbook pro 2018 Mojave, 11.0.2.
I have this same issue and have followed most of the methods to attempt to get VMWare to work with Mojave...need some help if there are direct support methods please let me know.
I think I have this figured out. Every time I reboot my Mac and then startup my Win10 VM, I get the error: Could not open /dev/vmmon: Broken pipe. Then if I reboot, and try again, the problem goes away. So here is how I cope with this.
1. Boot my Mac and do a bunch of work, possibly for days.
2. Start up VMware and run into the issue. Doesn't matter if the VM is powered down or suspended.
3. Realize I forgot to run Step 4 since my last reboot.
4. Reboot the Mac
5. Run VMware and the Win10 VM comes up fine.
If I reboot the Mac, I'm effectively at Step 1 again. The key is that you have to hit the error, reboot, and try again. There is definitely an every-other-boot phenomenon with this issue. Meanwhile, my VirtualBox VMs keep chugging away not having any broken or cracked pipes.
This is not a great solution but if it allows functionality it will be ok temporarily. Thanks for the response.