Error code: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED #10332

bebablub · 2023-07-25T16:32:55Z

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!

ghost · 2023-07-25T21:06:18Z

/logs would be appreciated

microsoft-github-policy-service · 2023-07-25T21:06:23Z

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!

bebablub · 2023-07-26T01:16:55Z

Hello,

thank you for reply. I have executed the script as administrator in a powershell and tried to start wsl within my terminal. Logs are attached

WslLogs-2023-07-26_03-10-04.zip

thx!

bebablub · 2023-07-26T21:24:16Z

Does anyone have an idea?.... :/ Otherwise will do a clean Windows install....

NeonWizard · 2023-11-06T01:01:32Z

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

AskAlice · 2023-11-16T20:08:34Z

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

NeonWizard · 2023-11-17T07:10:10Z

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 service aren't cherry-picked

You are literally a godsend. I was in selective startup for some reason, switching to normal startup fixed it.

snhok · 2023-11-17T15:36:22Z

For me, I had recently updated my bios and the Intel Virtualization Technology became disabled. After I reenabled it, WSL2 was working again.

AskAlice · 2023-11-17T23:46:45Z

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 service aren't cherry-picked

You are literally a godsend. I was in selective startup for some reason, switching to normal startup fixed it.

lol I would say the same to you. When you mentioned you weren't able to find any solutions having tried the ones above, I thought about what i changed when i migrated my windows install to a VM with gpu passthrouh on linux, and realized I disabled the hypervisor in startup settings. I thought it was weird that the windows bootloader UI looked like windows 7 and there was no automatic timer and I had to press enter every time I wanted to boot into a different bcdedit entry...

jafber · 2023-12-04T20:36:33Z

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:

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

prokopis3 · 2023-12-08T12:34:03Z

WslLogs-2023-07-26_03-10-04.zip
same problem here i just upload the logs file of our system
any thoughts

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!

sergiopvilar · 2023-12-10T13:11:24Z

Same issue here. I have everything enabled on the windows and on my BIOS as well. Not sure why I'm getting this since I had WSL 2 running a while ago on the same machine.

NeonWizard · 2023-12-11T19:07:40Z

Same issue here. I have everything enabled on the windows and on my BIOS as well. Not sure why I'm getting this since I had WSL 2 running a while ago on the same machine.

Did you give AskAlice's solution a try? If WSL gets in a bad state Windows apparently can automatically disable its bootup processes in msconfig. I think this happened to me when Docker Desktop had a really bad memory leak inside WSL2

yeremi01 · 2023-12-12T01:07:48Z

aqui esta mi solucion https://www.youtube.com/watch?v=QW2DgEzb3Vc

xiurenfuwo · 2024-01-15T01:46:06Z

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

Thanks, it effects.

prokopis3 · 2024-01-15T08:35:51Z

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

misft55 · 2024-01-19T06:45:01Z

Hello,
I don't know if your wsl --install issue was resolved, I will put this out there JIC.
My issue was resolved differently than prokopis3.
I was working on MacOS/VirtualBox Win 11install and in a "how to" related to Win11Vming in Windows Security I changed two Core Isolation options to off.

Memory Integrity
Kernel-mode Hardware-enforced Stack Protection

I turned them back on, restarted and Ubuntu fired right up.

Ubuntu 22.04.3 LTS (GNU/Linux 5.15.133.1-microsoft-standard-WSL2 x86_64)
wsl 2
Processor 11th Gen Intel(R) Core(TM) i3-1115G4 @ 3.00GHz 3.00 GHz
System type 64-bit operating system, x64-based processor
Edition Windows 11 Home
Version 23H2
OS build 22631.3007
Experience Windows Feature Experience Pack 1000.22681.1000.0

goodpersons · 2024-03-30T07:01:17Z

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

CalvinXu17 · 2024-07-19T09:29:14Z

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

This is useful!! Thanks bro.

microsoft-github-policy-service bot added the needs-author-feedback label Jul 25, 2023

microsoft-github-policy-service bot removed the needs-author-feedback label Jul 26, 2023

github-actions bot mentioned this issue Feb 2, 2024

After update HCS_E_HYPERV_NOT_INSTALLED #11117

Closed

2 tasks

ghoebenreich mentioned this issue Mar 27, 2024

Not able to switch to WSL2. Error code: Wsl/Service/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED #11384

Open

2 tasks

github-actions bot mentioned this issue Jul 12, 2024

WSL2 won't launch even after troubleshooting with Hyper-V #11775

Closed

github-actions bot mentioned this issue Sep 28, 2024

WSL not working after windows update (Windows 10 Pro): WslRegisterDistribution failed with error: 0x80370102 #12092

Closed

2 tasks

github-actions bot mentioned this issue Oct 14, 2024

WSL fails to start with HCS_E_HYPERV_NOT_INSTALLED error after Windows 11 in-place upgrade despite hyper-v being on #12165

Open

2 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error code: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED #10332

Error code: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED #10332

bebablub commented Jul 25, 2023

ghost commented Jul 25, 2023

microsoft-github-policy-service bot commented Jul 25, 2023

bebablub commented Jul 26, 2023

bebablub commented Jul 26, 2023

NeonWizard commented Nov 6, 2023 •

edited

Loading

AskAlice commented Nov 16, 2023 •

edited

Loading

NeonWizard commented Nov 17, 2023

snhok commented Nov 17, 2023

AskAlice commented Nov 17, 2023

jafber commented Dec 4, 2023

prokopis3 commented Dec 8, 2023

sergiopvilar commented Dec 10, 2023

NeonWizard commented Dec 11, 2023

yeremi01 commented Dec 12, 2023

xiurenfuwo commented Jan 15, 2024 •

edited

Loading

prokopis3 commented Jan 15, 2024

misft55 commented Jan 19, 2024

goodpersons commented Mar 30, 2024

CalvinXu17 commented Jul 19, 2024

Error code: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED #10332

Error code: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED #10332

Comments

bebablub commented Jul 25, 2023

Windows Version

WSL Version

Are you using WSL 1 or WSL 2?

Kernel Version

Distro Version

Other Software

Repro Steps

Expected Behavior

Actual Behavior

Diagnostic Logs

ghost commented Jul 25, 2023

microsoft-github-policy-service bot commented Jul 25, 2023

bebablub commented Jul 26, 2023

bebablub commented Jul 26, 2023

NeonWizard commented Nov 6, 2023 • edited Loading

AskAlice commented Nov 16, 2023 • edited Loading

NeonWizard commented Nov 17, 2023

snhok commented Nov 17, 2023

AskAlice commented Nov 17, 2023

jafber commented Dec 4, 2023

prokopis3 commented Dec 8, 2023

sergiopvilar commented Dec 10, 2023

NeonWizard commented Dec 11, 2023

yeremi01 commented Dec 12, 2023

xiurenfuwo commented Jan 15, 2024 • edited Loading

prokopis3 commented Jan 15, 2024

misft55 commented Jan 19, 2024

goodpersons commented Mar 30, 2024

CalvinXu17 commented Jul 19, 2024

NeonWizard commented Nov 6, 2023 •

edited

Loading

AskAlice commented Nov 16, 2023 •

edited

Loading

xiurenfuwo commented Jan 15, 2024 •

edited

Loading