Hyper-v is installed -- NO IT ISNT ;-)

Docker Desktop
1

I’m having trouble with Docker Toolbox 1.11.2 under Windows 10.

It did previously work.
I decided to instead try the new “docker for windows”, but unfortunately Hyper-V didn’t play nicely with some other VMs I needed to run for other work, so I’ve decided to go back to docker for windows.

However having removed hyper-v (from add/remove windows features), and with hypervisorlaunchtype-Off in bcdedit the script is still thinking hyper-v is installed

What check is docker toolbox using?

The workaround to pass --virtualbox-no-vtx-check worked ok, but I shouldn’t have needed it since Hyper-V was both removed using add/remove, and the hypervisorlaunchtype was set to disable it?

Expected behavior

Docker Quickstart Terminal launches clean on a Windows 10 system

Actual behavior

Running pre-create checks…
Error with pre-create check: "Hyper-V is installed. VirtualBox won’t boot a 64bits VM when Hyper-V is activated. If it’s installed but deactivated, you can use --virtualbox-no-vtx-check to try anyways"
Looks like something went wrong in step ´Checking if machine default exists´… Press any key to continue…

Information

hypervisorlaunchtype=Off
Hyper-V is not ticked in add/remove optional windows features

Steps to reproduce the behavior

Suspected but not gone through the loop again on this:

  1. …enable hyper-v using add/remove optional windows features
  2. …reboot
  3. remove hyper-v using add/remove optional windows features
  4. reboot
  5. fails as described here
2

Thanks for reporting. Since this is strictly speaking a Toolbox problem, could I get you to open an issue there?

3

Experiencing same issue. Please advise.

4

I am also experiencing the same issue, almost 2 years after the first post.

I let Docker for Windows install Hyper-V on a server that was working pretty well with Docker Toolbox to try it out. After seeing too many issues with the blasted Linux containers failing to boot due to TSC timeouts, I uninstalled DfW and Hyper-V to go back to Toolbox. Now I can’t get that running, again, because Docker Toolbox still sees traces of Hyper-V after I’ve uninstalled it and its support tools.

I’m very disappointed to see that this problem has been around for so long. :frowning: