Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS. #5363
Comments
|
From the doc https://docs.microsoft.com/en-us/windows/wsl/wsl2-faq, It seems that hyper-v is a requirement when running wsl2. So I have to enable hyper-v? I will test it and report later. |
|
Hope to document enable Hyper-V in https://docs.microsoft.com/en-us/windows/wsl/install-win10 when install and run wsl2.
|
|
@liudonghua123 - The Hyper-V feature is not required, but Virtual Machine Platform (which includes the Hyper-V hypervisor) is required. |
|
I get same error after clean install, Win 10 Home. Tried many times to enable/reenable features and rebooting pc. Virtualization is enabled in bios and shown as active in task manager. With clean install of ubuntu i get error |
|
|
|
suddenly resolved it by resetting bios. |
|
@benhillis From the doc https://docs.microsoft.com/en-us/windows/wsl/wsl2-faq, It seems that hyper-v is a requirement when running wsl2. If I disabled it, then I got |
|
The faq says (quoth) "...WSL uses Hyper-V architecture to enable its virtualization. This architecture will be available in the 'Virtual Machine Platform' optional component". That is the checkbox you want, and you look good:
You also seem okay as far as Hyper-V requirements go, notably your BIOS, per your Collect detailed logs. @benhillis there is probably some semi-actionable here, at least in terms of user feedback in the error path. The upcoming |
|
Seems that NX Pages protection can be issue, enable it if the WSL2 fails to launch. |
|
I'm having the same issue. i updated my windows system, restarted and keep getting this message. I have been running wsl2 with no issues and all of a sudden this is now occurring. |
|
Same problem: |
I figured out my issue. It broke to do installing CS:GO ESEA client. In order to fix, i had to uninstall and disable and re-enable WSL features. |
|
when i took your advice, I fixed unexpectedly. thanks ！
|
|
I was just glad to see that by enabling the following modules in
Seems to be kind of like brute force, but at least it works now 😃 |
|
After the update to WSL2 and some reboots later, I had the same issue. Disabling and re-enabling WSL fixed the problem for me. @spennymac Thanks for figuring that out! 👍 |
|
When I try to update to WSL 2 I get this as well. Of course I followed all the steps listed here https://docs.microsoft.com/en-us/windows/wsl/install-win10#update-to-wsl-2 |
|
suffer this problem and still cannot fix it, even though I reinstall WSL and enable the virtualization in BIOS |
|
|
I reset my BIOS and bcdedit /set hypervisorlaunchtype autoReally worked! |
|
If anyone else come across this trying to upgrade to WSL2 from 1
|
|
I'm keeping Hyper-V turned off because I use VMware Workstation Pro on my PC, but your command below fixed the problem for me. Thank you very much!
|
I have the same situation. Hyper-V off due to VMware but after running this command, rebooting and running again |
|
I solved this issue in simpler way. Went to BIOS setup, disabled Virtualization in BIOS. Booted Windows. Once properly booted, shutdown and restart in BIOS setup. Enable Virtualization in BIOS et voilà. It works in WSL 2. I had to reinstall Ubuntu though, which was still showing WSL 1 version. But because it was fresh install, I did not have to worry about legacy baggage. |
This last bit did it for me after restart. |
|
I solved my issue the same way that TradianIndian solved his. Disable Virtualization in the bios, rebooted to windows, enabled virtualization and now WSL works for me. |
|
Similar to @TradingIndian and @michaeldrawe, my issue was that virtualization was disabled on my machine. You can check whether virtualization is enabled or not by opening the "Turn Windows features on or off" menu -- if virtualization is disabled, the check box next to "Virtual Machine Platform" will be grayed out, and a pop-up will confirm that virtualization is not enabled. To fix the problem, I followed these instructions to enable virtualization in my UEFI firmware. |
That worked for me... Gotta love the good ol' turn it off and on again. |
|
ran systeminfo So the message it showed didn't make sense. Tried this one mentioned by people above. fixed it 🤷👍 |
|
Two month's ago I had a conflict with wsl as "catastrophic failure". Solutions from the issue didn't solve my problem, so I had to make a clean install and end up losing wsl data. This time, it doesn't just work as solutions from up above, neither a clean install. |
F |
thanks |
|
|
|
After trying everything here, I still can't get WSL2 to work, any ideas as to what I can try and what I should look for? |
|
@Natemo6348 |
|
@kdomo did not work for me, any other ideas? |
|
WSL 2 : This warning is a collective one it address many different causes of show stoppers. |
How did you get all the environment info of your machine? |
|
@Ukriyte typing systeminfo as administrator in your terminal should work |
|
I was having the same error on a Windows-10 machine despite having the Virtual Machine Platform and Windows Subsystem for Linux features turned on. Got around it by enabling Intel Software Guards Extension in Bios settings (it was set to software controlled). |
Thanks for the help. It worked like a charm! Note: Before running the commands, open Powershell with admin rights. |
|
Have you tried |
|
Just enable the optional component 'Windows Hypervisor Platform' |
|
if you are using a virtualized windows, enable this CPU setting in your virtual platform... |
|
What's left in this feature? Is it to update the documentation in the FAQ?
This second paragraph seems like it was written before WSL2 or maybe before the 'Virtual Machine Platform' checkbox existed? If I'm wrong about that, IMHO, the wording gives this impression. I'd add how to get to the "Turn Windows Features On or Off" dialog to change that 'Virtual Machine Platform' checkbox (Press Win + Q then search for "Turn Windows Features On or Off"). I tried to find out how I could submit a PR with a doc update, but after a few minutes I couldn't find where it's committed. I'm assuming only MS employees can edit that page. |
|
I still cannot run VMWare Player 5.5.7 with Virtualization enabled (I need this to run Docker in the VM) and WSL2 on the same desktop computer. This works on my Lenovo T480 laptop; I don't know why the laptop is different, as all the Windows features are the same as the desktop. Both are on Windows 10. As others have noted, I have the "Virtual Machine Platform" feature enabled and the "Hyper-V" feature disabled due to the VMWare requirement. The command "bcdedit /set hypervisorlaunchtype auto" does not work as the VMWare VM will not run due to the Virtualization being turned on in the Gust OS. I know this is an ancient issue, but are there any updates on running WSL2 and VMWare on the same desktop computer? |
|
Found a solution for coexisting VMware Workstation Pro and Hyper-V on the same system. Although they can't run simultaneously, you can switch between them using the following commands: To use VMware Workstation Pro: Bcdedit /set hypervisorlaunchtype offRestart your system after executing the command. To use Hyper-V: Bcdedit /set hypervisorlaunchtype autoAgain, restart your system after executing the command. This allows you to use either VMware Workstation Pro 15 or Hyper-V on the same machine, one at a time. Hope this helps! |
|
Yes, @borguuh if you are OK with restarting all the time, that would work. I don't what to have to restart just to run a quick WSL command. I only restart when Windows makes me! Again, I can run both at the same time on my laptop, but not my desktop. They both have the same settings. I would like to run both WSL2 and VMWare Player (BTW: Not Pro) at the same time. |
|
Edit: Was able to fix it setting my BIOS to default and enabling the SVM again. |
|
Just resolved this issue by updating my bios to include virtualization. It's quite hidden in UEFI, the search did nothing for me. Windows doesn't even pick it up in windows features. Good luck! |
|
I also did everything, until the suggestions of some above, to deactivate and reactivate WSL (in windows features), worked for me as well. |
bcdedit /set hypervisorlaunchtype autoSolved |
hi sir |
|
|
|
@TradingIndian this worked for me too. Thanks! |
|
for solve this problem : |
|
This command saved my life bcdedit /set hypervisorlaunchtype auto |
and others
Environment
Steps to reproduce
Open Ubuntu 18.04 or 20.04.
Expected behavior
Works as expected.
Actual behavior
I can confirm that I have enabled
Virtual Machine PlatformandVT-x. But the errors when I started Ubuntu is confused.And for some reasons I do not want to enable Hyper-V features. From the doc (https://docs.microsoft.com/en-us/windows/wsl/), it is not a requirement for WSL2.
The text was updated successfully, but these errors were encountered: