Quick Guide to fix Error “This host supports Intel VT-x” in VMware Workstation Hello Everybody, Have you ever installed and used VMware virtual machine to work? If you have already used it, then it is inevitable that a frequent error occurs during the installation of VMware Workstation as below: This host supports Intel VT-x, but Intel VT-x is disabled. Intel VT-x might be disabled if it has been disabled in the BIOS / firmware settings or the host has not been power-cycled since changing this setting. (1) Verify that the BIOS / firmware settings enable Intel VT-x and disable 'trusted execution.' (2) Power-cycle the host if either of these BIOS / firmware settings have been changed. (3) Power-cycle the host if you have not done so since installing VMware Player. (4) Update the host's BIOS / firmware to the latest version. This host does not support "Intel EPT" hardware assisted MMU virtualization. This host does not support virtualizing real mode. The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor. Module 'CPUIDEarly' power on failed.Failed to start the virtual machine Normally by default, the VT-x function (which supports running virtual machines) is turned off or disabled by the manufacturer. When you install the VMware program and launch it, the computer will report the error as above. Today, QTit will give you a quick guide to help you fix this common error. Step 1: Restart your computer, access BIOS SETUP. Access to BIOS SETUP is different for each computer. You can see the access shortcuts on each model as below: Step 2: Access to the Virtualization function (usually located on the Security or Virtualization Support tab) + Intel (R) Virtualization Technology + Intel (R) VT-d Feature You will now see that the functions are in Disabled mode. Please Enabled them. By default, the Virtualization function is disabled by the manufacturer Select Enabled mode to enable Virtualization function in BIOS SETUP After customization is complete, press F10 to save your settings. Now try again on VMware to see if the error is gone!