VMWare Workstation Player on Azure VM for testing

VMWare Workstation Player on Azure VM for testing | Updated July 2021

I had a request to run VMWare Workstation Player on an Azure VM for some testing and labs. Challenge accepted!

Demo environment:

Azure VM Standard E4s_v4 Gen 1 running Windows 10 2004 Enterprise 

UPDATE: It works also for Windows 10 20H2 Enterprise

Installed VMWare Workstation Player 16.0 free for non-commercial use

Tried to spin up a VM, but I got an error for Hyper-V conflict.

to solve it:

Download: https://www.microsoft.com/en-us/download/confirmation.aspx?id=53337 or https://1drv.ms/u/s!AvpafHi49lqjgpsm8e07X6hXVUFKoA?e=XTMlR2

Extract the dgreadiness_v3.6.zip to a local folder and execute the following commands in a Windows Powershell with “Run as Admin” (ignore all error messages):

  1. .\DG_Readiness_Tool_v3.6.ps1 -enable
  2. Reboot
  3. .\DG_Readiness_Tool_v3.6.ps1 -disable
  4. Reboot
  5. bcdedit /deletevalue hypervisorlaunchtype
  6. bcdedit /set hypervisorlaunchtype off
  7. Don’t Reboot (if you reboot, you need to run all steps again).

Finally, the VMWare Workstation Player VM started and I managed to set up and run a Windows 10 VM.

 

UPDATE: It works also for Windows 10 20H2 Enterprise:

Share

8 comments

  1. Thank you for this walkthrough. I’ve tried to run VMware in an Azure VM earlier and failed multiple times. So reading this is great news and indeed it works for me!
    Thanks for sharing.

  2. sadly didnt work for me i tried every thing in several forums .
    azure vm win server datacenter 2016 hyper v windows 10 20h2

  3. This didnt work for me either. Trying to run a VM inside workstation pro on a Azure VM. Still getting the “workstation and HyperV aren’t compatible” message

  4. Hi,

    did you disabled the hyperv by running the below? (admin cmd and restart of course)
    execute .\DG_Readiness_Tool_v3.6.ps1 -disable
    execute bcdedit /deletevalue hypervisorlaunchtype
    execute bcdedit /set hypervisorlaunchtype off

    It seems that the hyperv is still enabled at your VM.

  5. Hello,

    I tried all the commands mentioned in your article and it still doesnt work. Have tried different version of VMware workstations like 12,14,15,5,5 and 16 pro with different OS offered by Azure like Windows N Pro, Windows 10 20H2 and Windows 2012/2016. It still gives the same error on workstation ad well as player.

    We can’t get into the BIOS of VM hosted on Azure. So, its very frustrating that after trying all the methods, its just not working out. Any suggestions would be helpful.

    Note : I am installing a VM with above mentioned OS.
    On that I am installing workstation and running these commands with reboot as suggested.
    Still NO LUCK. 🙁

    Regards

    1. Hi Vishwas Mehra,

      The problem is not at the Windows Version nor the VMware WS version. Maybe the problem is at the Azure VM Size.
      e.g. I was able to make it work at an E4s_v4 VM. It should work at the D_v3 VMs too, but many people told me that they work only at the E_v4 series.

      You can find what VMs have the “Nested Virtualization” feature and try them.

  6. I have plans to deploy vRA and vSphere lab on the Azure VM with VMware workstation. Is it possible to do so with a high end configuration VM.

    Server CPU Memory Storage
    vCenter Server(Tiny) 2 12 415
    ESXi host 8 24 150
    vRealize Lifecycle Manager 2 6 78
    VMware Identity Manager 8 16 100
    vRealize Automation 12 42 246

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.