Failure to initiate Hyper-V Host Compute Service (vmcompute)

With this functionality, you can utilize a virtual machine as a Hyper-V host and produce virtual machines within the virtualized host. To learn more about virtual machine versions, refer to the guide on updating virtual machine versions in Hyper-V on either Windows 10 or Windows Server 2016.

On my Windows 10 computer, I’m attempting to set up Docker using WSL 2. Although I initially believed it would be straightforward, I’ve been unable to get it running after two days of effort.

The issue I’m currently investigating relates to the inability to install a Linux distribution through the Windows Store. Specifically, an error message is being displayed.

Encountered error 0x80370102 while attempting to register WslRegisterDistribution. This error indicates that a required feature is missing, preventing the virtual machine from starting.

Following additional attempts to resolve the issue, it appears that the inability to execute the Hyper-V Host Compute Service is the likely cause.

 PS C:Usersjjj> 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 relies on the Windows Container Isolation service, but the latter could not initiate due to an error stating that the specified file cannot be located.

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:


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.


The latest version of Windows 10, specifically build 19042.964, is now available.



Thanks for your posting!

From the details you provided, it appears that you have explored various methods and here are my observations.

Following the disabling of CFG override system settings for vmcompute.exe, did you use PowerShell to start vmcompute via “net start vmcompute” or start the Hyper-V Host Compute Service through the system Services app? After doing so, have you tried rebooting your computer and reopening Hyper-V? It’s worth noting that occasionally this method may not suffice, and you may also need to execute these commands.

Navigate to the Docker directory in the Program Files folder by entering “cd ‘C:Program FilesDockerDocker'” in the command prompt. Then, execute the command “./DockerCli.exe -SwitchDaemon” to switch the Docker daemon.

This blog covers a method that can help resolve the issue you are facing.

This link directs to a Stack Overflow post about an issue with starting Docker on a Windows system.

The accuracy and effectiveness of the information hosted in the given link cannot be guaranteed by Microsoft, as it is posted by a third party.

Additionally, in case you have attempted this approach without success, would you be able to provide me with any error messages or codes that were displayed? This information would be beneficial.

The blogger in the article did not utilize the “disabled CFG override system settings of vmcompute.exe” method, but their system version did not include the container service. This could serve as a similar test for you to investigate your own issue.

Refer to the issue #945 in the Virtualization-Documentation repository on GitHub by MicrosoftDocs.

Kindly be informed that the information shared in the provided link is being hosted by a third party. Microsoft cannot assure the precision and efficiency of the information.

It appears that the order of commands you used in steps 5 and 6 could be the reason for the encountered error message. In order to resolve this issue, you should disable the hyper-v feature on your computer and restart the Hyper-V installation. The correct sequence of commands to run after this should be followed.

By executing the “systeminfo” command in the command prompt, you can confirm the host’s readiness for virtualization. To enable the hypervisor in bcdedit, execute “bcdedit /set {current} hypervisorlaunchtype auto”. Then, run bcdedit once more to ensure that the hypervisor is enabled on your computer. Finally, after rebooting the server, virtual machines started without any problems.

This is the article that provides further information on the commands.

Check out this link for a solution to the problem of being unable to start a virtual machine due to the hypervisor not running:

Kindly be advised that the information provided in the provided link is being hosted by a third-party source. Microsoft cannot assure the precision and efficacy of the said information.

Regarding the Windows Container Isolation service that you mentioned, it appears to be the root cause of your issue. To provide you with a better understanding of this service and how it relates to your problem, I have discovered an article that may be of assistance.

This webpage on Microsoft’s documentation website provides information about version compatibility when deploying containers on Windows operating systems. The page can be found at the following URL:

As I see it, an unsuitable hypervisor may be the cause of Hyper-V’s dysfunction. I will continue to investigate and notify you promptly if I discover any valuable information.

I appreciate your kindness and understanding!



If you find the answer useful, kindly consider clicking on the “Accept Answer” button and giving it an upvote.

In order to receive email notifications for this thread, make sure to refer to our documentation and follow the steps to enable this feature.

Docker can be used on Windows Home Edition by utilizing WSL 2, which does not require Hyper V. For more information, refer to the following link: “Docker Windows and WSL 2”.

Frequently Asked Questions

Posted in Uncategorized