Thanks, this sounds totally reasonable.
Unfortunately it does not seem to work with VMWare Fusion Pro 11.03.
We need to wait for an update.
Hey kinda curious to know how you were able to find the "EG7KH642X6" information specifically.....
To find the team id used for the signing of a kernel extension:
sudo sqlite3 /var/db/SystemPolicyConfiguration/KextPolicy
select * from kext_policy;
The ID column is the first column, and that's how I found EG7KH642X6
@mfat1317Weird, it's working for me on 11.03 standard—I'd be surprised if the kernel extensions had different team IDs. I've posted the method for finding it above (whatever it is, easier to make a typo as it's a randomish string).
My kexts have the same IDs you indicated, unfortunately I do not see vmmon within the com.vmware.kext.* group.
I do not know how to load it, I've tried
$ sudo kextload -b /Applications/VMware\ Fusion.app/Contents/Library/kexts/vmmon.kext
but it does not seem to load the kext.
I've completely uninstalled and reinstalled it 5 or more times, I've also followed the procedure to eliminate
after uninstalling, but nothing works.
I have no idea. I will try now to notarize the issue to apple even though I am under Mac osx 10.14.4, not using the 5 beta.
For me, I’ve tryed all the proposition and unable to start my VM, I got all the time the same message,
I don’t know what I can do more, but if someone can help me I appreciate. Please find below some information;
2019-06-11T22:31:50.679+01:00| vmx| I125: AppleXPC: Connecting to service com.vmware.VMMonHelper...
2019-06-11T22:31:50.679+01:00| host-32516| W115: AppleXPC: Failed to connect to service com.vmware.VMMonHelper
2019-06-11T22:31:50.679+01:00| vmx| W115: AppleXPC: Failed to connect to service com.vmware.VMMonHelper
2019-06-11T22:31:50.679+01:00| vmx| W115: Failed communicating with vmmon helper.
2019-06-11T22:31:50.679+01:00| vmx| I125: Msg_Post: Error
2019-06-11T22:31:50.679+01:00| vmx| I125: [msg.vmmonPosix.openFailed] Could not open /dev/vmmon: Broken pipe.
2019-06-11T22:31:50.679+01:00| vmx| I125+ Please make sure that the kernel module `vmmon' is loaded.
2019-06-11T22:31:50.679+01:00| vmx| I125: ----------------------------------------
2019-06-11T22:31:50.686+01:00| vmx| I130: Vigor_MessageQueue: event msg.vmmonPosix.openFailed (seq 6506) queued
2019-06-11T22:31:52.276+01:00| vmx| I125: Msg_Post: Error
2019-06-11T22:31:52.276+01:00| vmx| I125: [msg.vmmonPosix.initFailed] Failed to initialize monitor device.
2019-06-11T22:31:52.276+01:00| vmx| I125: ----------------------------------------
2019-06-11T22:31:52.277+01:00| vmx| I130: Vigor_MessageQueue: event msg.vmmonPosix.initFailed (seq 6507) queued
2019-06-11T22:31:53.027+01:00| vmx| I125: Module 'VMMon' initialization failed.
2019-06-11T22:31:53.028+01:00| vmx| I125: Services_Exit: Closed the services.
2019-06-11T22:31:53.030+01:00| vmx| I125: Vix: [mainDispatch.c:833]: VMAutomation_LateShutdown()
2019-06-11T22:31:53.030+01:00| vmx| I125: Vix: [mainDispatch.c:782]: VMAutomationCloseListenerSocket. Closing listener socket.
2019-06-11T22:31:53.033+01:00| vmx| I125: Flushing VMX VMDB connections
2019-06-11T22:31:53.033+01:00| vmx| I125: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#1/'
2019-06-11T22:31:53.033+01:00| vmx| I125: VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#1/' (0)
2019-06-11T22:31:53.034+01:00| vmx| I125: VigorTransport_ServerDestroy: server destroyed.
2019-06-11T22:31:53.034+01:00| vmx| I125: WQPoolFreePoll : pollIx = 2, signalHandle = 16
2019-06-11T22:31:53.034+01:00| vmx| I125: WQPoolFreePoll : pollIx = 1, signalHandle = 18
2019-06-11T22:31:53.041+01:00| vmx| W115: Failed to initialize VM.
I have the same issue on my Mac OS running Catalina, and VMWare Fusion 11.1.1. I have uploaded the zip bundle to dropbox link you mentioned just now, and set the hang/crash prior.
disabling csrutil fixed my broken pipe issue
I ran into this issue as a Mac Admin who deploys the profile. Our whitelist is correctly whitelisting the VMWare Fusion kext. However, I would get this same error. Only when I exempted myself from the whitelist, and then re-launched VMWare Fusion did the prompt for the blocked kext show up, and I was able to allow it. Very strange.
Great job! Now it works. Thanks
I have done a full uninstall and am still not getting the ability to allow this in Security section
Just to make sure:
- drag fusion to the trash
- empty trash
- reboot the machine
- empty trash
- install fusion
and make sure you are doing all this as an administrator, not regular, user account
Two remedies for restoring VMware Fusion 11.5.5 function within macOS Mojave 10.14.6.
Numerous attempts at deleting and restoring VMware Fusion 11.5.5 (16269456) with the latest security updates from Apple for Mojave 10.14.6 on an iMac 2017 did not remedy repeated VMware errors reporting broken /dev/vmmon kexts.
Two independent methods of restoring operation appears to work on my 2017 iMac. Each has implications for macOS security practice.
1: Eskimoke in message 13 of this thread suggested using ‘csrutil disable’ in macOS Mojave Recovery mode. An action that turns off macOS ‘System Integrity Protection’ and worked on my iMac.
2: The second involves a more lengthy reinstall of macOS 10.14.6 whilst retaining the macOS 'csrutil enable' function. It involves restoring macOS Mojave 10.14.6 from a cloned backup and then refusing the latest Apple Security Update 2020-004 10.14.6.
The Apple update that is offered and currently highlighted by a reference to the link at : https://support.apple.com/kb/HT201222 appears to be one that should be avoided for VMware 11.5.5 with Mojave 10.14.6
Restoring the Applications directory containing the latest VMware Fusion 11.5.5 worked as expected after denying the security update.
One symptom observed within macOS Mojave after installation of that Apple Security Update is the directory /Library/StagedExtensions/Library/Applications/Support/VMware/ VMware Fusion/Services/Contents/Library/kexts directory was deleted from my iMac. The very files that are reported missing during VMware use.