Tested with VMWare Fusion Version 11.5.7 (17130923) on macOS Mojave 10.14.6 (18G9323)
Edit the *.vmx
file to remove the lines specifying the bootcamp disk. Save the deleted text to a file *.vmx-add
. For example:
ide0:0.virtualSSD = 1
ide0:0.present = "TRUE"
ide0:0.fileName = "rdisk2.vmdk"
ide0:0.deviceType = "rawDisk"
Restart VMWare Fusion, and encrypt the machine and add a TPM. Exit VMWare Fusion.
Download and install https://github.com/RF3/VMwareVMX:
git clone https://github.com/RF3/VMwareVMX.git
virtualenv pyenv
. pyenv/bin/activate
pip install pycryptodome
mv 'Windows 10 x64.vmx' 'Windows 10 x64.vmx-old'
~/Documents/VMwareVMX/main.py -a 'Windows 10 x64.vmx-add' 'Windows 10 x64.vmx-old' 'Windows 10 x64.vmx-new'
mv 'Windows 10 x64.vmx-old' 'Windows 10 x64.vmx'
Open VMWare Fusion, and confirm it now works.
In 12.2, this may be simplified to just adding one parameter instead:
managedVM.autoAddVTPM = "software"
# also possibly useful?
uefi.secureBoot.enabled = "TRUE"
uefi.allowAuthBypass = "TRUE"
vvtd.enable = "TRUE"
windows.vbs.enabled = "TRUE"
vhv.enable = "TRUE"
How I fixed VMware file catalina fusion