I’ve been encountering this issue, and as far as I can tell, it has something to do with how Windows starts (or doesn’t start) either the Hyper-V service, its hypervisor, or the Windows Hypervisor Platform. I can’t precisely say when this has started happening, but my best guess is 2 to 3 weeks ago, while I was still using Docker 3.6. I use Docker, VMWare, and WSL. The behavior of the virtualization services is erratic, to say the least, and not necessarily Docker’s fault, but I’m writing this to try and help investigating.
I’ve witnessed the following scenarios, all starting with all applications off.
- Docker says it can’t enable the Hyper-V service. I start a WSL window, then VMWare, successfuly. Then I try starting Docker, now it works (simultaneously with WSL+VMWare).
- Docker starts fine out of the blue. VMWare suddenly doesn’t start virtual machines. WSL works.
- Today, VMWare started fine. Docker didn’t start the first time with the usual error message. After a few minutes, I tried again, and it worked.
My best guess is that a Windows update changed something about how one of the necessary virtualization services actually fires up (or doesn’t), and it’s borking Docker and VMWare.
i have already enabled virtualization in my BIOS, and also enable it in Windows feature
furthermore, the android emulator with android studio working well, but when i try to run Docker for windows, i encounter this problem?
i don’t know where the problem is?
asked Jun 26, 2020 at 10:27
Osama MohammedOsama Mohammed
2,19110 gold badges28 silver badges51 bronze badges
2
You need to autostart the hypervisor at startup.
Open a Powershell as Admin.
Paste the line:
bcdedit /set hypervisorlaunchtype auto
Then the hypervisor will start at the next boot and it should work.
For future information see:
https://d3v.one/windows-10-changing-hyper-v-support-at-boot-time/
answered Jun 26, 2020 at 13:52
2
In my case this worked for me More concrete steps:
got to ‘Apps and Features.
Select Programs and Features on the right under related settings.
Select Turn Windows Features on or off.
Unselect Hyper-V and click OK. (So I disable it)
Restart computer
After restart I go to:
‘Apps and Features.
Select Programs and Features on the right under related settings.
Select Turn Windows Features on or off.
select Hyper-V and click OK. (So I enable it)
Computer restart
After restart, then docker worked correctly.
answered Aug 31, 2021 at 4:55
0
What worked for my team was to make sure Containers and Hyper-V was enabled, then making sure Docker Desktop was updated.
answered Sep 16, 2021 at 13:53
1
I tried both options described here without success:
- Unchecked
Hyper-VinWindows feature(reboot), checked again(reboot) - Run
bcdedit /set hypervisorlaunchtype autoas Administrator in Powershell and reboot the PC
SOLUTION: What solved the issue for me was to update the Docker Desktop version (from 3.6 to 4.3)
answered Dec 15, 2021 at 14:49
I am a new to Docker. After the installation of Docker Toolbox (OS: Windows 10) I run Docker Quickstart Terminal and in the console I see this:
Running pre-create checks...
Error wirh pre-create check: "Hyper-V is installed. VirtualBox won't boot a 64bits VM when Hyper-V is activated. It it's installed but deactivated, you can use --virtualbox-no-vtx-check to try anyways"
Look like something went wrong in step 'Checking if machine default exists'...
Press any key to continue...
What did I do wrong? All checking of system and install steps are taken from here.
Thank you very much for your help!
Moshisho
2,7211 gold badge22 silver badges37 bronze badges
asked Apr 27, 2016 at 9:39
Denis StarkovDenis Starkov
8151 gold badge6 silver badges10 bronze badges
7
Hyper-V and VirtualBox are conflicting each other.
You can either uninstall Hyper-V or run
docker-machine create -d virtualbox --virtualbox-no-vtx-check test
Source
answered Apr 27, 2016 at 9:49
4
Docker supports Hyper-V as the driver
You need to perform the following steps:
-
Create a virtual switch, refer to this article on how to do that
-
Create a docker machine using that network switch and hyper-V driver.
docker-machine create -d hyperv --hyperv-virtual-switch "name of the virtual switch created above" default
phuclv
35.9k13 gold badges146 silver badges455 bronze badges
answered Sep 5, 2016 at 6:10
curiousgeekcuriousgeek
8466 silver badges11 bronze badges
4
I got the same error when I installed Docker Toolbox on my Windows 10 machine.
Solution:
- Install Docker Community Edition (not Docker Toolbox)
- Enable Hyper-V
Open Control Panel -> System and Security -> Programs (left panel) -> Turn Windows features on or off -> Check the Hyper-V box
As of 2017’s Win 10, if you don’t have Hyper-V option, then your Windows OS is not Enterprise Edition. Also, Docker seems to work a lot better on Intel processors (not AMD).
- Add C:Program FilesDockerDockerresourcesbin to Path in Environmental Variables.
- Open Git Bash and type
docker-compose upand now that command should work.
If you don’t have GitBash, please download it.
phuclv
35.9k13 gold badges146 silver badges455 bronze badges
answered Nov 22, 2017 at 18:01
GeneGene
10.6k1 gold badge64 silver badges57 bronze badges
1
I was having the same issue, and this blog post solved it. The author runs you through the steps of adding the --virtualbox-no-vtx-check flag to the docker shell script.
Virtualbox and Hyper-V don’t play well together. I am NOT the author.
answered Jun 28, 2016 at 21:58
cph2117cph2117
2,6111 gold badge26 silver badges41 bronze badges
0
I set the Hyper-V off using windows feature on off and it worked for me.
answered Aug 25, 2017 at 9:09
1
See if when you run:
docker-machine create -d hyperv --hyperv-virtual-switch "Virtual Switch" default
you get Error with: pre-create check: "Hyper-V PowerShell Module is not available"
If so just enable in Docker(icon on your desktop)->settings->expose daemon on TCP …
JuanCrg90
1,00614 silver badges24 bronze badges
answered Jun 26, 2018 at 14:27
1
You need to disable Hypervisor to check new application that use VT-x before the virtual machine launch:
-
Open the command prompt as Administrator
-
Run
bcdeditto check hypervisor status: -
Check hypervisor launch type.
-
If is set to auto then disable it:
bcdedit /set hypervisorlaunchtype off -
Reboot host machine and launch VirtualBox again
After performing above steps I opened again Docker Quickstart terminal and it is working fine.
double-beep
4,84016 gold badges32 silver badges41 bronze badges
answered May 28, 2020 at 15:12
I pressed the Windows Button on keyboard. Typed ‘Hyper-V Manager’. It opened the ‘Hyper-V Manager’. Then I right clicked on my machine name. There was an option to ‘stop’. I selected this option. It stopped the ‘Hyper-V’ on my machine and then Kitematic worked fine, i.e., it download the hello-world-nginx and displayed the web page.
NOTE: This is strange and I am not sure why. Once I have done above steps, now when I restarted the Hyper-V using Hyper-V Manager, Kitematic is still working and downloading images. Can anybody comment why it is now still working when Hyper-V is also running ? Thank you.
Good
Ali Ahsan
answered Dec 15, 2018 at 11:18
The solution as suggested by @Gene is correct and works perfectly if:
- One has windows pro edition
- Both Hyper-V Management Tools and Hyper-V Platform are enabled
Sometime this isn’t always the case; here is what to do:
Check Windows Edition:
To check which version right click on Windows key and select System.
Scroll down to Windows specifications and look at [Edition]
Check Hyper-V Platform (virtualisation)
For Hyper-V Platform to be enabled one must turn on virtualisation; normally this is done via the BIOS.
On HP laptop one this is done from the BIOS.
- On start-up click Ctrl+F10
- Press the right arrow key to System Configuration tab.
- Select Virtualization Technology and then press the Enter key.
- Select Enabled and press the Enter key.
Once these steps are done then:
- Search for Turn Windows features on or off.
- Scroll down to Hyper-V
- Tick this box (Ensure you see a tick NOT a black box which indicates some features not enabled)
Upon restart docker should be running… good luck !!
answered Aug 16, 2019 at 19:06
ItharIthar
4,6154 gold badges38 silver badges38 bronze badges
I am a new to Docker. After the installation of Docker Toolbox (OS: Windows 10) I run Docker Quickstart Terminal and in the console I see this:
Running pre-create checks...
Error wirh pre-create check: "Hyper-V is installed. VirtualBox won't boot a 64bits VM when Hyper-V is activated. It it's installed but deactivated, you can use --virtualbox-no-vtx-check to try anyways"
Look like something went wrong in step 'Checking if machine default exists'...
Press any key to continue...
What did I do wrong? All checking of system and install steps are taken from here.
Thank you very much for your help!
Moshisho
2,7211 gold badge22 silver badges37 bronze badges
asked Apr 27, 2016 at 9:39
Denis StarkovDenis Starkov
8151 gold badge6 silver badges10 bronze badges
7
Hyper-V and VirtualBox are conflicting each other.
You can either uninstall Hyper-V or run
docker-machine create -d virtualbox --virtualbox-no-vtx-check test
Source
answered Apr 27, 2016 at 9:49
4
Docker supports Hyper-V as the driver
You need to perform the following steps:
-
Create a virtual switch, refer to this article on how to do that
-
Create a docker machine using that network switch and hyper-V driver.
docker-machine create -d hyperv --hyperv-virtual-switch "name of the virtual switch created above" default
phuclv
35.9k13 gold badges146 silver badges455 bronze badges
answered Sep 5, 2016 at 6:10
curiousgeekcuriousgeek
8466 silver badges11 bronze badges
4
I got the same error when I installed Docker Toolbox on my Windows 10 machine.
Solution:
- Install Docker Community Edition (not Docker Toolbox)
- Enable Hyper-V
Open Control Panel -> System and Security -> Programs (left panel) -> Turn Windows features on or off -> Check the Hyper-V box
As of 2017’s Win 10, if you don’t have Hyper-V option, then your Windows OS is not Enterprise Edition. Also, Docker seems to work a lot better on Intel processors (not AMD).
- Add C:Program FilesDockerDockerresourcesbin to Path in Environmental Variables.
- Open Git Bash and type
docker-compose upand now that command should work.
If you don’t have GitBash, please download it.
phuclv
35.9k13 gold badges146 silver badges455 bronze badges
answered Nov 22, 2017 at 18:01
GeneGene
10.6k1 gold badge64 silver badges57 bronze badges
1
I was having the same issue, and this blog post solved it. The author runs you through the steps of adding the --virtualbox-no-vtx-check flag to the docker shell script.
Virtualbox and Hyper-V don’t play well together. I am NOT the author.
answered Jun 28, 2016 at 21:58
cph2117cph2117
2,6111 gold badge26 silver badges41 bronze badges
0
I set the Hyper-V off using windows feature on off and it worked for me.
answered Aug 25, 2017 at 9:09
1
See if when you run:
docker-machine create -d hyperv --hyperv-virtual-switch "Virtual Switch" default
you get Error with: pre-create check: "Hyper-V PowerShell Module is not available"
If so just enable in Docker(icon on your desktop)->settings->expose daemon on TCP …
JuanCrg90
1,00614 silver badges24 bronze badges
answered Jun 26, 2018 at 14:27
1
You need to disable Hypervisor to check new application that use VT-x before the virtual machine launch:
-
Open the command prompt as Administrator
-
Run
bcdeditto check hypervisor status: -
Check hypervisor launch type.
-
If is set to auto then disable it:
bcdedit /set hypervisorlaunchtype off -
Reboot host machine and launch VirtualBox again
After performing above steps I opened again Docker Quickstart terminal and it is working fine.
double-beep
4,84016 gold badges32 silver badges41 bronze badges
answered May 28, 2020 at 15:12
I pressed the Windows Button on keyboard. Typed ‘Hyper-V Manager’. It opened the ‘Hyper-V Manager’. Then I right clicked on my machine name. There was an option to ‘stop’. I selected this option. It stopped the ‘Hyper-V’ on my machine and then Kitematic worked fine, i.e., it download the hello-world-nginx and displayed the web page.
NOTE: This is strange and I am not sure why. Once I have done above steps, now when I restarted the Hyper-V using Hyper-V Manager, Kitematic is still working and downloading images. Can anybody comment why it is now still working when Hyper-V is also running ? Thank you.
Good
Ali Ahsan
answered Dec 15, 2018 at 11:18
The solution as suggested by @Gene is correct and works perfectly if:
- One has windows pro edition
- Both Hyper-V Management Tools and Hyper-V Platform are enabled
Sometime this isn’t always the case; here is what to do:
Check Windows Edition:
To check which version right click on Windows key and select System.
Scroll down to Windows specifications and look at [Edition]
Check Hyper-V Platform (virtualisation)
For Hyper-V Platform to be enabled one must turn on virtualisation; normally this is done via the BIOS.
On HP laptop one this is done from the BIOS.
- On start-up click Ctrl+F10
- Press the right arrow key to System Configuration tab.
- Select Virtualization Technology and then press the Enter key.
- Select Enabled and press the Enter key.
Once these steps are done then:
- Search for Turn Windows features on or off.
- Scroll down to Hyper-V
- Tick this box (Ensure you see a tick NOT a black box which indicates some features not enabled)
Upon restart docker should be running… good luck !!
answered Aug 16, 2019 at 19:06
ItharIthar
4,6154 gold badges38 silver badges38 bronze badges