WSL: Error code: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED

Windows Version

Microsoft Windows [Version 10.0.22631.2050]

WSL Version

WSL version: 1.3.14.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

Kernel version: 5.15.90.3-1

Distro Version

Ubuntu-20.04

Other Software

No response

Repro Steps

It worked a few weeks ago so I installed Ubuntu 20.04 distro. But now i am getting `WSL2 is not supported with your current machine configuration. Please enable the “Virtual Machine Platform” optional component and ensure virtualization is enabled in the BIOS. Enable “Virtual Machine Platform” by running: wsl.exe --install --no-distribution For information please visit https://aka.ms/enablevirtualization Error code: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED Press any key to continue…

[process exited with code 4294967295 (0xffffffff)] You can now close this terminal with Ctrl+D, or press Enter to restart.`

After trying to start the distro within Windows Terminal 1.17.11461.0

Expected Behavior

Ubuntu WSL starts

Actual Behavior

`WSL2 is not supported with your current machine configuration. Please enable the “Virtual Machine Platform” optional component and ensure virtualization is enabled in the BIOS. Enable “Virtual Machine Platform” by running: wsl.exe --install --no-distribution For information please visit https://aka.ms/enablevirtualization Error code: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED Press any key to continue…

[process exited with code 4294967295 (0xffffffff)] You can now close this terminal with Ctrl+D, or press Enter to restart.`

Diagnostic Logs

I am running on a a pretty new AMD Ryzen 9 7940HS based ASUS ROG Zephyrus G14 (GA402XZ-NC021W).

SMT is enabled at BIOS, enable or disable Secure Boot does not seem to have any effect

I tried with no effect:

Enabled core isolation (memory integrity & Kernel mode enforced hardware stack)

Checked that file system is uncompressed

wsl --update

wsl --update wsl --shutdown wsl

netsh winsock reset

DISM /online /disable-feature /featurename:VirtualMachinePlatform /norestart DISM /online /disable-feature /featurename:Microsoft-Windows-Subsystem-Linux /norestart then reboot and DISM /online /enable-feature /featurename:VirtualMachinePlatform /norestart DISM /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /norestart

Reinstalling hyper visor plattform and virtual machine plattform through software control panel

Manually starting the LXSSMANAGER and validating that HV Host Service is running

Validated service logs (which were clean)

Created a new user at system… which ended up in same problems

Does anyone has an idea? Thank you!

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Reactions: 3
  • Comments: 22 (1 by maintainers)

Most upvoted comments

bcdedit /set hypervisorlaunchtype auto 之前使用模拟器 提示让我禁用 Hyper-V , 之后我进行了 Hyper-V 的重启 试过上面的所以的方法都没有效果,在最后 执行了 如上指令 在重启电脑 得到了解决 希望可以帮助到你

Same issue here. Not able to find any solutions online. Just randomly started happening, I haven’t changed anything.

check msconfig and ensure you are in normal startup mode, and your boot services aren’t cherry-picked

Had the same problem, could not start Docker Desktop (and curiously also not install WSL 2). Turning the Hyper-V Windows feature off and on again solved it for me. So:

  1. Control Panel > Programs > Turn Windows features on or off > Untick Hyper-V > Ok > Restart

  2. Control Panel > Programs > Turn Windows features on or off > Tick Hyper-V > Ok > Restart

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

Thank you!

The wrong drivers were installed in the motherboard. My problem fixed

/logs would be appreciated