I just remembered something that you might want to check.

There was a similar problem reported and the root cause of that was improper permissions on the /private/var/db/KernelExtensionManagement folder

See the reply in this thread from jameslodberg:

https://communities.vmware.com/t5/VMware-Fusion-Discussions/VM-s-not-working-in-Fusion/m-p/2816692/h...