The validation process found problems on the server to which you want to install features, the features are not compatible with the current configuration of your server


VMware Workstation Pro is the industry standard for running multiple operating systems as virtual machines (VMs) on a single Linux or Windows PC to build, test, or demo software. IT professionals, developers, and businesses who build, test, or demo software for any device, platform, or cloud rely on Workstation Pro. VMware Workstation Pro allows you to run multiple virtual machines, OCI containers, and Kubernetes clusters at once on the same Windows or Linux PC. Create fully featured and securely isolated Linux and Windows VMs and other desktop servers, and cloud environments, complete with configurable virtual networking and network condition simulation, for use in code development, solution architecting, application testing, product demonstrations, and more. Below are some related guides: How to install Windows Server 2022 on VMware Workstation, how to extend a VM’s Hard Disk on VMware Workstation, Boot failure: Fix EFI network timeout on VMware Workstation, the virtual machine ran into a non-fatal problem as described below, we suggest that you take appropriate action to prevent the problem from recurring, how to solve VMware workstation .lck error, and how to add and remove a new virtual disk from a VM on VMware Workstation.

You may be unable to add the HyperV role onto your server that is running on VMware WorkStation. Kindly refer to the following error below. This error was prompted because the virtualize intel vt-x/ept or amd-v/rvi for the Server was not enabled.You may want to see these trobleshooting guides too: Windows failed to start, a recent hardware or software change might be the cause: VMware Status code 0xc000014c, the boot configuration data for your PC is missing or contains errors, Taking ownership of a VM failed: The virtual machine appears to be in use.

Virtualize Intel VT-x/EPT or AMD-V/RVI: Workstation Pro forces the virtual machine execution mode to VT-x/EPT or AMD-RVI. Physical Address Extension (PAE) mode must be enabled to use virtualized AMD-V/RVI. If the execution mode is not supported by the host system, virtualized VT-x/EPT or AMD/RVI will not available. If you migrate the virtual machine to another VMware product, virtualized VT-x/EPT or AMD-V/RVI might not be available. Hyper-V is a hypervisor-based virtualization technology and it uses the Windows hypervisor, which requires a physical processor with specific features. For hardware details, see System requirements for Hyper-V on Windows Server.


To resolve this issue, we will have to enable the Virtual Machine Processor Settings. The Virtual Machine must be turned off in order to perform this task. To do this, please follow the steps below.
– Right Click on the VM and select settings as shown below. This will open up the Virtual Machne Settings window


Alternatively, you can click on the Server, on the VM dashboard. Click on Edit virtual machine settings
– Click on Processors, and
– Ensure the “virtualize intel vt-x/ept or amd-v/rvi” button is checked.
– Click on Ok when done.


Note: IOMMU (Intel VT-D) provides direct memory access (DMA) protection. Kindly refer to this similar guide “Please enable the Virtual Machine Platform Windows Feature and ensure Virtualization is enabled in the BIOS: How to enable virtualization (VT-X) in VMWare workstation“.

Power up your VM, you should be able to select and install the role/feature (HyperV in my case) as shown below. Here is a similar error: Enable virtualization in Windows: How to fix VirtualBox Displaying only 32 bits Option.


I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.

Notify of

Inline Feedbacks
View all comments
Would love your thoughts, please comment.x