How to solve Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED

Question

How to solve Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED

Benjamin Barinka 40

Hello,

after some while i tried to start my already installed wsl based Ubuntu 20.04 and it crashes with:

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...

It ran a few weeks ago without any problems. I am owner of a pretty new AMD Ryzen 9 7940HS based Asus Rog G14 laptop (ASUS ROG Zephyrus G14 (GA402XZ-NC021W). SMT and Secure Boot are enabled at BIOS. Core isolution (memory integrity & Kernel mode enforced hardware stack) is enabled. Running on Windows 11:

PS C:\WINDOWS\system32> wsl -l Windows Subsystem for Linux Distributions: Ubuntu-20.04 (Default) PS C:\WINDOWS\system32> wsl -v WSL version: 1.3.14.0 Kernel version: 5.15.90.3-1 WSLg version: 1.0.55 MSRDC version: 1.2.4419 Direct3D version: 1.608.2-61064218 DXCore version: 10.0.25880.1000-230602-1350.main Windows version: 10.0.22631.2050 PS C:\WINDOWS\system32>

Already googled some hours and tried:

wsl --update

or

wsl --update
wsl --shutdown
wsl

already read

https://learn.microsoft.com/de-de/windows/wsl/troubleshooting

folders are uncompressed...

or

netsh winsock reset

or

DISM /online /disable-feature /featurename:VirtualMachinePlatform /norestart
DISM /online /disable-feature /featurename:Microsoft-Windows-Subsystem-Linux /norestart

reboot

DISM /online /enable-feature /featurename:VirtualMachinePlatform /norestart
DISM /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /norestart

or

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

or

manually starting the LXSSMANAGER and validating that HV Host Service is running....

and validated service logs (were no errors are inside)

or created a new user at system... which ended up in same problems

All without any help :(

Does anyone have an idea what i could try?

Thank you very much!

Best regards

Shankar Subramanian 10 Reputation points

2023-10-11T21:10:39.1633333+00:00

Same issue...
Maria Antonia Martorell March 10 Reputation points

2023-11-24T17:32:49.9833333+00:00

I have the same problem, were you able to solve it in the end? I still do not.
jafber 40 Reputation points

2023-12-04T20:34:32.9833333+00:00
I was going crazy with the same problem, but turning the Hyper-V Windows feature off and on again solved it for me. So:

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

Control Panel > Programs > Turn Windows features on or off > Tick Hyper-V > Ok > Restart
Rahul Ram 180 Reputation points

2024-04-04T18:26:50.2266667+00:00

Had the same issue this solved it for me.

Remember to restart after doing this step.
Alioune NDIONE 5 Reputation points

2024-08-06T21:41:13.8833333+00:00

Ca m'a sauvé la mise , Merci.
XOne T 0 Reputation points

2024-10-29T02:33:02.0633333+00:00

That's work for me.
Minh Vu 0 Reputation points

2024-11-02T07:57:33.8666667+00:00

for me, it was fixed when I turned this on
Rui Pedro Mendo Coelho 0 Reputation points

2024-12-04T17:01:21.42+00:00

TYSM RAHUL IT FINALLY WORKED !!!!
prathamesh patrawale 0 Reputation points

2025-04-22T23:44:14.8666667+00:00

its working fine its help me
prathamesh patrawale 0 Reputation points

2025-04-22T23:49:06.7933333+00:00

first i check hyper v which seen on and i use many methods and also restart laptop multiple times i decided to switch bios legacy (mbr) to uefi but i can acess bios password thank you you done lot of help me
Tony Sanginez 0 Reputation points

2025-05-22T21:44:54.3833333+00:00

This help me!
ricardo gonzalez 0 Reputation points

2025-06-07T11:32:29.53+00:00

I just had the same Issue, and the source was that on one recent update (That by the way Microsoft Removed Wiped Cleaned Dev Home without even asking me) and this removal left my already selected preference from "Hyper-V Manager" in settings:

Option "NUMA Spanning" (I blanked the checked box just for demonstration purposes) , it needs to be Selected/Checked , otherwise you'll experience problems with hyper-v, wsl, docker and docker desktop:

After that click Apply, and on the upper right corer in the Actions Pane select the "Stop Service" Option, wait for at least 10 seconds and then click on "Start Service" to restart it, and finally restart your system.

So just checking for this preference should fix the issue, and as other users stated another straight forward method is to just uncheck the windows feature "Hyper-V"

, because when it gets re enabled it will select the default preferences and "NUMA Spanning" gets selected/checked.

9 answers

Your answer

Shankar Subramanian 10 Reputation points

2023-10-11T21:10:39.1633333+00:00

Same issue...
Maria Antonia Martorell March 10 Reputation points

2023-11-24T17:32:49.9833333+00:00

I have the same problem, were you able to solve it in the end? I still do not.
jafber 40 Reputation points

2023-12-04T20:34:32.9833333+00:00

I was going crazy with the same problem, but turning the Hyper-V Windows feature off and on again solved it for me. So:

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

Control Panel > Programs > Turn Windows features on or off > Tick Hyper-V > Ok > Restart
Rahul Ram 180 Reputation points

2024-04-04T18:26:50.2266667+00:00

Had the same issue this solved it for me.

Remember to restart after doing this step.
Alioune NDIONE 5 Reputation points

2024-08-06T21:41:13.8833333+00:00

Ca m'a sauvé la mise , Merci.
XOne T 0 Reputation points

2024-10-29T02:33:02.0633333+00:00

That's work for me.
Minh Vu 0 Reputation points

2024-11-02T07:57:33.8666667+00:00

for me, it was fixed when I turned this on
Rui Pedro Mendo Coelho 0 Reputation points

2024-12-04T17:01:21.42+00:00

TYSM RAHUL IT FINALLY WORKED !!!!
prathamesh patrawale 0 Reputation points

2025-04-22T23:44:14.8666667+00:00

its working fine its help me
prathamesh patrawale 0 Reputation points

2025-04-22T23:49:06.7933333+00:00

first i check hyper v which seen on and i use many methods and also restart laptop multiple times i decided to switch bios legacy (mbr) to uefi but i can acess bios password thank you you done lot of help me
Tony Sanginez 0 Reputation points

2025-05-22T21:44:54.3833333+00:00

This help me!
ricardo gonzalez 0 Reputation points

2025-06-07T11:32:29.53+00:00

I just had the same Issue, and the source was that on one recent update (That by the way Microsoft Removed Wiped Cleaned Dev Home without even asking me) and this removal left my already selected preference from "Hyper-V Manager" in settings:

Option "NUMA Spanning" (I blanked the checked box just for demonstration purposes) , it needs to be Selected/Checked , otherwise you'll experience problems with hyper-v, wsl, docker and docker desktop:

After that click Apply, and on the upper right corer in the Actions Pane select the "Stop Service" Option, wait for at least 10 seconds and then click on "Start Service" to restart it, and finally restart your system.

So just checking for this preference should fix the issue, and as other users stated another straight forward method is to just uncheck the windows feature "Hyper-V"

, because when it gets re enabled it will select the default preferences and "NUMA Spanning" gets selected/checked.

Answer 1

Steve Watkins 60

This solved it for me,
from https://learn.microsoft.com/en-us/windows/wsl/troubleshooting#installation-issues

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

Steve Watkins 60 Reputation points

2024-02-02T22:10:20.9866667+00:00

Yikes my # comments got picked up by mardown!
Viktor Kovachev 0 Reputation points

2024-02-12T12:39:10.9+00:00

This fixed it for me, ty very much!
eljyw 10 Reputation points

2024-02-22T14:20:58.51+00:00

don't forget to reboot after setting the parameter
Junzhao HUANG (Ginger) 0 Reputation points

2024-03-06T06:21:35.11+00:00

it's good
（˙▽ ·） 0 Reputation points

2024-03-26T03:07:16.8366667+00:00

it works！thank you
Sergei Gridnevskii 0 Reputation points

2024-07-25T06:52:40.4466667+00:00

Does not work for me,

bcdedit /enum

The boot configuration data store could not be opened.

Access is denied.

I don't have admin access to PC, it is owned by organization.

The only solution is to reboot PC, but this is really annoying. Microsoft cannot solve this issue since 2020.
Tony Sanginez 0 Reputation points

2025-05-22T21:45:12.14+00:00

Thanks a lot! This help me

Answer 2

Kinstray 15

Thanks for your help. Reformatting it to make it easier to Copy/Paste.

This solved it for me too from https://learn.microsoft.com/en-us/windows/wsl/troubleshooting#installation-issues

You can validate this by running (elevated Powershell or Command Prompt):

bcdedit /enum | findstr -i hypervisorlaunchtype

If you see hypervisorlaunchtype Off, then the hypervisor is disabled.

To enable it run in an elevated Powershell or Command Prompt:

bcdedit /set hypervisorlaunchtype Auto

Kiervin SALO 0 Reputation points

2025-05-22T00:19:30.0033333+00:00

I did it and it works, Thank you.

Answer 3

Thierry Estrada 0

Hi, Just had this problem in a VM. Solved using command on host: Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true as suggested in https://learn.microsoft.com/en-us/windows/wsl/troubleshooting#installation-issues

Answer 4

#ELROY LIANG BO JUN# 0

Issue for me was Virtualization was disabled. I followed this article to enable it at BIOS. https://www.simplilearn.com/enable-virtualization-windows-10-article

Answer 5

Okechukwu Okafor 0

Boot into your BIOS and enable virtualization.

Share via

How to solve Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED

9 answers

Your answer