All right! After you’re basically done with the virtual machine configuration, everything should work great. But things don’t go always as expected. When you switch on the machine, you’ll see a lovely screen with an error that points to “The CPU have been disabled by default. Power off or reset the virtual machine”. Here’s How to Fix The CPU has been disabled by the guest OS
While Windows computer isn’t the default system to install macOS. The important thing is, Apple doesn’t support installing macOS on non-Apple hardware and is neither willing to do. But that’s not the only one who does this. Perhaps, when we use the patch for VMware, that is because, unlike VirtualBox, VMware Workstation Player doesn’t support installing macOS by default. In this case, when you try to install macOS on VMware without the patch, you’ll end up without installing.
Since installing macOS, whatever version isn’t the supported way, there will be likely problems messing around. Whether you’ve an Intel or AMD processor, you’ll probably need to play the tricky steps. But if you’re installing Mojave on an AMD system, you’ll need to pull off a few more steps including the actual steps which are for both processors. This is a tiny change but really matters. How to Fix The CPU has been disabled by the guest OS
There are several reasons which might cause the problem. The first one is that you may have not configured the virtual machine for your AMD system. While AMD systems are different from Intel ones, we will need to use the different config key for setting up correctly. The other reason that the error can pop up is if you’ve installed the VMware or VirtualBox while the Hyper-v is installed.
While this problem usually happens when installing macOS on VMware, so we will take a look at How to Fix The CPU has been disabled by the guest OS
Change The VM Hardware Compatibility to 10.x
All the usual installing steps are important, but you need to perform some more steps in addition to them. The nice thing is, it’s all done from the vmx file. There are two ways you do get it done. The first way you could do it is from the VMware with the wizard. The other way you could do is from the vmx file. We’ll move with the easier one. This is simple as we have covered you with every step with shots. Here’s how to do it real quick. How to Fix The CPU has been disabled by the guest OS
Go ahead and navigate to the virtual machine files. Now right click on the .vmx file and select Open with and choose Notepad.
Open VMX with Notepad
When the file opened, change the version number to 10. It will change the virtual machine hardware compatibility to 10.
Change The VM Hardware Compatibility to 10
If you miss changing the hardware compatibility of the machine from VMware, you’ll likely encounter this problem.
Add The Config Key For The Virtual Machine (For AMD Systems Only)
Now without closing the .vmx file, copy the following code and paste it at the end of all lines. If you’ve the config key smc.version = 0 already there, you may remove it and paste this in place of it. It should look like this.
cpuid.0.eax = “0000:0000:0000:0000:0000:0000:0000:1011”
cpuid.0.ebx = “0111:0101:0110:1110:0110:0101:0100:0111”
cpuid.0.ecx = “0110:1100:0110:0101:0111:0100:0110:1110”
cpuid.0.edx = “0100:1001:0110:0101:0110:1110:0110:1001”
cpuid.1.eax = “0000:0000:0000:0001:0000:0110:0111:0001”
cpuid.1.ebx = “0000:0010:0000:0001:0000:1000:0000:0000”
cpuid.1.ecx = “1000:0010:1001:1000:0010:0010:0000:0011”
cpuid.1.edx = “0000:1111:1010:1011:1111:1011:1111:1111”
featureCompat.enable = “FALSE”
Insert Code
When you’re done with it, simply save it.
Save
And you’re all set! All there’s left to do is switch the machine on and proceed with the installation.
Power on the virtual machine
That’s all well and good. Everything should work
Gaffar
I was able to run the VM on 3950X Processor with the following VMX details :
.encoding = “windows-1252”
config.version = “8”
virtualHW.version = “10”
pciBridge0.present = “TRUE”
pciBridge4.present = “TRUE”
pciBridge4.virtualDev = “pcieRootPort”
pciBridge4.functions = “8”
pciBridge5.present = “TRUE”
pciBridge5.virtualDev = “pcieRootPort”
pciBridge5.functions = “8”
pciBridge6.present = “TRUE”
pciBridge6.virtualDev = “pcieRootPort”
pciBridge6.functions = “8”
pciBridge7.present = “TRUE”
pciBridge7.virtualDev = “pcieRootPort”
pciBridge7.functions = “8”
vmci0.present = “TRUE”
hpet0.present = “TRUE”
ich7m.present = “TRUE”
board-id.reflectHost = “TRUE”
displayName = “macOS Catalina”
guestOS = “darwin19-64”
nvram = “macOS Catalina.nvram”
virtualHW.productCompatibility = “hosted”
gui.exitOnCLIHLT = “FALSE”
powerType.powerOff = “soft”
powerType.powerOn = “soft”
powerType.suspend = “soft”
powerType.reset = “soft”
usb.vbluetooth.startConnected = “TRUE”
smc.present = “TRUE”
smbios.restrictSerialCharset = “TRUE”
firmware = “efi”
tools.syncTime = “FALSE”
sound.autoDetect = “TRUE”
sound.virtualDev = “hdaudio”
sound.fileName = “-1”
sound.present = “TRUE”
numvcpus = “8”
cpuid.coresPerSocket = “8”
memsize = “32000”
sata0.present = “TRUE”
sata0:0.fileName = “macOS Catalina.vmdk”
sata0:0.present = “TRUE”
sata0:1.deviceType = “cdrom-image”
sata0:1.fileName = “C:\Users\Leon\Downloads\macOS Catalina ISO by Geekrar\macOS Catalina ISO by Geekrar\macOS Catalina Final [Geekrar].iso”
sata0:1.present = “TRUE”
usb.present = “TRUE”
ehci.present = “TRUE”
usb_xhci.present = “TRUE”
ethernet0.connectionType = “nat”
ethernet0.addressType = “generated”
ethernet0.virtualDev = “e1000e”
ethernet0.present = “TRUE”
extendedConfigFile = “macOS Catalina.vmxf”
floppy0.present = “FALSE”
smc.version = “0”
vhv.enable = “TRUE”
numa.autosize.cookie = “80001”
numa.autosize.vcpu.maxPerVirtualNode = “8”
uuid.bios = “56 4d be 15 17 2a 61 bb-54 bc 19 ea 20 f5 a1 5f”
uuid.location = “56 4d be 15 17 2a 61 bb-54 bc 19 ea 20 f5 a1 5f”
sata0:0.redo = “”
pciBridge0.pciSlotNumber = “17”
pciBridge4.pciSlotNumber = “21”
pciBridge5.pciSlotNumber = “22”
pciBridge6.pciSlotNumber = “23”
pciBridge7.pciSlotNumber = “24”
usb.pciSlotNumber = “32”
ethernet0.pciSlotNumber = “160”
sound.pciSlotNumber = “33”
ehci.pciSlotNumber = “34”
usb_xhci.pciSlotNumber = “192”
vmci0.pciSlotNumber = “35”
sata0.pciSlotNumber = “36”
svga.vramSize = “134217728”
vmotion.checkpointFBSize = “134217728”
vmotion.checkpointSVGAPrimarySize = “268435456”
ethernet0.generatedAddress = “00:0c:29:f5:a1:5f”
ethernet0.generatedAddressOffset = “0”
vmci0.id = “552968543”
monitor.phys_bits_used = “40”
cleanShutdown = “TRUE”
softPowerOff = “FALSE”
usb_xhci:6.speed = “2”
usb_xhci:6.present = “TRUE”
usb_xhci:6.deviceType = “hub”
usb_xhci:6.port = “6”
usb_xhci:6.parent = “-1”
usb_xhci:7.speed = “4”
usb_xhci:7.present = “TRUE”
usb_xhci:7.deviceType = “hub”
usb_xhci:7.port = “7”
usb_xhci:7.parent = “-1”
toolsInstallManager.updateCounter = “4”
usb:1.speed = “2”
usb:1.present = “TRUE”
usb:1.deviceType = “hub”
usb:1.port = “1”
usb:1.parent = “-1”
usb_xhci:4.present = “TRUE”
usb_xhci:4.deviceType = “hid”
usb_xhci:4.port = “4”
usb_xhci:4.parent = “-1”
sata0:1.startConnected = “TRUE”
toolsInstallManager.lastInstallError = “21004”
tools.remindInstall = “TRUE”
cpuid.0.eax = “0000:0000:0000:0000:0000:0000:0000:1011”
cpuid.0.ebx = “0111:0101:0110:1110:0110:0101:0100:0111”
cpuid.0.ecx = “0110:1100:0110:0101:0111:0100:0110:1110”
cpuid.0.edx = “0100:1001:0110:0101:0110:1110:0110:1001”
cpuid.1.eax = “0000:0000:0000:0001:0000:0110:0111:0001”
cpuid.1.ebx = “0000:0010:0000:0001:0000:1000:0000:0000”
cpuid.1.ecx = “1000:0010:1001:1000:0010:0010:0000:0011”
cpuid.1.edx = “0000:1111:1010:1011:1111:1011:1111:1111”
featureCompat.enable = “FALSE”
Lou
Same here with a Ryzen 3800X: “Failed to start the virtual machine.”
Yujin
Mine also prompts “Failed to start Virtual Machine“
Ryzen 2600
Chanchana Sornsoontorn
This is exactly what happens to me. I use AMD Ryzen 7 3700X
Adam Joel Stepansky
Anyone figure this out for 15.5 with AMD? New error appears regarding feature cpuids
David Schlender
I had the same issue. Did you find a solution to this?
Angel
What/???
StigNerg
I have done all this steps. I still cant rund mac mojave, I use AMD ryzen 7, 2700
StigNerg
no.. mac Catalina
Gary Stewart
That’s a few us with amd CPUs following all the fixes and ending up with “Failed to start the virtual machine” any ideas?
Danijel Lukic
At first inserted:
smc.version = “0”
Getting the Message that Guest turned off CPU.
Then changed the Version from 16 to 10
Then added the following (Because i have an AMD CPU):
cpuid.0.eax = “0000:0000:0000:0000:0000:0000:0000:1011”
cpuid.0.ebx = “0111:0101:0110:1110:0110:0101:0100:0111”
cpuid.0.ecx = “0110:1100:0110:0101:0111:0100:0110:1110”
cpuid.0.edx = “0100:1001:0110:0101:0110:1110:0110:1001”
cpuid.1.eax = “0000:0000:0000:0001:0000:0110:0111:0001”
cpuid.1.ebx = “0000:0010:0000:0001:0000:1000:0000:0000”
cpuid.1.ecx = “1000:0010:1001:1000:0010:0010:0000:0011”
cpuid.1.edx = “0000:1111:1010:1011:1111:1011:1111:1111”
featureCompat.enable = “FALSE”
Now i get the following error:
Failed to start the virtual machine
bubba
Thanks for pointing this out!
Gary Stewart
“Failed to start the virtual machine.” error message for me as well, any ideas?
Fernando Suarez Ornani
“Failed to start the virtual machine.” (no more explanation). What can I do?
Regarding “feature cpuid.ss was absent” and the like, beware that the lines that you have to add have the wrong quotations. For example:
featureCompat.enable = “FALSE”
Should be:
featureCompat.enable = “FALSE”
Same goes for CPUID lines, although they wont give you errors.
SAURISH MONGA
Error while powering on : feature ‘cpuid.ds’ was absent, but must be present.
feature cpuid.ss was absent, but must be present
feature cpuid.intel was abset but must be present
module featurecompatlate power on failed
value (random unreadable text) for variable featurecompat.enable is not a valid boolean value
using value TRUE
failed to start virtual machine
this is the error i got from following this. Im using amd processor what should i do?
Ahmad Syarbini
Error while powering on : feature ‘cpuid.ds’ was absent, but must be present.
feature cpuid.ss was absent, but must be present
feature cpuid.intel was abset but must be present
module featurecompatlate power on failed
value (random unreadable text) for variable featurecompat.enable is not a valid boolean value
using value TRUE
failed to start virtual machine
this is the error i got from following this. Im using ryzen 7 2700. please help.
suy uy
I can install vmware tool after this step