WSL 2 Error 0x80370102: Virtual Machine Platform or Virtualization Not Enabled

A user runs wsl or opens a WSL 2 distribution and sees:Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.The same code can appear when WSL installation fails. Ask what changed on the device recently, such as a new build, a firmware update or reset, a boot configuration change, or moving the Windows image into a virtual machine.

1. Work through the causes in this order and stop at the first one that is proven.Is this Windows a virtual machine? On a Hyper-V guest, nested virtualization must be exposed by the host. On an Azure VM, check whether Trusted Launch is enabled: Microsoft states nested virtualization is not supported on Azure VMs with Trusted Launch.Is Virtual Machine Platform disabled? If DISM reports the feature as disabled, this is the cause.Is the hypervisor switched off at boot? If the bcdedit line reads hypervisorlaunchtype Off, the hypervisor is disabled.Is virtualization off in firmware, or missing? If any Hyper-V requirement in systeminfo reads No, check hardware-assisted virtualization (Intel VT or AMD-V), Second Level Address Translation (SLAT) and Data Execution Prevention. WSL 2 needs SLAT; older CPUs such as the Intel Core 2 Duo cannot run it.Is a third-party hypervisor in the way? Microsoft asks for VMware 15.5.5 or later and VirtualBox 6 or later, which can run alongside Hyper-V, or for older versions to be turned off.

1. Work through the causes in this order and stop at the first one that is proven.Is this Windows a virtual machine?

2. On a Hyper-V guest, nested virtualization must be exposed by the host.

3. On an Azure VM, check whether Trusted Launch is enabled: Microsoft states nested virtualization is not supported on Azure VMs with Trusted Launch.Is Virtual Machine Platform disabled?

4. If DISM reports the feature as disabled, this is the cause.Is the hypervisor switched off at boot?

5. If the bcdedit line reads hypervisorlaunchtype Off, the hypervisor is disabled.Is virtualization off in firmware, or missing?

6. If any Hyper-V requirement in systeminfo reads No, check hardware-assisted virtualization (Intel VT or AMD-V), Second Level Address Translation (SLAT) and Data Execution Prevention.

7. WSL 2 needs SLAT; older CPUs such as the Intel Core 2 Duo cannot run it.Is a third-party hypervisor in the way?

8. Microsoft asks for VMware 15.5.5 or later and VirtualBox 6 or later, which can run alongside Hyper-V, or for older versions to be turned off.

• Record which cause it was, the before and after values, and who changed them.

• If the hypervisor had been switched off, find out what set it to Off.

• If a script, tool or policy did, it can switch it off again.

• Add the Virtual Machine Platform state and the hypervisorlaunchtype value to the build checks for developer images, and confirm that firmware baselines keep CPU virtualization on.

• The next safe decision after closure is whether other devices share the same image or firmware baseline and need the same check.

1. Local administrator rights on the affected Windows device.nAccess to the device's BitLocker recovery key before any boot configuration or firmware change.nFor a Hyper-V guest, administrator access to the Hyper-V host.

1. Repeat the DISM, bcdedit or systeminfo check for the item you changed. u2014 VirtualMachinePlatform enabled, hypervisorlaunchtype Auto, all requirements Yes or hypervisor detected. u2014 The changed item shows the expected value after restart.nRun wsl --list --verbose and start the affected distribution. u2014 A shell opens; VERSION shows 2. u2014 No 0x80370102 error.nCompare wsl --status with the saved output. u2014 Only the expected difference. u2014 No unplanned configuration change.