New installation of Vmware fusion 11 pro on macos Mojave Could not open /dev/vmmon: Broken pipe

[jp4tey]

Why is this happening on a an upgrade to the lates version on the latest version of Macos....

Any clues

I am getting fed up with these sort of issues with VMware when Parallels works perfectly...

????

[1200MTS]

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.

[healthmanuk]

here is my diagnostics attached - can you please enlighten me with the resolution please sir

[healthmanuk]

please help based on this diagnostic attached

[SummerWolf]

Thanks.

The problem is over.

get solved~ ^^

[prazapati]

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?

[signsi67]

Same Problem here. Nothing of the above fixes does work for me.

I am no longer able to use fusion.

[carlsuetw]

Same issue here, Macbook pro 2018 Mojave, 11.0.2.

[cachaulo]

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.

[1200MTS]

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.

[cachaulo]

This is not a great solution but if it allows functionality it will be ok temporarily. Thanks for the response.

[jmadd_mac]

For me this solved my issue. Installing on a remote mac with Apple Remote Desktop the clicks would not work until I used an actual mouse and keyboard.

[iiseppi]

I have this problem also in my Mac Mini. In Macbook Pro Fusion works normally, but in mini I cannot launch the vm.

Parallels Desktop 14 works in mini normally.

[andyfuchs]

Same here, Macbook pro 2018 Mojave, 11.0.2.

Is there a VMWare uninstaller?

[umlkkleiner]

Hi, I just started having this same issue yesterday.  Fusion 11.0.3 working fine until then.  When I start a VM I get this /dev/vmmon related error.  I would like to know how to completely uninstall Fusion as I did remove the application and what I think are associated files then reinstalled, but still same issue.  Running macOS 10.14.4

kextstat | grep vm shows no VMWARE modules loaded

other errors :

bash-3.2# kextutil -print-diagnostics /Applications/VMware\ Fusion.app/Contents/Library/kexts/vmmon.kext/

Kext rejected due to system policy: <OSKext 0x7fac60e11200 [0x7fff9a4118f0]> { URL = "file:///Library/StagedExtensions/Applications/VMware%20Fusion.app/Contents/Library/kexts/vmmon.kext/", ID = "com.vmware.kext.vmx86" }

Diagnostics for /Applications/VMware Fusion.app/Contents/Library/kexts/vmmon.kext:

bash-3.2# kextload /Applications/VMware\ Fusion.app/Contents/Library/kexts/vmmon.kext/ -v

Requesting load of /Applications/VMware Fusion.app/Contents/Library/kexts/vmmon.kext.

/Applications/VMware Fusion.app/Contents/Library/kexts/vmmon.kext failed to load - (libkern/kext) system policy prevents loading; check the system/kernel logs for errors or try kextutil(8).

[audenmahk]

Same issue here -- happened all of a sudden.

There is no mention of Fusion not being able to run something in the Security system preferences pane, and have tried all the other recommendations in this thread.

Very frustrating.

[Technogeezer]

By any chance are your Macs being managed by your employer?

I ask because not too long ago I had a situation where USB devices on the host weren't visible to a Fusion VM. Digging into the error messages, we found that the Fusion USB kexts would not load with a message similar to what you are seeing - could not load because of system policy.

All the usual settings checked out fine.

It turns out that the root cause was that my employer deployed a kext whitelist profile (visible through System Preferences > Profiles ) that failed to whitelist the Fusion kexts.

[matthewberryman]

Same problem here, have uninstalled VMWare Fusion and reinstalled but no prompt to authorise the kernel extensions. Trying to load from the command line also fails. The advice from Zhaokaiy if run would disable all system integrity protection checks, e.g. code injection, protection of system paths like /bin , etc. so I would strongly avoid that from a security perspective. It's better to leave everything in place but to whitelist kernel extensions from VMware only (effectively, the same as pressing "allow" in system preferences for VMware each time... if you get the allow prompt). In full, the steps are:

(

1. Click the  menu.
2. Select Restart...
3. Hold down Command-R to boot into the Recovery System.
4. Click the Utilities menu and select Terminal.
5. Type /usr/sbin/spctl kext-consent add EG7KH642X6 and press return.
6. Close the Terminal app.
7. Click the  menu and select Restart....

)

[audenmahk]

That did the trick for me -- you're a hero!

[billearl]

I second the emotion.  Worked for me too, with SIP enabled.

[dtertius]

Works for me too. Tks