Hello, @Arunkumar Venkatesan ! We received your feedback and want to make sure that your question has been addressed.
How do I resolve Windows Subsystem for Linux (WSL) Error: 0x80370102 on an Azure VM?
You can find the complete troubleshooting checklist for this issue in the WSL troubleshooting documentation:
https://learn.microsoft.com/en-us/windows/wsl/troubleshooting#error-0x80370102-the-virtual-machine-could-not-be-started-because-a-required-feature-is-not-installed
In line with what @TP has said, there are two requirements that I would highlight from this list:
- If your machine is a VM, enable nested virtualization manually. Launch powershell with admin, and run the following command, replacing
<VMName>
with the name of the virtual machine on your host system (you can find the name in your Hyper-V Manager):
Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true
- If you are receiving this error on an Azure Virtual Machine, check to ensure that Trusted Launch is disabled. Nested Virtualization is not supported on Azure virtual machines.
Also confirm that the VM you have selected is capable of running nested virtualization:
https://learn.microsoft.com/en-us/azure/virtual-machines/acu
Complete troubleshooting list:
Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.
- Check the Hyper-V system requirements
- If your machine is a VM, enable nested virtualization manually. Launch powershell with admin, and run the following command, replacing
<VMName>
with the name of the virtual machine on your host system (you can find the name in your Hyper-V Manager):
Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true
- Please follow guidelines from your PC's manufacturer on how to enable virtualization. In general, this can involve using the system BIOS to ensure that these features are enabled on your CPU. Instructions for this process can vary from machine to machine, please see this article from Bleeping Computer for an example.
- Restart your machine after enabling the
Virtual Machine Platform
optional component.
- Make sure that the hypervisor launch is enabled in your boot configuration. You can validate this by running (elevated powershell):
bcdedit /enum | findstr -i hypervisorlaunchtype
If you see hypervisorlaunchtype Off
, then the hypervisor is disabled. To enable it run in an elevated powershell:
bcdedit /set hypervisorlaunchtype Auto
- Additionally, if you have 3rd party hypervisors installed (Such as VMware or VirtualBox) then please ensure you have these on the latest versions which can support HyperV (VMware 15.5.5+ and VirtualBox 6+) or are turned off.
- If you are receiving this error on an Azure Virtual Machine, check to ensure that Trusted Launch is disabled. Nested Virtualization is not supported on Azure virtual machines.
Learn more about how to Configure Nested Virtualization when running Hyper-V in a Virtual Machine.
I hope this has been helpful! Your feedback is important so please let us know that your issue has been addressed by accepting an answer.
If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!