Windows 10 Home X64, I have installed Docker for Windows. Works well.
But Hyper-V, which was installed with Docker conflict with my other software. Want to uninstall.
Uninstallation went well, but after it I still have some leftovers like service: “HV Host Service”, “Hyper-V Heartbeat Service”, 9 services in total with similar names.
How to get rid of them?
You can’t if you want to use Docker on Windows; it requires Hyper-V.
If you no longer want to use Docker, you can disable Hyper-V via OptionalFeatures.exe, which is included with Windows.
Windows 10 Home. There is no such feature as Hyper-V.
SO, I don’t know how Docker managed to install it, but now I can’t uninstall.
I was under the impression that the relevant services fall under “Windows Hypervisor Platform” and “Virtual Machine Platform.” How many times have you rebooted since uninstalling Docker? I’ve noticed that sometimes it takes a cold reboot (shut down, leave computer off for a few seconds, turn back on) to install or uninstall Hyper-V, which I assume is a Windows bug.
I rebooted it several times.
I also used methods, described here
and here
Services still exist 
Installing and uninstalling Docker Desktop on Windows Home has left my machine unusable for use with VirtualBox because the hyper-v was not uninstalled properly. VirtualBox now complains VERR_NEM_VM_CREATE failed. Disable Hyper-V to run virtualization software - Windows Client | Microsoft Docs describes how you determine hyper-v is running and how to disable it. I see from msinfo32.exe I have a hypervisor but because this is Windows Home I have no way to disable it. Docker Desktop should refuse to run on Windows Home rather than trashing it.
Yep, that’s to expected if running the latest 6.1.28 on Windows 10. While patching things up for Windows 11 compatibility, Oracle broke Windows 10 compatiblity. Just re-install VBox 6.1.26 and it will work again. This is lengthly discussed in the Virtualbox forum.
The whole thread went sideways all along:
– Windows Home does not provide the Windows feature Hyper-V
– Windows (all versions) provide the Virtual Machine Platform, which is a lightweigt Hyper-V environment. The services seen on the screenshots above belong to it. Do NOT disable them by yourself. Either enable or disable the feature.
– Windows Subsystem for Linux (WSL2) requires the Virtual Machine Platform to run the Linux Kernel and the user distributions.
You can not enable WSL2 without enabling the Virtual Machine Platform. Even though the Virtual Machine Platform is not Hyper-V per se, it is still enough of Hyper-V under the hood to disturb other virtualization solutions. This is why newer VirtualBox and VMware Workstation versions provide a compatibility mode that can co-exist with Hyper-V, but has a performance penelty. I am running Vbox 6.1.26 and WSL2 side by side without any issues on Windows 10 21H1 Enterprise.
If you want to get rid of the “Hyper-V” components on Windows Home, you have to disable WSL and the Virtual Machine Platform.
This whole response is completly unrelated to docker.
My understanding of this thread was that Docker for Windows was installed on Windows Home and when it is was found to conflict with other virtualization solution it was uninstalled. The hypothesis was that it left left hyper-v installed but there was some confusion about the services for the lightweight hypervisor which may have confused things.
So I was trying to further the hypothesis that full hyper-v was left installed by Docker for Windows as evidenced by the fact that VirtualBox started complained about a hyper-v being present immediately after installing and uninstalling Docker for Window. Other threads indicate the only solution to fixing having installed and uninstalling Docker for Windows on Windows Home is to reinstall Windows. Unfortunately re-installing VirtualBox did not solve the problem. I have moved on to another machine so it is not an immediate problem for me but still feel there may be an outstanding issue with trying to run Docker for Windows on Windows Home or at least uninstalling it.
BTW in my case I never actually installed WSL2 kernel package. I decided after installing Docker for Windows and then realizing that it also needed WSL2 that I would just use a different machine and so uninstalled Docker.
So all I am saying is that if installing and uninstalling Docker for Windows on Windows Home leaves Windows home in a state where it cannot run Virtual Box that is still a problem in search of a solution. Certainly an edge case but not clear what happens if you end up in that situation.
See: VERR_NEM_VM_CREATE_FAILED: What do I do? - virtualbox.org
I don’t use Docker for Desktop at all, as I feel it’s a half-assed solution The only platform Docker was and always will be a first class cititzen is Linux. Any Linux distribution directly supported by Docker will do, regardless whether on baremetal, in a vm or in a WSL2 distro.
I am curious if the DDfW documentation hides the fact that it requires Hyper-V or WSL2 to run? Because once either one of both is installed, I don’t feel its a Docker problem, but rather a Hyper-V or WSL2 problem. Docker always leverages things already available on a platform - its foundation always was more like an orchestrating glue.
I am quite sure that I used WSL2 and Virtualbox side by side on my private laptop as well, which until recently did run Win10 and now runs Win11. And like I wrote I do run WSL2 + VBox on Win10 Enterprise without issue - the full hyper-v feature is also not enabled. Is it possible the virtualization settings are not enabled in your bios?