WSL: WSL2 not starting despite Hyper-V and virtualization being enabled

Background: I used to run WSL1 & WSL2 perfectly fine, I had to disable Hyper-V along with WSL a little bit ago. Ever since I disabled them in the past I haven’t been able to enable everything properly again. Hyper-V features on enabled and services running, Virtualization is enabled in BIOS but yet… I cannot start WSL.

No hardware changes or anything else significant between the last time it worked and now.

Please fill out the below information:

  • Microsoft Windows [Version 10.0.19025.1051]

  • What you’re doing and what’s happening:

C:\WINDOWS\system32>wsl
Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.
For information please visit https://aka.ms/wsl2-install
  • What’s wrong / what should be happening instead: It should just go into my WSL2 VM, it is instead just spitting out: Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.

wsl -l -v output:

C:\Users\Walshy\wsl-report>wsl -l -v
  NAME      STATE           VERSION
* Ubuntu    Stopped         2
  Debian    Stopped         1
Images of features, services and virtualization in task manager

Features: Image of Windows features

Services: Image of services

Task Manager showing Virtualization enabled: Task Manager showing Virtualization enabled

  • Strace of the failing command, if applicable:
C:\Users\Walshy\wsl-report>strace wsl -d Ubuntu
--- Process 12808 created
--- Process 12808 loaded C:\Windows\System32\ntdll.dll at 00007ffa89ab0000
--- Process 12808 loaded C:\Windows\System32\kernel32.dll at 00007ffa88b80000
--- Process 12808 loaded C:\Windows\System32\KernelBase.dll at 00007ffa87610000
--- Process 12808 loaded C:\Windows\System32\ucrtbase.dll at 00007ffa878e0000
--- Process 12808 thread 14612 created
--- Process 12808 loaded C:\Windows\System32\SHCore.dll at 00007ffa88cc0000
--- Process 12808 loaded C:\Windows\System32\msvcrt.dll at 00007ffa88d80000
--- Process 12808 loaded C:\Windows\System32\combase.dll at 00007ffa87b30000
--- Process 12808 loaded C:\Windows\System32\rpcrt4.dll at 00007ffa88330000
--- Process 12808 thread 13688 created
--- Process 12808 loaded C:\Windows\System32\ws2_32.dll at 00007ffa89840000
--- Process 12808 loaded C:\Windows\System32\kernel.appcore.dll at 00007ffa85b40000
--- Process 12808 loaded C:\Windows\System32\bcryptprimitives.dll at 00007ffa87380000
--- Process 12808 loaded C:\Windows\System32\sechost.dll at 00007ffa899d0000
--- Process 12808 loaded C:\Windows\System32\clbcatq.dll at 00007ffa89550000
--- Process 12808 thread 4416 created
--- Process 12808 thread 4616 created
--- Process 12808 thread 17776 created
--- Process 12808 loaded C:\Windows\System32\lxss\LxssManagerProxyStub.dll at 00007ffa7a100000
--- Process 12808, exception e06d7363 at 00007ffa87645a29
--- Process 12808 unloaded DLL at 00007ffa7a100000
--- Process 12808, exception e06d7363 at 00007ffa87645a29
Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.
For information please visit https://aka.ms/wsl2-install
--- Process 12808 thread 14612 exited with status 0xffffffff
--- Process 12808 thread 13688 exited with status 0xffffffff
--- Process 12808 thread 4416 exited with status 0xffffffff
--- Process 12808 thread 4616 exited with status 0xffffffff
--- Process 12808 thread 17776 exited with status 0xffffffff
--- Process 12808 exited with status 0xffffffff
  • I have attached the logman details (Started before running wsl and stopped after it failed): wsl-report.zip

About this issue

  • Original URL
  • State: open
  • Created 7 years ago
  • Reactions: 10
  • Comments: 66 (2 by maintainers)

Most upvoted comments

Did you try bcdedit /set hypervisorlaunchtype auto

I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.

Did you try bcdedit /set hypervisorlaunchtype auto

I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.

Mine was working fine till I started up an Android Studio Emulator last week. Since then I’ve been fighting to try and get wsl2 working again. BIOS was good, features were turned on, but no dice.

Finally tried the command above with a reboot and it worked!

Did you try bcdedit /set hypervisorlaunchtype auto I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.

Mine was working fine till I started up an Android Studio Emulator last week. Since then I’ve been fighting to try and get wsl2 working again. BIOS was good, features were turned on, but no dice.

Finally tried the command above with a reboot and it worked!

Yes, it work for wsl, but doesn’t good for VirtualBox.

WSL : bcdedit /set hypervisorlaunchtype auto + RESTART VirtualBox: bcdedit /set hypervisorlaunchtype off + RESTART

Someone from spacedesk over at the spacedesk forum posted a potential fix, I can’t try it anymore as I have reset my PC in the meantime. I hope it can help someone else.

Currently it seems as if there could be a side effect with microsoft hyper-v virtualization infrastructure driver. It seems as if the problem could be solved by manually re-installing this driver. Please try the fix below and let us know if it solved the problem.

  1. Go to device manager -> Action -> add legacy hardware.
  2. Choose Option „Select hardware manual from list“ in the wizard
  3. Choose „Systemdevices“ in the list
  4. Choose „Microsoft“ in vendors
  5. Choose „microsoft hyper-v virtualization infrastructure driver“ in models
  6. Follow the wizard to finish the installation
  7. Restart the computer

image

Just to be sure, you do have the feature “Virtual Machine Platform” enabled, as in this picture?

image

I was having this same problem. I disabled AMD SVM, booted, then re-enabled AMD SVM and it worked again. Hope this helps

Did you try bcdedit /set hypervisorlaunchtype auto

I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.

So, It is not possible to use VM and WSL2 at same time?

I ended up re-installing Windows and tried to reinstall all programs one by one that were previously installed in my system. Took several hours for me (re-installed Windows multiple times) until I figured out which program did ruin the WSL.

Turned out that the culprit was spacedesk. So, my solution was to not install spacedesk after re-installing Windows.

I’m also having this issue seemingly as a result of installing Spacedesk. Trying to start, export, or change the version of an existing WSL2 distro gives the “Please enable the Virtual Machine Platform Windows feature” error message. I’ve tried every fix suggested here and in this thread but with no success. Thankfully WSL1 still works, after I reinstalled the distro.

  • Windows 10.0.19044.1415
  • WSL kernel version 5.10.60.1
  • Spacedesk version 1.0.25

Did you try bcdedit /set hypervisorlaunchtype auto I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again. It really works if you ever tried android emulator.

Yeah it worked finally!

I used:

Activate VirtualBox (Disable Hyper-V):
bcdedit /set hypervisorlaunchtype off

Activate WSL (Enable Hyper-V):
bcdedit /set hypervisorlaunchtype auto

to enable and disable Hyper V so I can run WSL or VM. However, the PC needs restart

Did you try bcdedit /set hypervisorlaunchtype auto I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.

So, It is not possible to use VM and WSL2 at same time?

I quote this question. Is any way to have both WSL2 and VM ?

Had no problem last week. But this is now happening to me. I didn’t touch anything about the VirtualMachinePlatform. I didn’t touch any BIOS settings. I’m relying on WSL2 for my work and now suddenly not working

I tried:

  • reinstall WSL via Turn on/off features
  • run dism thingy to disable and enable WSL2 and Virtual Machine Platform
  • disable + re-enable the VT-d and Intel Vietualization Technology
  • run bcedit thingy to auto, and off as well
  • enable / disable hypervisor
  • uninstall docker desktop
  • uninstall windows subsystem for android
  • reset network adapters
  • reset winsock
  • restart the computer many times
  • check windows event viewer: no error related to wsl
  • subscribe to beta channel

Nothing worked for me.

I have the same issue, I have all the required features enabled (with the virtualization enabled in the BIOS). I don’t have any emulator like the Android simulator, VMware, VirtualBox or anything like that. I tried everything but nothing solves this issue. image

Re-installing Windows with “Keep my personal files” settings worked for me.

I you uninstall spacedesk using spacedesk installer before re-installing Windows, the driver will not be brought back to your new Windows installation.

But if you don’t uninstall spacedesk, Windows will still bring spacedesk over your new Windows installation, BUT somehow they work together (WSL and spacedesk), then again don’t use the spacedesk installer to install it again.

@benhillis How it’s going to help on original issue, did anyone solved this original issue in Win 10 home edition successfully? Can you please elaborate valid steps? Thanks in advance!

Someone from spacedesk over at the spacedesk forum posted a potential fix, I can’t try it anymore as I have reset my PC in the meantime. I hope it can help someone else.

Currently it seems as if there could be a side effect with microsoft hyper-v virtualization infrastructure driver. It seems as if the problem could be solved by manually re-installing this driver. Please try the fix below and let us know if it solved the problem.

  1. Go to device manager -> Action -> add legacy hardware.
  2. Choose Option „Select hardware manual from list“ in the wizard
  3. Choose „Systemdevices“ in the list
  4. Choose „Microsoft“ in vendors
  5. Choose „microsoft hyper-v virtualization infrastructure driver“ in models
  6. Follow the wizard to finish the installation
  7. Restart the computer

image

Thanks, this really worked for me. Now I can use WSL without any problems.

Did you try bcdedit /set hypervisorlaunchtype auto

I disabled hyper-v with bcdedit /set hypervisorlaunchtype off to do some work in VMWare, and ebabled it with auto successfully back again.

It really works if you ever tried android emulator.

WSL : bcdedit /set hypervisorlaunchtype auto + RESTART VirtualBox: bcdedit /set hypervisorlaunchtype off + RESTART

worked for me

Finally it fixed it for me by doing an update installation “keep my personal files and programs” through the MediaCreationTool. Wsl (and Windows sandbox) is finally working again.

One tip for anyone wondering about the output of the Intel® Processor Identification Utility. It still shows for me an X (for not enabled) for Intel Virtualisation Technology and EPT/SLAT support. But my wsl2 and Windows sandbox is working fine. (i5-10600k)

@WalshyDev, at 2:58 in, this YouTuber says to not enable Windows Hypervisor Platform when adding WSL2. He doesn’t say why, though.

VMWare Workstation 15.5.5 Pro supports using the Microsoft Hypervisor Platform APIS. You will need to be running that version or later.

WSL2 requires the “Virtual Machine Platform” optional component which is available on all SKUs.

It works for me after update. I tried both bcdebit /set hypervisorlaunchtype auto & off it works but i have to restart my pc every time to update setting. After update it is working fine.

I got the same problem,now I can only use wsl1.

Stupid question, but, did you reboot Windows after enabling everything? 😅