microsoft / WSL

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

Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS. #5363

Open liudonghua123 opened 4 years ago

liudonghua123 commented 4 years ago

Environment

C:\Users\Liu.D.H>ver

Microsoft Windows [Version 10.0.19041.264]

C:\Users\Liu.D.H>bcdedit

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {8c132511-806f-11e9-8860-f798d1b7a8f1}
displayorder            {current}
                        {89f269f4-cc9f-11e6-8727-64006a16df31}
                        {8c132516-806f-11e9-8860-f798d1b7a8f1}
toolsdisplayorder       {memdiag}
timeout                 5

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.exe
description             Windows 10
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {8c132514-806f-11e9-8860-f798d1b7a8f1}
displaymessageoverride  Recovery
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {8c132511-806f-11e9-8860-f798d1b7a8f1}
nx                      OptIn
bootmenupolicy          Legacy
hypervisorlaunchtype    Off

Windows Boot Loader
-------------------
identifier              {89f269f4-cc9f-11e6-8727-64006a16df31}
device                  partition=\Device\HarddiskVolume1
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  zh-CN
inherit                 {bootloadersettings}
osdevice                partition=\Device\HarddiskVolume1
systemroot              \Windows
resumeobject            {89f269f3-cc9f-11e6-8727-64006a16df31}
nx                      OptIn
detecthal               Yes

Windows Boot Loader
-------------------
identifier              {8c132516-806f-11e9-8860-f798d1b7a8f1}
device                  partition=C:
path                    \WINDOWS\system32\winload.exe
description             Windows10 with Hyper-V
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {8c132514-806f-11e9-8860-f798d1b7a8f1}
displaymessageoverride  Recovery
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {8c132511-806f-11e9-8860-f798d1b7a8f1}
nx                      OptIn
bootmenupolicy          Legacy
hypervisorlaunchtype    Auto

C:\Users\Liu.D.H>systeminfo

Host Name:                 DESKTOP-LDH
OS Name:                   Microsoft Windows 10 Education
OS Version:                10.0.19041 N/A Build 19041
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Windows User
Registered Organization:
Product ID:                00328-10000-00001-AA635
Original Install Date:     2020-05-11, 22:13:14
System Boot Time:          2020-06-08, 10:12:11
System Manufacturer:       Dell Inc.
System Model:              Vostro 3900
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 60 Stepping 3 GenuineIntel ~3601 Mhz
BIOS Version:              Dell Inc. A10, 2015-07-30
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             zh-cn;Chinese (China)
Input Locale:              zh-cn;Chinese (China)
Time Zone:                 (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi
Total Physical Memory:     16,301 MB
Available Physical Memory: 9,703 MB
Virtual Memory: Max Size:  33,709 MB
Virtual Memory: Available: 26,300 MB
Virtual Memory: In Use:    7,409 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:              \\DESKTOP-LDH
Hotfix(s):                 6 Hotfix(s) Installed.
                           [01]: KB4552925
                           [02]: KB4534170
                           [03]: KB4537759
                           [04]: KB4545706
                           [05]: KB4557968
                           [06]: KB4556803
Network Card(s):           4 NIC(s) Installed.
                           [01]: TAP-Windows Adapter V9
                                 Connection Name: 以太网
                                 Status:          Media disconnected
                           [02]: Realtek PCIe GBE Family Controller
                                 Connection Name: Ethernet_Realtek
                                 DHCP Enabled:    Yes
                                 DHCP Server:     113.55.112.1
                                 IP address(es)
                                 [01]: 113.55.127.140
                                 [02]: fe80::3d0a:ecde:2178:d77c
                                 [03]: 2001:250:2800:cc09:6600:6aff:fe16:df31
                           [03]: Realtek RTL8188CU Wireless LAN 802.11n USB 2.0 Network Adapter
                                 Connection Name: Wi-Fi 2
                                 Status:          Media disconnected
                           [04]: Microsoft KM-TEST Loopback Adapter
                                 Connection Name: Npcap Loopback Adapter
                                 DHCP Enabled:    Yes
                                 DHCP Server:     255.255.255.255
                                 IP address(es)
                                 [01]: 169.254.104.11
                                 [02]: fe80::d8bf:11ab:7b05:680b
Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                           Virtualization Enabled In Firmware: Yes
                           Second Level Address Translation: Yes
                           Data Execution Prevention Available: Yes

C:\Users\Liu.D.H>

image

Steps to reproduce

Open Ubuntu 18.04 or 20.04.

Expected behavior

Works as expected.

Actual behavior

image

I can confirm that I have enabled Virtual Machine Platform and VT-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.

1pavanb commented 2 years ago

ran systeminfo looked like this

Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                           Virtualization Enabled In Firmware: Yes
                           Second Level Address Translation: Yes
                           Data Execution Prevention Available: Yes

So the message it showed didn't make sense. Tried this one mentioned by people above.

DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V
bcdedit /set hypervisorlaunchtype auto

fixed it Checked systeminfo again to see any difference.

Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

🤷👍

MSRhmn commented 2 years ago

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.

1pavanb commented 2 years ago

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

alienkodok commented 2 years ago

Hope to document enable Hyper-V in https://docs.microsoft.com/en-us/windows/wsl/install-win10 when install and run wsl2.

  • DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V
  • bcdedit /set hypervisorlaunchtype auto

thanks

kdomo commented 2 years ago

bcdedit /set hypervisorlaunchtype auto Please enable Hyper-V Windows first Then reboot and enter the BIOS. Anyway, when this window appears, press F7. The Advanced Mode will appear. I'll go to Advanced Change the SVM Mode to Enabled.

Natemo2625 commented 2 years ago

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?

kdomo commented 2 years ago

@Natemo6348 Please enable Hyper-V Windows first Then reboot and enter the BIOS. Change the SVM Mode to Enabled

Natemo2625 commented 2 years ago

@kdomo did not work for me, any other ideas?

irving-vale commented 2 years ago

https://made4geek.com/error-0x80370102-the-virtual-machine-could-not-be-started-because-a-required-feature-is-not-installed-wsl-2-code-example/

dkalog commented 1 year ago

WSL 2 : This warning is a collective one it address many different causes of show stoppers. Although I had configure/ticked WSL and virtual machine platform from additional features, that was not ENOUGH For my case was enough to bcdedit /set hypervisorlaunchtype auto or ON.
( I haved picked AUTO because I used SL in conjunction with VBOX 6.1.34 and beyond..

Ukriyte commented 1 year ago

Environment

C:\Users\Liu.D.H>ver

Microsoft Windows [Version 10.0.19041.264]

C:\Users\Liu.D.H>bcdedit

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {8c132511-806f-11e9-8860-f798d1b7a8f1}
displayorder            {current}
                        {89f269f4-cc9f-11e6-8727-64006a16df31}
                        {8c132516-806f-11e9-8860-f798d1b7a8f1}
toolsdisplayorder       {memdiag}
timeout                 5

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.exe
description             Windows 10
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {8c132514-806f-11e9-8860-f798d1b7a8f1}
displaymessageoverride  Recovery
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {8c132511-806f-11e9-8860-f798d1b7a8f1}
nx                      OptIn
bootmenupolicy          Legacy
hypervisorlaunchtype    Off

Windows Boot Loader
-------------------
identifier              {89f269f4-cc9f-11e6-8727-64006a16df31}
device                  partition=\Device\HarddiskVolume1
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  zh-CN
inherit                 {bootloadersettings}
osdevice                partition=\Device\HarddiskVolume1
systemroot              \Windows
resumeobject            {89f269f3-cc9f-11e6-8727-64006a16df31}
nx                      OptIn
detecthal               Yes

Windows Boot Loader
-------------------
identifier              {8c132516-806f-11e9-8860-f798d1b7a8f1}
device                  partition=C:
path                    \WINDOWS\system32\winload.exe
description             Windows10 with Hyper-V
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {8c132514-806f-11e9-8860-f798d1b7a8f1}
displaymessageoverride  Recovery
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {8c132511-806f-11e9-8860-f798d1b7a8f1}
nx                      OptIn
bootmenupolicy          Legacy
hypervisorlaunchtype    Auto

C:\Users\Liu.D.H>systeminfo

Host Name:                 DESKTOP-LDH
OS Name:                   Microsoft Windows 10 Education
OS Version:                10.0.19041 N/A Build 19041
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Windows User
Registered Organization:
Product ID:                00328-10000-00001-AA635
Original Install Date:     2020-05-11, 22:13:14
System Boot Time:          2020-06-08, 10:12:11
System Manufacturer:       Dell Inc.
System Model:              Vostro 3900
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 60 Stepping 3 GenuineIntel ~3601 Mhz
BIOS Version:              Dell Inc. A10, 2015-07-30
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             zh-cn;Chinese (China)
Input Locale:              zh-cn;Chinese (China)
Time Zone:                 (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi
Total Physical Memory:     16,301 MB
Available Physical Memory: 9,703 MB
Virtual Memory: Max Size:  33,709 MB
Virtual Memory: Available: 26,300 MB
Virtual Memory: In Use:    7,409 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:              \\DESKTOP-LDH
Hotfix(s):                 6 Hotfix(s) Installed.
                           [01]: KB4552925
                           [02]: KB4534170
                           [03]: KB4537759
                           [04]: KB4545706
                           [05]: KB4557968
                           [06]: KB4556803
Network Card(s):           4 NIC(s) Installed.
                           [01]: TAP-Windows Adapter V9
                                 Connection Name: 以太网
                                 Status:          Media disconnected
                           [02]: Realtek PCIe GBE Family Controller
                                 Connection Name: Ethernet_Realtek
                                 DHCP Enabled:    Yes
                                 DHCP Server:     113.55.112.1
                                 IP address(es)
                                 [01]: 113.55.127.140
                                 [02]: fe80::3d0a:ecde:2178:d77c
                                 [03]: 2001:250:2800:cc09:6600:6aff:fe16:df31
                           [03]: Realtek RTL8188CU Wireless LAN 802.11n USB 2.0 Network Adapter
                                 Connection Name: Wi-Fi 2
                                 Status:          Media disconnected
                           [04]: Microsoft KM-TEST Loopback Adapter
                                 Connection Name: Npcap Loopback Adapter
                                 DHCP Enabled:    Yes
                                 DHCP Server:     255.255.255.255
                                 IP address(es)
                                 [01]: 169.254.104.11
                                 [02]: fe80::d8bf:11ab:7b05:680b
Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                           Virtualization Enabled In Firmware: Yes
                           Second Level Address Translation: Yes
                           Data Execution Prevention Available: Yes

C:\Users\Liu.D.H>

image

Steps to reproduce

Open Ubuntu 18.04 or 20.04.

Expected behavior

Works as expected.

Actual behavior

image

I can confirm that I have enabled Virtual Machine Platform and VT-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.

Environment

C:\Users\Liu.D.H>ver

Microsoft Windows [Version 10.0.19041.264]

C:\Users\Liu.D.H>bcdedit

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {8c132511-806f-11e9-8860-f798d1b7a8f1}
displayorder            {current}
                        {89f269f4-cc9f-11e6-8727-64006a16df31}
                        {8c132516-806f-11e9-8860-f798d1b7a8f1}
toolsdisplayorder       {memdiag}
timeout                 5

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.exe
description             Windows 10
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {8c132514-806f-11e9-8860-f798d1b7a8f1}
displaymessageoverride  Recovery
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {8c132511-806f-11e9-8860-f798d1b7a8f1}
nx                      OptIn
bootmenupolicy          Legacy
hypervisorlaunchtype    Off

Windows Boot Loader
-------------------
identifier              {89f269f4-cc9f-11e6-8727-64006a16df31}
device                  partition=\Device\HarddiskVolume1
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  zh-CN
inherit                 {bootloadersettings}
osdevice                partition=\Device\HarddiskVolume1
systemroot              \Windows
resumeobject            {89f269f3-cc9f-11e6-8727-64006a16df31}
nx                      OptIn
detecthal               Yes

Windows Boot Loader
-------------------
identifier              {8c132516-806f-11e9-8860-f798d1b7a8f1}
device                  partition=C:
path                    \WINDOWS\system32\winload.exe
description             Windows10 with Hyper-V
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {8c132514-806f-11e9-8860-f798d1b7a8f1}
displaymessageoverride  Recovery
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {8c132511-806f-11e9-8860-f798d1b7a8f1}
nx                      OptIn
bootmenupolicy          Legacy
hypervisorlaunchtype    Auto

C:\Users\Liu.D.H>systeminfo

Host Name:                 DESKTOP-LDH
OS Name:                   Microsoft Windows 10 Education
OS Version:                10.0.19041 N/A Build 19041
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Windows User
Registered Organization:
Product ID:                00328-10000-00001-AA635
Original Install Date:     2020-05-11, 22:13:14
System Boot Time:          2020-06-08, 10:12:11
System Manufacturer:       Dell Inc.
System Model:              Vostro 3900
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 60 Stepping 3 GenuineIntel ~3601 Mhz
BIOS Version:              Dell Inc. A10, 2015-07-30
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             zh-cn;Chinese (China)
Input Locale:              zh-cn;Chinese (China)
Time Zone:                 (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi
Total Physical Memory:     16,301 MB
Available Physical Memory: 9,703 MB
Virtual Memory: Max Size:  33,709 MB
Virtual Memory: Available: 26,300 MB
Virtual Memory: In Use:    7,409 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:              \\DESKTOP-LDH
Hotfix(s):                 6 Hotfix(s) Installed.
                           [01]: KB4552925
                           [02]: KB4534170
                           [03]: KB4537759
                           [04]: KB4545706
                           [05]: KB4557968
                           [06]: KB4556803
Network Card(s):           4 NIC(s) Installed.
                           [01]: TAP-Windows Adapter V9
                                 Connection Name: 以太网
                                 Status:          Media disconnected
                           [02]: Realtek PCIe GBE Family Controller
                                 Connection Name: Ethernet_Realtek
                                 DHCP Enabled:    Yes
                                 DHCP Server:     113.55.112.1
                                 IP address(es)
                                 [01]: 113.55.127.140
                                 [02]: fe80::3d0a:ecde:2178:d77c
                                 [03]: 2001:250:2800:cc09:6600:6aff:fe16:df31
                           [03]: Realtek RTL8188CU Wireless LAN 802.11n USB 2.0 Network Adapter
                                 Connection Name: Wi-Fi 2
                                 Status:          Media disconnected
                           [04]: Microsoft KM-TEST Loopback Adapter
                                 Connection Name: Npcap Loopback Adapter
                                 DHCP Enabled:    Yes
                                 DHCP Server:     255.255.255.255
                                 IP address(es)
                                 [01]: 169.254.104.11
                                 [02]: fe80::d8bf:11ab:7b05:680b
Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                           Virtualization Enabled In Firmware: Yes
                           Second Level Address Translation: Yes
                           Data Execution Prevention Available: Yes

C:\Users\Liu.D.H>

image

Steps to reproduce

Open Ubuntu 18.04 or 20.04.

Expected behavior

Works as expected.

Actual behavior

image

I can confirm that I have enabled Virtual Machine Platform and VT-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.

How did you get all the environment info of your machine?

S-Osman4 commented 1 year ago

@Ukriyte typing systeminfo as administrator in your terminal should work

MHKhan18 commented 1 year ago

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

NikolozCh commented 1 year ago

Hope to document enable Hyper-V in https://docs.microsoft.com/en-us/windows/wsl/install-win10 when install and run wsl2.

  • DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V
  • bcdedit /set hypervisorlaunchtype auto

Thanks for the help. It worked like a charm!

Note: Before running the commands, open Powershell with admin rights.

wabass commented 1 year ago

Have you tried

$wsl --update
mym4y4 commented 1 year ago

Just enable the optional component 'Windows Hypervisor Platform'

jay-jjwu commented 1 year ago

if you are using a virtualized windows, enable this CPU setting in your virtual platform... image

DanKaplanSES commented 1 year ago

What's left in this feature? Is it to update the documentation in the FAQ?

WSL 2 is available on all Desktop SKUs where WSL is available, including Windows 10 Home and Windows 11 Home.

The newest version of WSL uses Hyper-V architecture to enable its virtualization. This architecture will be available in the 'Virtual Machine Platform' optional component. This optional component will be available on all SKUs. You can expect to see more details about this experience soon as we get closer to the WSL 2 release.

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.

Stan-Green commented 11 months ago

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?

borguuh commented 10 months ago

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 off

Restart your system after executing the command.

To use Hyper-V:

Bcdedit /set hypervisorlaunchtype auto

Again, 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!

Stan-Green commented 10 months ago

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.

annehanako commented 9 months ago

image I am having the following issue, I need WSL for Docker, trying to fix it. I already enabled my VM in BIOS and followed all the steps I could find, still nothing working. In my other computer tho I had no issues with this. I will be updating if I find a way to fix it.

Edit: Was able to fix it setting my BIOS to default and enabling the SVM again.

AshleyHelen808 commented 8 months ago

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!

bravemaster3 commented 6 months ago

I also did everything, until the suggestions of some above, to deactivate and reactivate WSL (in windows features), worked for me as well.

f4lz commented 3 months ago
 bcdedit /set hypervisorlaunchtype auto

Solved

AionZones commented 2 months ago

Environment

C:\Users\Liu.D.H>ver

Microsoft Windows [Version 10.0.19041.264]

C:\Users\Liu.D.H>bcdedit

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {8c132511-806f-11e9-8860-f798d1b7a8f1}
displayorder            {current}
                        {89f269f4-cc9f-11e6-8727-64006a16df31}
                        {8c132516-806f-11e9-8860-f798d1b7a8f1}
toolsdisplayorder       {memdiag}
timeout                 5

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.exe
description             Windows 10
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {8c132514-806f-11e9-8860-f798d1b7a8f1}
displaymessageoverride  Recovery
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {8c132511-806f-11e9-8860-f798d1b7a8f1}
nx                      OptIn
bootmenupolicy          Legacy
hypervisorlaunchtype    Off

Windows Boot Loader
-------------------
identifier              {89f269f4-cc9f-11e6-8727-64006a16df31}
device                  partition=\Device\HarddiskVolume1
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  zh-CN
inherit                 {bootloadersettings}
osdevice                partition=\Device\HarddiskVolume1
systemroot              \Windows
resumeobject            {89f269f3-cc9f-11e6-8727-64006a16df31}
nx                      OptIn
detecthal               Yes

Windows Boot Loader
-------------------
identifier              {8c132516-806f-11e9-8860-f798d1b7a8f1}
device                  partition=C:
path                    \WINDOWS\system32\winload.exe
description             Windows10 with Hyper-V
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {8c132514-806f-11e9-8860-f798d1b7a8f1}
displaymessageoverride  Recovery
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {8c132511-806f-11e9-8860-f798d1b7a8f1}
nx                      OptIn
bootmenupolicy          Legacy
hypervisorlaunchtype    Auto

C:\Users\Liu.D.H>systeminfo

Host Name:                 DESKTOP-LDH
OS Name:                   Microsoft Windows 10 Education
OS Version:                10.0.19041 N/A Build 19041
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Windows User
Registered Organization:
Product ID:                00328-10000-00001-AA635
Original Install Date:     2020-05-11, 22:13:14
System Boot Time:          2020-06-08, 10:12:11
System Manufacturer:       Dell Inc.
System Model:              Vostro 3900
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 60 Stepping 3 GenuineIntel ~3601 Mhz
BIOS Version:              Dell Inc. A10, 2015-07-30
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             zh-cn;Chinese (China)
Input Locale:              zh-cn;Chinese (China)
Time Zone:                 (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi
Total Physical Memory:     16,301 MB
Available Physical Memory: 9,703 MB
Virtual Memory: Max Size:  33,709 MB
Virtual Memory: Available: 26,300 MB
Virtual Memory: In Use:    7,409 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:              \\DESKTOP-LDH
Hotfix(s):                 6 Hotfix(s) Installed.
                           [01]: KB4552925
                           [02]: KB4534170
                           [03]: KB4537759
                           [04]: KB4545706
                           [05]: KB4557968
                           [06]: KB4556803
Network Card(s):           4 NIC(s) Installed.
                           [01]: TAP-Windows Adapter V9
                                 Connection Name: 以太网
                                 Status:          Media disconnected
                           [02]: Realtek PCIe GBE Family Controller
                                 Connection Name: Ethernet_Realtek
                                 DHCP Enabled:    Yes
                                 DHCP Server:     113.55.112.1
                                 IP address(es)
                                 [01]: 113.55.127.140
                                 [02]: fe80::3d0a:ecde:2178:d77c
                                 [03]: 2001:250:2800:cc09:6600:6aff:fe16:df31
                           [03]: Realtek RTL8188CU Wireless LAN 802.11n USB 2.0 Network Adapter
                                 Connection Name: Wi-Fi 2
                                 Status:          Media disconnected
                           [04]: Microsoft KM-TEST Loopback Adapter
                                 Connection Name: Npcap Loopback Adapter
                                 DHCP Enabled:    Yes
                                 DHCP Server:     255.255.255.255
                                 IP address(es)
                                 [01]: 169.254.104.11
                                 [02]: fe80::d8bf:11ab:7b05:680b
Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                           Virtualization Enabled In Firmware: Yes
                           Second Level Address Translation: Yes
                           Data Execution Prevention Available: Yes

C:\Users\Liu.D.H>

image

Steps to reproduce

Open Ubuntu 18.04 or 20.04.

Expected behavior

Works as expected.

Actual behavior

image

I can confirm that I have enabled Virtual Machine Platform and VT-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.

hi sir

AionZones commented 2 months ago

image Can you help me how to disable in command prompt the four hyper v pls? Im playing a game called aion and i cant run the game because it still detecting the hyper v error.. Pls let me know how you can disable it tru command prompt or any settings in windows 11 Home. Thank u so much in advance for helping

VladasZ commented 2 months ago

@TradingIndian this worked for me too. Thanks!

rtmreza commented 2 months ago

for solve this problem : see this video

https://www.youtube.com/watch?v=myouQBBDhXQ