Docker for Windows error: "Hardware assisted virtualization and data execution protection must be enabled in the BIOS"

docker toolbox
docker hub
docker desktop for windows
docker for windows download without login
install docker on windows server 2019
docker desktop for windows server 2016
docker prerequisites
docker desktop logs

I've installed Docker and I'm getting this error when I run the GUI:

Hardware assisted virtualization and data execution protection must be enabled in the BIOS

Seems like a bug since Docker works like a charm from the command line, but I'm wondering if anyone has a clue about why this is happening?

Before you ask, yes, I've enabled virtualization in the BIOS and the Intel Processor Identification Utility confirms that it's activated. Docker, docker-machine and docker-compose all work from the command line, Virtualbox works, running Docker from a Debian or Ubuntu VM works.

There's just this weird issue about the GUI.

My specs:

  • Windows 10 Pro x64 Anniversary Edition
  • Intel core i5-6300HQ @ 2.30GHz

If the features described are enabled the problem is with Hyper-V that is disabled or Hypervisor agent not running

SOLUTION A (If Hyper-V is totally disabled or not installed)

  1. Open PowerShell as administrator and

  2. Enable Hyper-V with

    dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All

SOLUTION B (If Hyper-V feature is already enabled but doesn't work)

Enable Hypervisor with

bcdedit /set hypervisorlaunchtype auto

Now restart the system and try again.

SOLUTION C

If the problem persists probably Hyper-V on your system is corrupted, so

  1. Go in Control Panel -> [Programs] -> [Windows Features] and completely uncheck all Hyper-V related components. Restart the system.

  2. Enable Hyper-V again. Restart.

NOTE 1:

Hyper-V needs hardware virtualization as prerequisite. Make sure your PC supports it, if yes and still won't work there is the possibility your BIOS is not configured correctly and this feature is disabled. In this case, check, enable it and try again. The virtualization features could be reported under different names according the platform used (e.g if you don't see any option that uses virtualization label explicitly, on AMD you have to check SVM feature state, on Intel the VT-x feature state).

NOTE 2:

Hyper-V can be installed only with some version e.g.:

Windows 10 Enterprise; Windows 10 Professional; Windows 10 Education.

Hyper-V cannot be installed on cheaper or mobile Windows versions e.g.:

Windows 10 Home; Windows 10 Mobile; Windows 10 Mobile Enterprise.

Error trying to install Docker for Windows, Has anyone had any problems with Launching Docker for Windows lately, haven'​t ran the hello-world right after the installation, and got the error messages. For example windows 10 home will not run docker for windows. Check if the host is Windows 10 Home edition. If it is, go download and install Docker Toolbox for Windows, which includes up-to-date Docker and some environment components. Docker for Windows relies on native Hyper-V to create virtual machine. But Win 10 Home edition does not have it.

Below is working solution for me, please follow these steps

  1. Open PowerShell as administrator or CMD prompt as administrator

  2. Run this command in PowerShell-> bcdedit /set hypervisorlaunchtype auto

  3. Now restart the system and try again.

cheers.

Docker for windows won't launch, Be able to run Docker on Windows 10 without error described further. Actual behavior. Unable to create: The running command stopped because  In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running. in an elevated powershell, tried instructions on https://www.edureka.co/community/51478/how-to-start-a-docker-daemon-manually, but "dockerd not recognized" was all i could see.

I uninstalled Intel HAXM and VirtualBox, Docker now runs

An error occurred trying to run Docker for Windows · Issue #3181 , ERROR: Couldn't connect to Docker daemon. You might need to start Docker for Windows. Docker is running Docker version 19.03.4, build  Docker on Windows error: “docker pull redis” +1 vote I've installed Docker EE for Windows Server 2016 and was able to pull and run the hello-world example.

Open the task manager and click on the performance tab. If virtualization is disabled, you need to follow the instructions here to enable it: https://blogs.technet.microsoft.com/canitpro/2015/09/08/step-by-step-enabling-hyper-v-for-use-on-windows-10/

ERROR: Couldn't connect to Docker daemon. You might need to , Bug reports for Docker Desktop for Windows. Contribute to <host> not set in Windows: 【error during connect: Post http://<host>:2375/v1.40/containers/】. After running docker-compose pull --ignore-pull-failures I get this error: ERROR: Couldn&#39;t connect to Docker daemon. You might need to start Docker for Windows. Docker is running Docker vers

For me, all I had to do it uninstalling VMware.

Docker now is running

Issues · docker/for-win · GitHub, After installing Docker for Windows (recently renamed to Docker Desktop) I could not get the basic command docker run hello-world working. Are you using Windows 10 Pro or Enterprise? It specifically asks your for Windows 10 Pro or Enterprise.If you are using Windows 10 Home, no matter which build, you cannot use Docker Desktop.

Docker for Windows: fix unauthorized errors, In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker  Expected behavior Docker starts Actual behavior Docker don´t starts with error: [20:31:50.147][HyperV ][Info ] Creating a virtual machine named MobyLinuxVM [20:31:50.163][HyperV ][Info ] Checking for Hyper-V Windows optional feature [20:31:50.178][PowerShell ][Info ] Run script [20:31:52.000][HyperV ][Info ] Hyper-V Windows feature is enabled [20:31:52.026][PowerShell ][Info ] Run script

Troubleshooting Docker for Windows, When its running in windows container it works fine. But if i switch to Linux container getting below error. Os: Windows 10 Docker Desktop: 2.2.0.3. General 🔗 Start Docker when you log in - Automatically start Docker Desktop upon Windows system login. Automatically check for updates - By default, Docker Desktop automatically checks for updates and notifies you when an Expose daemon on tcp://localhost:2375 without TLS - Click this option to

Getting error while switching to Linux Container in docker, In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker  It shows you how to use a MusicStore application with Windows containers. Docker Container Platform for Windows articles and blog posts on the Docker website. Install Docker Desktop on Windows. Double-click Docker Desktop Installer.exe to run the installer.

Comments
  • @Julien try to unistall and reinstall Hyper-V see the edit
  • In case anyone else has a similar issue, I had recently installed Bash on Ubuntu on Windows (which uses Hyper-V). After I uninstalled it and then followed the steps in this answer, Docker worked for me!
  • I'm running Windows 10 in Bootcamp on MacBook Pro. I had the same problem. I first tried dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All but didn't seem to solve it, so then I tried bcdedit /set hypervisorlaunchtype auto and Docker is now running for me.
  • This wasn't the issue in my case, it was the fact that the virtuallization was disabled in the BIOS. I had to enable the virtualization feature in the security tab in the BIOS, which caused docker to work immidiately afterwards.
  • Solution B worked for me after upgrading/switching my SSD via the Samsung SSD Migration Tool.
  • Worked for me, without uninstalling Intel HAXM, but now vmware no more works :(
  • I had installed HAXM for Android Development, and had to disable HyperV. Removing it restored Docker for Windows. Now if anyone can tell me how to get the Android Emulator and Docker to coexist?
  • itwriting.com/blog/…
  • For me it didn't work even when Hyper-V was enabled and BIOS configured; I was still getting that error. Disabling Hyper-V + restarting Windows and then enabling it back on solved the problem for me.