search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.37k stars 817 forks source link

After update HCS_E_HYPERV_NOT_INSTALLED #11117

Closed SirLouen closed 8 months ago

SirLouen commented 8 months ago

Windows Version

10.0.22631.3007

WSL Version

2.0.14.0

Are you using WSL 1 or WSL 2?

Kernel Version

No response

Distro Version

No response

Other Software

No response

Repro Steps

  1. Virtual Machine Platform is installed
  2. VT is enabled on BIOS
  3. Hyper-V IS NOT INSTALLED`(and I won't be installing because I don't need Hyper-V and AFAIK, is not needed for WSL2)

Expected Behavior

Ubuntu VM starts on command

Actual Behavior

Everything was running perfect (except for one minor bug with some graphics glitch I wanted to solve). I updated to latest 2.0.14.0 WSL version with wsl --update and the issue started from there.

When I start the VM with Ubuntu, it fails with the error: Error code: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED

Diagnostic Logs

No response

Further information

I'm using an Android Emulator called MuMu, which happens to disable Hyper-V. I don't have the Hyper-V libraries installed (in Features) but I only have Virtual Machine Platform.

I tried to uninstall -> Reboot -> and then reinstall -> Reboot, the Virtual Machine Platform and it happened to work again the WSL2, but as soon as I go into MuMu it says that Hyper-V has been enabled with the Virtual Machine Platform. So I must assume that despite of not installing the specific features of Hyper-V the Virtual Machine Platform HAS Hyper-V by Default

Conclusion: WSL2 does not, work without Hyper-V, despite I've read that it does. It seems that there is a subset of Hyper-V inside Virtual Machine Platform. Very unfortunate I could not use WSL2 anymore, while using Android instances with Intel's VT Virtualization platform (what MuMu emulator uses)

github-actions[bot] commented 8 months ago

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

SirLouen commented 8 months ago

I've updated the original report with Further Information to clarify a situation that I have encountered. Maybe it could be useful to get some extra answers to dig further, or maybe it's plain impossible to run WSL2 under the circumstances described, and this issue can be closed.

benhillis commented 8 months ago

MuMu uses a hypervisor that is not compatible with Hyper-V's hypervisor. This is by design.

SirLouen commented 8 months ago

MuMu uses a hypervisor that is not compatible with Hyper-V's hypervisor. This is by design.

Yes, that was my original question: Hyper-V is actually a full requirement for WSL2, right? I was reading in this issue that it wasn't https://github.com/MicrosoftDocs/WSL/issues/899

But maybe the answers were biased.