Error 0x80370102 The Virtual machine could not be started because a required feature is not installed .... #436

SteveALee · 2019-06-27T19:21:37Z

Following instructions on https://docs.microsoft.com/en-us/windows/wsl/wsl2-install#feedback with a fairly clean install of Build 18922

enabled The VMPlatform, reboot
enabled wsl, reboot
wsl set-default-verion 2
Install Ubuntu from store - https://aka.ms/wslstore as directed by wsl -l -v
Launch Ubuntu

Get the above error.

The text was updated successfully, but these errors were encountered:

craigloewen-msft · 2019-06-27T19:46:04Z

Is virtualization enabled in your BIOS? That could be a quick fix.

We're tracking this issue over in #404 and we can help you troubleshoot there!

SteveALee · 2019-06-28T08:27:34Z

Ah, yes. I didn;t check as 0x80370102 is different error number to that listed for that issue. I forgot to enable it as Insiders Machine was not a dev PC. Still getting the error though. Will head over to #404 (a very suitable number) :D

blackmasks · 2020-09-02T03:33:53Z

I had a similar problem on when installing on my new system. I checked my BIOS @craigloewen-msft as mentioned. The first time I didn't find anything but after doing a bit more research I tried turning on SVM in the BIOS and it worked. (I also turned on the Windows Hypervisor setting in Windows Features)

(Advanced → CPU Configuration → SVM → Enable)

This is the case for AMD systems. Apparently it is different for Intel based systems.

MJEND7 · 2020-09-03T03:49:29Z

Hi i am have i BIG issue with getting Kali Linux installed on my Windows 10 PC. i was having a problem with Kali it said that there were unmet dependencies. try 'apt --fix-broken install' with no packages (or specify a solution). and i looked it up and i just could not find anything to fix it so i was like "ok i will just uninstall and try a again later". but when i installed it again it will not even work like at ALL!!
and this is the error (╯°□°）╯︵ ┻━┻
WslRegisterDistribution failed with error: 0x80370102
Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.

but i have all the right "dependencies" #i say with sarcasm, pls pls pls help MeEeeE

ManoloMoraes · 2020-09-06T06:15:48Z

Is virtualization enabled in your BIOS? That could be a quick fix.

We're tracking this issue over in #404 and we can help you troubleshoot there!

Thank you, i enable and work.

ghost · 2020-09-22T13:38:50Z

Is virtualization enabled in your BIOS? That could be a quick fix.
We're tracking this issue over in #404 and we can help you troubleshoot there!

Thank you, i enable and work.

how did u do it

ktmn · 2020-09-25T06:45:20Z

"The Virtual machine could not be started because a required feature is not installed"

How about make the message say which feature is not installed.

I got Virtualization enabled in BIOS, Windows Subsystems for Linux and Virtual Machine Platform enabled in Windows features, still get the message.
Do I need Hyper-V enabled? Do I need Windows Hypervisor Platform?

Edit: no, enabling these 2 didn't solve it either.

Edit 2: running bcdedit /set hypervisorlaunchtype auto start and reboot seems to have worked for me. So maybe I did need Hyper-V and/or Hypervisor Platform enabled, but it doesn't tell you anything useful.

kscott5 · 2020-09-27T23:55:52Z

Hi @ktmn ,

Windows Subsystem for Linux or #WSL is for me and I'm aware this issue was closed. I got the following error after
Upgrading #WSL Windows Subsystem for #Linux on Windows 10 Professional with only bios #Virtualization and not SLAT.

"#0x80370102 the #virtual #machine could not be started because a required feature is not installed."

C:>wsl --set-default-version 1, Set default version 1, resolves the error on my desktop.

The above resolves the error and got me further. Now...

C:>ubunutu.exe
Prompts with new username and password.

MJEND7 · 2020-09-28T00:08:16Z

Yes I fix it thank you very much

…

On Mon., 28 Sep. 2020, 9:56 am Karega Scott, ***@***.***> wrote: Hi @ktmn <https://github.com/ktmn> , Windows Subsystem for Linux or #WSL is for me and I'm aware this issue was closed. I got the following error after Upgrading #WSL Windows Subsystem for #Linux on Windows 10 Professional with only bios #Virtualization and not SLAT. "#0x80370102 the #virtual #machine could not be started because a required feature is not installed." C:>wsl --set-default-version 1, Set default version 1, resolves the error on my desktop. The above resolves the error and got me further. Now... C:>ubunutu.exe Prompts with new username and password. [image: WSL2_Error_0x80370102] <https://user-images.githubusercontent.com/132991/94378978-01ab7980-00f3-11eb-80c9-50b5bc38d2ab.JPG> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#436 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOL4MB6S5AMHC42BBYUUVALSH7GJLANCNFSM4H37NKFA> .

thomas-griffiths · 2020-10-12T04:20:15Z

"The Virtual machine could not be started because a required feature is not installed"

How about make the message say which feature is not installed.

I got Virtualization enabled in BIOS, Windows Subsystems for Linux and Virtual Machine Platform enabled in Windows features, still get the message.
Do I need Hyper-V enabled? Do I need Windows Hypervisor Platform?

Edit: no, enabling these 2 didn't solve it either.

Edit 2: running bcdedit /set hypervisorlaunchtype auto start and reboot seems to have worked for me. So maybe I did need Hyper-V and/or Hypervisor Platform enabled, but it doesn't tell you anything useful.

This worked for me too. Thank you.

12729582 · 2020-10-15T09:51:13Z

Hi @ktmn ,

Windows Subsystem for Linux or #WSL is for me and I'm aware this issue was closed. I got the following error after
Upgrading #WSL Windows Subsystem for #Linux on Windows 10 Professional with only bios #Virtualization and not SLAT.

"#0x80370102 the #virtual #machine could not be started because a required feature is not installed."

C:>wsl --set-default-version 1, Set default version 1, resolves the error on my desktop.

The above resolves the error and got me further. Now...

C:>ubunutu.exe
Prompts with new username and password.

thank you thank you

mtshikomba · 2020-10-16T05:04:35Z

$ wsl --set-default-version 1

This one solved it for me.

Hi @ktmn ,

Windows Subsystem for Linux or #WSL is for me and I'm aware this issue was closed. I got the following error after
Upgrading #WSL Windows Subsystem for #Linux on Windows 10 Professional with only bios #Virtualization and not SLAT.

"#0x80370102 the #virtual #machine could not be started because a required feature is not installed."

C:>wsl --set-default-version 1, Set default version 1, resolves the error on my desktop.

The above resolves the error and got me further. Now...

C:>ubunutu.exe
Prompts with new username and password.

This one solved it for me.

pluc · 2020-12-03T14:39:57Z

How about you come up with specific, non-stupid error messages so people don't have to go through this thread to identify what was the error?

WhiteZorin · 2020-12-14T11:59:56Z

@ktmn - THANK YOU! the below has solved the issue after days of trying random solutions from google/blogs/ms threads...

Edit 2: running bcdedit /set hypervisorlaunchtype auto start and reboot seems to have worked for me. So maybe I did need Hyper-V and/or Hypervisor Platform enabled, but it doesn't tell you anything useful.

Although it doesn't show any Hyper-V or Hypervisor platform to be turned on in "Turn windows features on". And in services.msc the only one working currently is: Hyper-V host compute service...

ghost · 2020-12-15T19:42:49Z

I had the same problem and changing the setting in my bios to enable VM fixed this issue, so try that too in case none of the commands above fixed it for you

DarkChocolate · 2020-12-18T20:28:14Z

"The Virtual machine could not be started because a required feature is not installed"

How about make the message say which feature is not installed.

I got Virtualization enabled in BIOS, Windows Subsystems for Linux and Virtual Machine Platform enabled in Windows features, still get the message.
Do I need Hyper-V enabled? Do I need Windows Hypervisor Platform?

Edit: no, enabling these 2 didn't solve it either.

Edit 2: running bcdedit /set hypervisorlaunchtype auto start and reboot seems to have worked for me. So maybe I did need Hyper-V and/or Hypervisor Platform enabled, but it doesn't tell you anything useful.

This worked for me as well, thank you!

imperialguy · 2020-12-24T13:01:48Z

"The Virtual machine could not be started because a required feature is not installed"
How about make the message say which feature is not installed.
I got Virtualization enabled in BIOS, Windows Subsystems for Linux and Virtual Machine Platform enabled in Windows features, still get the message.
Do I need Hyper-V enabled? Do I need Windows Hypervisor Platform?
Edit: no, enabling these 2 didn't solve it either.
Edit 2: running bcdedit /set hypervisorlaunchtype auto start and reboot seems to have worked for me. So maybe I did need Hyper-V and/or Hypervisor Platform enabled, but it doesn't tell you anything useful.

This worked for me as well, thank you!

None of them worked for me. I am running WSL2 on Windows 10 VM on proxmox with nested virtualization enabled. Task Manager on Windwows does show Virtualization: Enabled. All the program features are enabled as well. And I did all the steps mentioned above. Still doesn't work. Any ideas?

NvkAnirudh · 2020-12-27T06:13:29Z

$ wsl --set-default-version 1

This one solved it for me.

Hi @ktmn ,
Windows Subsystem for Linux or #WSL is for me and I'm aware this issue was closed. I got the following error after
Upgrading #WSL Windows Subsystem for #Linux on Windows 10 Professional with only bios #Virtualization and not SLAT.
"#0x80370102 the #virtual #machine could not be started because a required feature is not installed."
C:>wsl --set-default-version 1, Set default version 1, resolves the error on my desktop.
The above resolves the error and got me further. Now...
C:>ubunutu.exe
Prompts with new username and password.

This one solved it for me.

This solved my issue too, thanks

keeganparr · 2020-12-28T21:48:40Z

I had to enable the "Virtualize Intel VT-x/EPT or AMD-V/RVI" setting in VMware Workstation under Hardware-->Processors.

dannierl · 2021-01-19T01:57:49Z

running bcdedit /set hypervisorlaunchtype auto start and reboot

This works for me as well.

boobytrap · 2021-01-19T02:32:49Z

Worked for me as well - Thank you.
In my HP laptop, the BIOS option I enabled is called "Virtualization Technology"

FuzzieKiwi · 2021-01-27T20:32:42Z

Hi @ktmn ,

Windows Subsystem for Linux or #WSL is for me and I'm aware this issue was closed. I got the following error after
Upgrading #WSL Windows Subsystem for #Linux on Windows 10 Professional with only bios #Virtualization and not SLAT.

"#0x80370102 the #virtual #machine could not be started because a required feature is not installed."

C:>wsl --set-default-version 1, Set default version 1, resolves the error on my desktop.

The above resolves the error and got me further. Now...

C:>ubunutu.exe
Prompts with new username and password.

Didn't realize my new mobo had virtualization disabled by default.

talesmgodois · 2021-02-12T02:44:25Z

dumb question, in my case, this is happening inside a vm... Can this work?

My scenario: I have a manjaro machine, which uses virtualbox to run a windows machine. I am trying to install a linux subsystem in this vm, should this work? I know that It might be too nestled

nameldk · 2021-02-12T03:20:11Z

Edit 2: running bcdedit /set hypervisorlaunchtype auto start and reboot seems to have worked for me. So maybe I did need Hyper-V and/or Hypervisor Platform enabled, but it doesn't tell you anything useful.

Thanks a lot. It's worked for me.

Varrions · 2021-03-20T08:59:36Z

"The Virtual machine could not be started because a required feature is not installed"

How about make the message say which feature is not installed.

I got Virtualization enabled in BIOS, Windows Subsystems for Linux and Virtual Machine Platform enabled in Windows features, still get the message.
Do I need Hyper-V enabled? Do I need Windows Hypervisor Platform?

Edit: no, enabling these 2 didn't solve it either.

Edit 2: running bcdedit /set hypervisorlaunchtype auto start and reboot seems to have worked for me. So maybe I did need Hyper-V and/or Hypervisor Platform enabled, but it doesn't tell you anything useful.

Thank you so much, it worked.

kelli217 · 2021-04-01T17:50:19Z

I am also having this nonspecific error when I try to get WSL working. I've tried several different distros, turned on all the parts of various virtualization features and virtual machines, and it still gives me this problem. I think my computer is just too limited.

Processor Intel(R) Celeron(R) CPU N2930 @ 1.83GHz, 1827 Mhz, 4 Core(s), 4 Logical Processor(s)

I think this processor just doesn't support Hyper-V. The BIOS settings have virtualization turned on, verified repeatedly, and still I get:

Hyper-V - Virtualization Enabled in Firmware No

So at this point, I think it's just because my computer is a low-end machine aimed at the education market and just doesn't have the capability to do this. I guess I'll just stick to switch-booting.

jfreeman2 · 2021-06-22T23:08:06Z

@gclair no worries...thanks for your help! Going to get in touch with someone at Microsoft to see if they can provide a solution. There's a chance that my specific form of this issue comes from hardware incompatibility, but I have no idea. I'll send a message out to this thread if I can find a solution.

Dalot · 2021-06-30T10:07:43Z

Tried everything above, one by one, nothing worked for me.

udaybais · 2021-07-08T03:42:03Z

firstly ,

open windows feature turn on or off.
turn of the above two.(hypervisor and virtualizations)
restart device.
again open and turn on both.
restart
It worked in my case.
problem happened because i used BLUESTACKS EMULATOR . emulator is not opening now. emulator of kali
definitely kali is better

farshidhss · 2021-07-08T12:31:13Z

"The Virtual machine could not be started because a required feature is not installed"

How about make the message say which feature is not installed.

I got Virtualization enabled in BIOS, Windows Subsystems for Linux and Virtual Machine Platform enabled in Windows features, still get the message.
Do I need Hyper-V enabled? Do I need Windows Hypervisor Platform?

Edit: no, enabling these 2 didn't solve it either.

Edit 2: running bcdedit /set hypervisorlaunchtype auto start and reboot seems to have worked for me. So maybe I did need Hyper-V and/or Hypervisor Platform enabled, but it doesn't tell you anything useful.

This is the only thing that worked for me.

veekthoven · 2021-07-16T22:34:17Z

This works for me too!

Hi @ktmn ,

Windows Subsystem for Linux or #WSL is for me and I'm aware this issue was closed. I got the following error after
Upgrading #WSL Windows Subsystem for #Linux on Windows 10 Professional with only bios #Virtualization and not SLAT.

"#0x80370102 the #virtual #machine could not be started because a required feature is not installed."

C:>wsl --set-default-version 1, Set default version 1, resolves the error on my desktop.

The above resolves the error and got me further. Now...

C:>ubunutu.exe
Prompts with new username and password.

JacobDrivers · 2021-10-07T00:20:10Z

wsl --set-default-version 1 Worked for me.
Had this issue. I previously had tried out WSL2, disabled the feature/uninstalled, and wanted to have WSL again, but without enabling hypervisor (Which is required for WSL2) because I use VMware a lot. I guess it had remembered me setting the default to WSL2. So, the fix for me was wsl --set-default-version 1.

They need to add WHY to the error. It would be simple to code in what requirement is missing, or if WSL is set differently. Would help a lot! Thanks.

Bitcents · 2021-11-15T19:50:40Z

I faced a similar problem today. I used WSL 2 for a long time, but had to disable SVM and Hyper-V as my work required me to use VMWare for some time. The project was finished yesterday and so I decided to reinstall Ubuntu. This is when the 0x80370102 was thrown. I reactivated Hyper-V, but forgot to re-enable SVM; this obviously led to some headache. Re-enabling SVM, however, fixed the problem. Hope this helps.

Umisyus · 2021-11-16T23:06:31Z

@Bitcents Hello, what is "svm"? is it a windows feature or a hardware feature? I'm having this issue as above. wsl2 will not work

WslRegisterDistribution failed with error: 0x80370102
Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.
I am believe that I have VT-x Virtualization enabled as Virtualization is showing Enabled in the Task Manager, but there is no option in BIOS for setting that for some reason. Thanks.

Umisyus · 2021-11-16T23:25:46Z

"Secure Virtual Mode"

Bitcents · 2021-11-17T00:59:42Z

@Bitcents Hello, what is "svm"? is it a windows feature or a hardware feature? I'm having this issue as above. wsl2 will not work

WslRegisterDistribution failed with error: 0x80370102
Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.
I am believe that I have VT-x Virtualization enabled as Virtualization is showing Enabled in the Task Manager, but there is no option in BIOS for setting that for some reason. Thanks.

Hey Umisyus. SVM is for AMD as VT-X is for Intel. If you have it enabled, then the problem with wsl may be from some of the other reasons mentioned above. Have you checked if the required Windows features are also installed?

muradtheOZ · 2021-11-27T17:11:48Z

Hi @ktmn ,

Windows Subsystem for Linux or #WSL is for me and I'm aware this issue was closed. I got the following error after Upgrading #WSL Windows Subsystem for #Linux on Windows 10 Professional with only bios #Virtualization and not SLAT.

"#0x80370102 the #virtual #machine could not be started because a required feature is not installed."

C:>wsl --set-default-version 1, Set default version 1, resolves the error on my desktop.

The above resolves the error and got me further. Now...

C:>ubunutu.exe Prompts with new username and password.

Thanks This works for me also

Umisyus · 2021-12-17T03:33:59Z

Realized that I needed to update my system and WSL2 started working after updating Windows.

lesniewskii · 2021-12-17T13:37:16Z

To enable virtualization on AMD u should do this at BOIS
(Advanced → CPU Configuration → SVM → Enable)

maysammansoury · 2021-12-25T10:02:29Z

Hi @ktmn ,
Windows Subsystem for Linux or #WSL is for me and I'm aware this issue was closed. I got the following error after Upgrading #WSL Windows Subsystem for #Linux on Windows 10 Professional with only bios #Virtualization and not SLAT.
"#0x80370102 the #virtual #machine could not be started because a required feature is not installed."
C:>wsl --set-default-version 1, Set default version 1, resolves the error on my desktop.
The above resolves the error and got me further. Now...
C:>ubunutu.exe Prompts with new username and password.

Thanks This works for me also

Thanks bro, It works for me as well

MadinaBonuAlisherova · 2022-02-14T13:00:44Z

I had a similar problem on when installing on my new system. I checked my BIOS @craigloewen-msft as mentioned. The first time I didn't find anything but after doing a bit more research I tried turning on SVM in the BIOS and it worked. (I also turned on the Windows Hypervisor setting in Windows Features)

(Advanced → CPU Configuration → SVM → Enable)

This is the case for AMD systems. Apparently it is different for Intel based systems.

Hi @ktmn ,

Windows Subsystem for Linux or #WSL is for me and I'm aware this issue was closed. I got the following error after Upgrading #WSL Windows Subsystem for #Linux on Windows 10 Professional with only bios #Virtualization and not SLAT.

"#0x80370102 the #virtual #machine could not be started because a required feature is not installed."

C:>wsl --set-default-version 1, Set default version 1, resolves the error on my desktop.

The above resolves the error and got me further. Now...

C:>ubunutu.exe Prompts with new username and password.

Thank you worked for me

piknik1979 · 2022-02-19T10:35:25Z

Is virtualization enabled in your BIOS? That could be a quick fix.

We're tracking this issue over in #404 and we can help you troubleshoot there!

Hello ! I'm getting the same problem on my Laptop with Windows 10 - however I'm not sure If I can change the virtualisation BIOS. Can you help with it, thanks!

kirannadimpalli · 2022-03-03T06:09:21Z

For this issue follow these steps 💯
🔢 🥇

go to windows PowerShell and run as administrator
paste this wsl --set-default-version 1
open Ubuntu again and check for error issue is resolved
Thank me later 👍🏻

numeralz · 2022-03-10T21:29:02Z

If anyone else is still struggling with this, and are tired of seeing "Enable virtualization in BIOS" because it's enabled:

For me, there was a hunter1.sys driver, which I believe was installed as part of an anti-cheat mechanism from some Steam game I had installed recently.

How I discovered it:
Windows Security > Device Security > Memory Integrity > ON

Gives me some error of a conflicting driver:
hunter1.sys

I found the hunter1.sys, deleted it, rebooted. BINGO. WSL 2 now works as if nothing had ever broke -.-

ARezaK · 2022-03-29T14:18:14Z

Deleting hunter1.says fixed it (comes from pubg)

shrujandev · 2022-04-01T00:19:35Z

Hi @ktmn ,

Windows Subsystem for Linux or #WSL is for me and I'm aware this issue was closed. I got the following error after Upgrading #WSL Windows Subsystem for #Linux on Windows 10 Professional with only bios #Virtualization and not SLAT.

"#0x80370102 the #virtual #machine could not be started because a required feature is not installed."

C:>wsl --set-default-version 1, Set default version 1, resolves the error on my desktop.

The above resolves the error and got me further. Now...

C:>ubunutu.exe Prompts with new username and password.

This solution worked for me
For some of the users, the Virtualization is already turned on but still, it gives you an error a simple fix would be to set the wsl version to 1
1: run your powershell in administrator mode
2: run the command wsl --set-default-version 1
3: try running the linux you installed from windows store

arnabbiswas1 · 2022-09-23T06:21:04Z

$ wsl --set-default-version 1 worked for me. This basically sets the WSL version to 1 instead of 2. There are a few specific scenarios where you might prefer using WSL 1 compared to WSL 2 (Microsoft documentation)

Don't enable Hyper-V unless it's needed, since it has other consequences. For me, when hyper-v is enabled:

I was not able to start my Ubuntu VM on Virtual Box
My ubuntu distribution on WSL was not getting connected to internet (when behind corporate firewall: ZScaler). See the issue here.

bogdan-panteleev · 2022-09-29T18:36:29Z

why the issue is closed? It is not solved and has must not be closed. Only downgrade to WSL 1 worked for me. Please create good error messages

ssbarnea · 2022-10-24T14:26:20Z

Any hints on how to enable this on Azure machines?

Update: Apparently only D and V machines starting with v3 have nested virtualization support, and that is not an easy to find information at all.

Gaurav8604 · 2022-10-25T14:40:09Z

Following instructions on https://docs.microsoft.com/en-us/windows/wsl/wsl2-install#feedback with a fairly clean install of Build 18922

enabled The VMPlatform, reboot

enabled wsl, reboot

wsl set-default-verion 2

Install Ubuntu from store - https://aka.ms/wslstore as directed by wsl -l -v

Launch Ubuntu

Get the above error.

wsl --set-default-version 1

This worked for me

sonrad10 · 2023-03-26T22:41:32Z

I was getting this error when trying to install Kali. I found this page which fixed it for me:

https://www.kali.org/docs/wsl/win-kex/

The key commands are:

dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart

Followed by a restart :)

LukasJerabek · 2023-05-03T21:21:19Z

On vmware windows virtual machine I had to go to setting of virtual machine, click on processors and enable Virtualize Intel VT-x/EPT or AMD-V/RVI. After that I could check hyperV in windows features (that were greyed out before). Reboot and than I got rid of the anoying error.

QuinntonCarter · 2023-08-17T17:17:05Z

I had a similar problem on when installing on my new system. I checked my BIOS @craigloewen-msft as mentioned. The first time I didn't find anything but after doing a bit more research I tried turning on SVM in the BIOS and it worked. (I also turned on the Windows Hypervisor setting in Windows Features)

(Advanced → CPU Configuration → SVM → Enable)

This is the case for AMD systems. Apparently it is different for Intel based systems.

This worked for me, I run an AMD CPU. Thank you

NeonWizard · 2023-11-06T02:23:35Z

Still the same issue 4 years later.

SVM enabled
Virtualization enabled
HyperV installed
Virtual Machine Platform installed
Windows Hypervisor Platform installed
Windows Subsystem for Linux installed
Windows updated
wsl.exe --install --no-distribution
bcdedit /set hypervisorlaunchtype auto start
Many reboots

Nothing has worked. This started happening a couple days after I killed a docker backend process because it was memory leaking really bad (20+ GB). Next time I restarted, WSL started giving this error.

craigloewen-msft closed this as completed Jun 27, 2019

craigloewen-msft added the duplicate label Jun 27, 2019

SteveALee mentioned this issue Jun 28, 2019

Cannot upgrade to version 2 even when Virtual Machine Platform is enabled #404

Closed

coolaj86 mentioned this issue Sep 15, 2020

WSL Doc Cleanup webinstall/webi-installers#114

Open

This was referenced Sep 23, 2022

WSL2 DNS issues microsoft/WSL#5256

Closed

No network access from WSL/Ubuntu microsoft/WSL#7141

Open

Error 0x80370102 The Virtual machine could not be started because a required feature is not installed .... #436

Error 0x80370102 The Virtual machine could not be started because a required feature is not installed .... #436

Comments

SteveALee commented Jun 27, 2019 • edited Loading

craigloewen-msft commented Jun 27, 2019

SteveALee commented Jun 28, 2019

blackmasks commented Sep 2, 2020

MJEND7 commented Sep 3, 2020 • edited Loading

ManoloMoraes commented Sep 6, 2020

ghost commented Sep 22, 2020

ktmn commented Sep 25, 2020 • edited Loading

kscott5 commented Sep 27, 2020

MJEND7 commented Sep 28, 2020 via email

thomas-griffiths commented Oct 12, 2020

12729582 commented Oct 15, 2020

mtshikomba commented Oct 16, 2020 • edited Loading

pluc commented Dec 3, 2020

WhiteZorin commented Dec 14, 2020

ghost commented Dec 15, 2020

DarkChocolate commented Dec 18, 2020

imperialguy commented Dec 24, 2020

NvkAnirudh commented Dec 27, 2020

keeganparr commented Dec 28, 2020

dannierl commented Jan 19, 2021

boobytrap commented Jan 19, 2021

FuzzieKiwi commented Jan 27, 2021

talesmgodois commented Feb 12, 2021

nameldk commented Feb 12, 2021

Varrions commented Mar 20, 2021

kelli217 commented Apr 1, 2021

jfreeman2 commented Jun 22, 2021

Dalot commented Jun 30, 2021

udaybais commented Jul 8, 2021

farshidhss commented Jul 8, 2021

veekthoven commented Jul 16, 2021 • edited Loading

JacobDrivers commented Oct 7, 2021

Bitcents commented Nov 15, 2021

Umisyus commented Nov 16, 2021

Umisyus commented Nov 16, 2021

Bitcents commented Nov 17, 2021

muradtheOZ commented Nov 27, 2021

Umisyus commented Dec 17, 2021

lesniewskii commented Dec 17, 2021

maysammansoury commented Dec 25, 2021

MadinaBonuAlisherova commented Feb 14, 2022

piknik1979 commented Feb 19, 2022 • edited Loading

kirannadimpalli commented Mar 3, 2022 • edited Loading

numeralz commented Mar 10, 2022

ARezaK commented Mar 29, 2022

shrujandev commented Apr 1, 2022

arnabbiswas1 commented Sep 23, 2022 • edited Loading

bogdan-panteleev commented Sep 29, 2022

ssbarnea commented Oct 24, 2022 • edited Loading

Gaurav8604 commented Oct 25, 2022

sonrad10 commented Mar 26, 2023

LukasJerabek commented May 3, 2023

QuinntonCarter commented Aug 17, 2023

NeonWizard commented Nov 6, 2023

SteveALee commented Jun 27, 2019 •

edited

Loading

MJEND7 commented Sep 3, 2020 •

edited

Loading

ktmn commented Sep 25, 2020 •

edited

Loading

mtshikomba commented Oct 16, 2020 •

edited

Loading

veekthoven commented Jul 16, 2021 •

edited

Loading

piknik1979 commented Feb 19, 2022 •

edited

Loading

kirannadimpalli commented Mar 3, 2022 •

edited

Loading

arnabbiswas1 commented Sep 23, 2022 •

edited

Loading

ssbarnea commented Oct 24, 2022 •

edited

Loading