question

Joms-7122 avatar image
0 Votes"
Joms-7122 asked jiayaozhu-MSFT commented

Hyper-V Host Compute Service (vmcompute) cannot be started.

I'm trying to install Docker with WSL 2 on my Windows 10 machine. I thought it was fairly simple but two days later I'm still struggling to make it work.

I've tracked the problem from not being able to install a Linux Distribution from the Windows Store. I'm getting an error:

WslRegisterDistribution failed with error: 0x80370102 Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.

After some more troubleshooting it is (probably) because I can't run this Hyper-V Host Compute Service:

 PS C:\Users\jjj> Start-Service "Hyper-V Host Compute Service"

 Start-Service : Service 'Hyper-V Host Compute Service (vmcompute)' cannot be started due to the following error: Cannot open vmcompute service on computer '.'.

In Windows Event Viewer I get this:

The Hyper-V Host Compute Service service depends on the Windows Container Isolation service which failed to start because of the following error: The system cannot find the file specified.

I don't know how to solve this cause I can't find any info online. What is Windows Container Isolation and why can't it be found? At this point vmms is working, vmcompute not.

Things I've done:

1.) Enabled SVM Mode in BIOS settings (I was using Virtualbox/Vagrant before so this is enabled already)
2.) Enabled the required Windows Features:

95916-1.png

3.) Installed Linux kernel update package.
4.) Disabled CFG override system settings of vmcompute.exe
5.) Ran bcdedit /set hypervisorlaunchtype auto
6.) Ran systeminfo but getting Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed. It seems like another hypervisor is running. Removing Hyper-V from Windows Features and running this command again I still get the same message. If I removed "Virtual Machines Platform" then the message is gone and the requirements are shown. Here's the weird part though - if I enable Hyper-V again with "Virtual Machines Platform" disabled, the "A hypervisor has been detected." is again displayed, but I still can't start vmcompute!
7.) I've installed HWiINFO and somehow AMD-V is greyed out so it means it's not supported. But I double checked and SVM Mode IS enabled in BIOS. I'm sure that it's enabled because I was using VirtualBox/Vagrant before which are now uninstalled.

System

Windows 10 Version 20H2 build 19042.964

96025-5.png


windows-server-hyper-vwindows-10-hyperv
1.png (34.9 KiB)
5.png (68.1 KiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

I would like to check if your issue has been resolved and if any of the replies here could be of help? If yes, please help accept answer, so that others meet a similar issue can find useful information quickly. If you have any other concerns or questions, please feel free to feedback.

Best Regards,
Joan

0 Votes 0 ·
jiayaozhu-MSFT avatar image
0 Votes"
jiayaozhu-MSFT answered Joms-7122 commented

HI,

Thanks for your posting!

Based on your descriptions, you really have tried many ways, and here is what I have noticed:

1) After you disabled CFG override system settings of vmcompute.exe, did you start vmcompute from powershell net start vmcompute (or alternately start the Hyper-V Host Compute Service from the system Services app) and rebooted your computer and try to open your Hyper-V again? In addition, sometimes the above method is not enough, you need to run these commands as well:

cd "C:\Program Files\Docker\Docker"
./DockerCli.exe -SwitchDaemon

Here is the blog that discuss this method to solve the issue similar to you:

https://stackoverflow.com/questions/50126279/cant-start-docker-on-windows

Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.

Besides, if you have tried this method and did not work, what error messages or codes you can find? It would be helpful if you could offer me any of these error messages or codes.

Here is an article in which the blogger failed to use this method "disabled CFG override system settings of vmcompute.exe" but his or her system version did not add container service. So I guess this can be a comparable test for you to research on your own issue:

https://github.com/MicrosoftDocs/Virtualization-Documentation/issues/945

Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.

2) I think the order that you run your commands in 5) and 6) is not appropriate and that may be the reason you encountered the error message. After disable hyper-v feature on your computer and restart your installation of Hyper-V, the correct order of running commands should be:

-Running systeminfo in command prompt shows that the host is ready for Virtualisation
-Running "bcdedit /set {current} hypervisorlaunchtype auto" to enable hypervisor in bcdedit
-Running bcdedit again to make sure your hypervisor is enabled in your computer
-After rebooting the server virtual machines started with no issues.

Here is the article that explain more about the commands:

https://www.mysysadmintips.com/windows/servers/876-virtual-machine-could-not-be-started-because-the-hypervisor-is-not-running

Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.

3) You mentioned Windows Container Isolation service, and I think this should be the core cause that led to your issue. And I found an article that can help you better understand this service, which can then help you understand your issue:

https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility?tabs=windows-server-20H2%2Cwindows-10-20H2

From my perspective, I guess an incompatible hypervisor prevents Hyper-V from working, I will keep working on this issue and let you know as soon as I find something useful.

Thanks for your support and patience!

BR,
Joan


If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you for the detailed response!

Funnily enough all the links you sent are already purple on my end haha. But I will try everything this weekend because I had to stop in order to continue with my work. The Windows Container Isolation service is really what's popping out to me as well as the cause of the issue.

Having said that I'm also planning to use WSL 2 instead of Hyper-V, but do I have to solve these issues first before I can proceed? That's what brought up all these troubleshooting in the first place. I can't install a Linux distribution in the Windows Store to work with WSL 2. I'm getting an error:

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80370114 Error: 0x80370114 The operation could not be started because a required feature is not installed. Press any key to continue...

And Docker is stuck at Docker Engine is starting...






0 Votes 0 ·

Hi,

Thanks for your patience!

After research with my colleagues, we suppose this issue can be attributed to your AMD Ryzen 7 3700 X. AMD products do somethims have imcompatible issue with Microsoft virtualization. Since most of methods we have tried and your WSL encountered the same issue, I will suggest you to discuss this issue with AMD's technical supporter, to see if they have any helpful ideas about your issue.

Thanks for your support and understanding! And don't forget to help me Accept Answer if you find my reply is helpful. In this way, people who have a similar issue with yours can find their answers more quickly.

Best regards
Joan

0 Votes 0 ·

Hi, just want to say that I had zero issues installing when I reinstalled Windows. So I think this was more of a software issue than a hardware one. I've also signed up for Windows Insider Program's Beta Channel to use build 19403 if that helps others. Thank you!

0 Votes 0 ·
yogyogi avatar image
0 Votes"
yogyogi answered yogyogi edited

You can simple use WSL 2 and docker will work. I am using docker on my windows home edition using wsl 2, home edition does not has hyper v. Please see this link:
Docker Windows and WSL 2


· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

This was actually what I was trying to do before I got into the rabbit hole of this whole mess.. WSL 2 was the plan all along but I can't make Docker run properly. It's stuck at Docker engine is starting.. and I can't even click on the settings because it loads forever.

Installing a Linux distro from the Windows Store also gives me this error:

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80370114 Error: 0x80370114 The operation could not be started because a required feature is not installed. Press any key to continue...

I'm afraid my last option is to just reinstall a fresh copy of Windows 10.

1 Vote 1 ·

I my case it took me some 30 minutes for the operation to complete. I also thought i am stuck but it completed. You should update the window if you haven't done so then download latest version of docker desktop and install it. Then try once again.

You can also use different linux distro like ubantu, kali, check documentation for it. Try with kali.

If everthing fails then reinstall window from recovery drive partition on your drive which is fast.

0 Votes 0 ·