I am evaluating a Windows 10 2004 VM on Azure but need to run my distro as a WSL2 instance for performance reasons. Git and grep are painful on WSL1.
I cannot get the Hyper-V features installed required to run WSL2. Running the following fails with the errors shown:
Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart
The term 'Install-WindowsFeature' is not recognized as the name of a cmdlet
The specified module 'servermanager' was not loaded because no valid module file was found in any module directory.
This is looking very much like nested virtualisation on an Azure VM is not going to work, in which case this project is dead in the water.
Am I missing something or is MS purposefully preventing developers from running the latest, and IMHO brilliant, features for WSL.