SolvedWSL Error 0x80370102 The Virtual machine could not be started because a required feature is not installed ....

Following instructions on https://docs.microsoft.com/en-us/windows/wsl/wsl2-install#feedback with a fairly clean install of Build 18922

  • enabled The VMPlatform, reboot
  • enabled wsl, reboot
  • wsl set-default-verion 2
  • Install Ubuntu from store - https://aka.ms/wslstore as directed by wsl -l -v
  • Launch Ubuntu

Get the above error.

53 Answers

✔️Accepted Answer

ktmn
348

"The Virtual machine could not be started because a required feature is not installed"

How about make the message say which feature is not installed.

I got Virtualization enabled in BIOS, Windows Subsystems for Linux and Virtual Machine Platform enabled in Windows features, still get the message.
Do I need Hyper-V enabled? Do I need Windows Hypervisor Platform?

Edit: no, enabling these 2 didn't solve it either.

Edit 2: running bcdedit /set hypervisorlaunchtype auto start and reboot seems to have worked for me. So maybe I did need Hyper-V and/or Hypervisor Platform enabled, but it doesn't tell you anything useful.

Other Answers:

Hi @ktmn ,

Windows Subsystem for Linux or #WSL is for me and I'm aware this issue was closed. I got the following error after
Upgrading #WSL Windows Subsystem for #Linux on Windows 10 Professional with only bios #Virtualization and not SLAT.

"#0x80370102 the #virtual #machine could not be started because a required feature is not installed."

C:>wsl --set-default-version 1, Set default version 1, resolves the error on my desktop.

The above resolves the error and got me further. Now...

C:>ubunutu.exe
Prompts with new username and password.

WSL2_Error_0x80370102

I had a similar problem on when installing on my new system. I checked my BIOS @craigloewen-msft as mentioned. The first time I didn't find anything but after doing a bit more research I tried turning on SVM in the BIOS and it worked. (I also turned on the Windows Hypervisor setting in Windows Features)

(Advanced → CPU Configuration → SVM → Enable)

This is the case for AMD systems. Apparently it is different for Intel based systems.

Is virtualization enabled in your BIOS? That could be a quick fix.

We're tracking this issue over in #404 and we can help you troubleshoot there!

$ wsl --set-default-version 1

This one solved it for me.

Hi @ktmn ,

Windows Subsystem for Linux or #WSL is for me and I'm aware this issue was closed. I got the following error after
Upgrading #WSL Windows Subsystem for #Linux on Windows 10 Professional with only bios #Virtualization and not SLAT.

"#0x80370102 the #virtual #machine could not be started because a required feature is not installed."

C:>wsl --set-default-version 1, Set default version 1, resolves the error on my desktop.

The above resolves the error and got me further. Now...

C:>ubunutu.exe
Prompts with new username and password.

WSL2_Error_0x80370102

This one solved it for me.