VMware Communities
albatros99
Enthusiast
Enthusiast
Jump to solution

VMWare Fusion Could not open /dev/vmmon: Broken pipe OSX 10.15.5

On a new macbook pro, i have installed osx 10.15.5.

After this i have download the newest version of vmware fusion 11.5.5 and install it without problem

I have create a new virtual machine and by starting it, the error /dev/vmmon: Broken pipe

i was not able to open a sr by vmware for this product.

Who have a solution?

There is nothing blocking on the security tab

Thanks for help

cg

Reply
0 Kudos
1 Solution

Accepted Solutions
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

in this post on the community there is this solution:

Could not open /dev/vmmon: Broken pipe.

This solution works for cases where the "Allow" button does not appear in Security & Privacy > General:

Using Terminal, get the TeamIdentifier value from the VMWare Fusion version you're using (the % is the prompt, so omit that):

   % codesign -dv --verbose=4 /Applications/VMware\ Fusion.app

From the results of that command, find the "TeamIdentifier" value, for example:

   TeamIdentifier=EG7KH642X6

Write that down, and note this is case-sensitive.

Reboot your Mac into Recovery Mode (hold down Command + R at boot)

In Recovery Mode, open Terminal, then:

  % /usr/sbin/spctl kext-consent add EG7KH642X6

Reboot, and you should be good to go now.

----------------------------------------------------

or this solution:

https://www.techcrumble.net/2019/07/could-not-open-dev-vmmon-broken-pipe-vmware-fusion-macos-mojave-...

ARomeo

Blog: https://www.aleadmin.it/

View solution in original post

7 Replies
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

in this post on the community there is this solution:

Could not open /dev/vmmon: Broken pipe.

This solution works for cases where the "Allow" button does not appear in Security & Privacy > General:

Using Terminal, get the TeamIdentifier value from the VMWare Fusion version you're using (the % is the prompt, so omit that):

   % codesign -dv --verbose=4 /Applications/VMware\ Fusion.app

From the results of that command, find the "TeamIdentifier" value, for example:

   TeamIdentifier=EG7KH642X6

Write that down, and note this is case-sensitive.

Reboot your Mac into Recovery Mode (hold down Command + R at boot)

In Recovery Mode, open Terminal, then:

  % /usr/sbin/spctl kext-consent add EG7KH642X6

Reboot, and you should be good to go now.

----------------------------------------------------

or this solution:

https://www.techcrumble.net/2019/07/could-not-open-dev-vmmon-broken-pipe-vmware-fusion-macos-mojave-...

ARomeo

Blog: https://www.aleadmin.it/
albatros99
Enthusiast
Enthusiast
Jump to solution

The correct first command is

% codesign -dv --verbose=4 “/Applications/VMware Fusion.app"

there is a blank in the name of the app, so that i must use up commatas "

Then all will be fine!

Thanks for help

Claude Greiner

Reply
0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

Great! I'm happy.

ARomeo

Blog: https://www.aleadmin.it/
Reply
0 Kudos
EagleInYokohama
Contributor
Contributor
Jump to solution

After rebooting Mac in Recovery mode, I saw -blash-3.2# in terminal.

I could not see % and could not accomplish %/usr/sbin/spctl kext-consent add EG7KH642X6.

May I ask the solution  for this  problem ?

Reply
0 Kudos
BG-0364
Contributor
Contributor
Jump to solution

I did not try this way to eliminate this vmmon, I used another one of Saber16, on the other hand I did not reactivate the SIP because the reactivation posed the same problem :

Detailed steps:

  1. From the Apple menu select Restart.
  2. As your Mac restarts, press and hold down the Command(⌘) + R keys immediately upon hearing the startup chime. Hold the keys until the Apple logo appears to get the computer in Recovery mode.
  3. The computer is now in Recovery mode. From the Apple menu select Utilities -> Terminal
  4. Run the command: csrutil disable
  5. From the Apple menu, select Restart.
  6. After the macOS is loaded, open terminal and type: sudo kextutil /Applications/VMware\ Fusion.app/Contents/Library/kexts/vmmon.kext/

After I use VMWare Fusion 11 without problem.

I do it with Mojave, I run actually with Catalina and it is good.

Saber16 recommends to activate the SIP, with me the vmmon problem reappeared.
It is to be tested:

  1. From the Apple menu, select Restart.
  2. As your Mac restarts, press and hold down the Command(⌘) + R keys immediately upon hearing the startup chime. Hold the keys until the Apple logo appears to get the computer in Recovery mode.
  3. The computer is now in Recovery mode. From the Apple menu select Utilities -> Terminal
  4. Run the command: csrutil enable
  5. From the Apple menu, select Restart.

 

Reply
0 Kudos
ColoradoMarmot
Champion
Champion
Jump to solution

If you have to disable boot security, there's something wrong with your OS setup.  That's not required, and shouldn't be done.  You need to troubleshoot the root cause.  Some possibilities include installing UNIX level tools, setting a root password, or not installing and running as an administrator.

Reply
0 Kudos
BG-0364
Contributor
Contributor
Jump to solution

Thank you for your advice.

It is true that there is a problem. VM Fusion 11 was working very well and it is, first, on the advice of Apple support, the use of SOS disks, and then security updates that caused this bug.😡
I searched and couldn't find anything else but this ugly thing to stop being annoyed.
This bad joke cost me a lot of time by updating the Os (<cmd><r>), by copying from a clone.
As for using Unix tools, it is not within my possibilities.😢
I did an update from Mojave to Catalina but I didn't try to put the SIP back.

Reply
0 Kudos