A better solution posted in another thread on the same subject.
1 Click the Apple 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 Apple menu and select Restart....
1 person found this helpful
The solution proposed by Mohannad does not work For VMware Fusion Professional 11.0.3.
I suggest you to downgrade and do not do what proposed before.
Yes. This issue is most probably related to notarisation issues which macOS 10.14.5 beta 2 introduced.
All that the developer needs to do is to submit the kext to Apple for notarisation (even without the whole package including the product). After that, macOS will start accepting it in few minutes.
Here is a note on Apple's website (Notarizing Your App Before Distribution | Apple Developer Documentation
Beginning in macOS 10.14.5, all new or updated kernel extensions and all software from developers new to distributing with Developer ID must be notarized in order to run. In a future version of macOS, notarization will be required by default for all software.
For example, in my case, my machine is a managed office workstation. I do not have access to recovery mode due to company's policy.
Old kexts are still working fine. VMware Fusion Pro 11.0.2 works perfectly fine on the latest macOS beta 2 as its kext was built before March (all kexts updated after March require notarisation).
Actually I'm under 10.14.4