Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker for Windows error: Unable to stop: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The specified module 'Hyper-V' was not loaded because no valid module file was found in any module directory #1212

Closed
sofhub2 opened this issue Oct 13, 2017 · 6 comments

Comments

@sofhub2
Copy link

sofhub2 commented Oct 13, 2017

I am running Windows 10 Home, creators update. I have installed Docker for Windows (CE). When I start Docker for windows (I am running it as administrator), after some time it throws the following exception. What should I do? The color of Docker icon in notification area is red. I have tried starting/restarting Docker windows service too. I have installed/uninstalled Docker a couple of times, but I get the same exception given below. Thanks for any help

Unable to stop: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The specified module 'Hyper-V' was not loaded because no valid module file was found in any module directory.
at , : line 79
at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV.cs:line 177
at Docker.Backend.ContainerEngine.Linux.DoStop() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 279
at Docker.Backend.ContainerEngine.Linux.Start(Settings settings, String daemonOptions) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 122
at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.b__0(Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 47
at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 145

@sofhub2 sofhub2 changed the title Docker for Windows erros: Unable to stop: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The specified module 'Hyper-V' was not loaded because no valid module file was found in any module directory Docker for Windows error: Unable to stop: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The specified module 'Hyper-V' was not loaded because no valid module file was found in any module directory Oct 13, 2017
@jasonbivins
Copy link

Hi @sofhub2 Docker for Windows requires Windows Pro or Education versions
https://docs.docker.com/docker-for-windows/install/#what-to-know-before-you-install

@sofhub2
Copy link
Author

sofhub2 commented Oct 14, 2017

Alright jasonbivins, thank you very much for pointing it out.

@XBLDev
Copy link

XBLDev commented Nov 30, 2017

Hi is this still the case? That Docker only runs on Windows Pro or Education versions? I just read the description in the link, it seems to be still the case? My laptop runs Win10 Home, can't seem to start Docker at all.

@eryogeshsingh
Copy link

I am on Windows 10 Pro and i still see the error.

@OmarAlashqar
Copy link

Leaving this here as it fixed the issue for me.

I had enabled Hyper-V and Containers through the Windows GUI, but disabling them and re-enabling them through Powershell worked (follow this)

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jun 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants