Docker Community Forums

Share and learn in the Docker community.

Installing Docker on Windows 10 Home

My steps:

  1. To install HyperV on Windows Home I used @hessi9 bat commands
  2. To install Docker on Windows Home without having to install a 3rd party product I used @mapk tip (change registry instead of editing installer).

Additional Info: It was necessary only to change the following registry key:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\EditionID which in my case were CoreSingleVersion.

Cheers and thank you all.

Thank you so much @hessi9 and @mapk! I have consolidated this thread into a Gist


i don’t know if this is still an issue for you, but i just had the same problem.

using windows containers (@installation) instead of linux solved the problem for me

Hey guys,
I am having an issue with installing the Hyper-V components… the script is looping forever (it seems finished 100% but I need to close the powershell window to stop it).
I did try to install Docker with checking / unchecking boxes, got to install it, but there was an error at launch again.
Any ideas,

You cannot install Docker for Windows on Windows 10 Home according to the documentation. System Requirements: Windows 10 64bit: Pro, Enterprise or Education (1607 Anniversary Update, Build 14393 or later). … Install a Linux virtual machine (VM) on our Windows OS, and then Install Docker Community on the VM.


We have now released a version of Docker Desktop Edge that allows users of Windows Insider Preview (Win Home 19018 or higher) to use Docker Desktop with WSL 2.
If you are trying this out and have issues feel free to drop issues on the for-win Github Repo!



I had followed @hessi9’s method to install docker. But now that it supports Windows 10 Home, without hyper v, I have been unable to deactivate hyper v, making virtualbox and intel haxm unusable.
I tried Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All and it returns a success but there are hyperv network adapters and hyperv services running in task manager. When I open “Turn features on/off”, hyperv is unticked.

Any idea how to completely uninstall hyperv from windows 10 home?

Thanks a lot @hessi9 and @mapk . It works like a charm, follow the steps and working fine.

Do you try this?

thx! it work for me - docker 2.2.3

showing error please help to remove ?

1 Like

From May 2020 Docker is available on Win 10 Home. For that you will have to update for the last windows (Windows 10 Home. version 2004) and the new version of Linux Subsystem (WSL2). You can simply do it from your Control Panel.
After that, you can simply install Docker as described here:

No way, checked all requirements, updated everything - no way I can run this sh…

Plenty of us have Docker working on Win 10 Home. Please confirm that you have updated to 2004 or higher and already have WSL2 working. We really can’t help you without level information and error messages.

Oh, I sorry guys, I forgot to check if virtualisation enabled in BIOS )))

I followed the instructions and I successfully installed the latest docker for Windows. Now I get error during connect. As far as I can see I enabled the Virtualization from BIOS (I can see it under Task Manager/Performance) and SystemInfo reports “Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.” which means that Hyper-V is running.

What is the root of the problem and how to solve it?

PS D:\download> docker version                                                                                                                                       Client: Docker Engine - Community
 Azure integration  0.1.15
 Version:           19.03.12
 API version:       1.40
 Go version:        go1.13.10
 Git commit:        48a66213fe
 Built:             Mon Jun 22 15:43:18 2020
 OS/Arch:           windows/amd64
 Experimental:      false
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.40/version: open //./pipe/docker_engine: The system cannot find the file specified. 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.