Unable to launch docker, Unable to create error after updating Windows 10

[Levity1]

• I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID: 2EE0A2AE-5143-4737-AE40-1D9FE24338A7/20191024222207

Expected behavior

Docker launches with no issues

Actual behavior

Error appears after launching --
"Unable to create - The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The input object cannot be bound to any parameters for the command either because the command does not take pipeline input or the input and its properties do not match any of the parameters that take pipeline input.

at Docker.Core.Pipe.NamedPipeClient.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters)
at Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup)
at Docker.Actions.<>c__DisplayClass24_0.b__0()
at Docker.ApiServices.TaskQueuing.TaskQueue.<>c__DisplayClass17_0.<.ctor>b__1()"

Information

• Windows Version:
  Windows 10 Version 10.0.18362 Build 18362
• Docker Desktop Version:
  2.1.0.4 (39773)
• Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM:
  No

Steps to reproduce the behavior

1. Launch docker
2. Error appears

[ThePlenkov]

Same for me. Suddenly crashes. Cannot work anywore!

[n-richaud]

The windows update reset some configurations , so you need to follow this procedure to make it work again : #1221 (comment)
On the laptop i tried the fix it was not for "Code flow guard (CFG)" i had to uncheck "override settings" so uncheck this uncheck it for all .

[ThePlenkov]

I solved my issue like this:

1. Disable Hyper-V (Windows features)
2. Reboot
3. Enable Hyper-V
4. Reboot

[Levity1]

Thanks for the help, I tried both of these methods and the Hyper-V changes the error code after the 2nd reboot, but reinstalling docker gets me back to square one.

Here is the error code I get after re-enabling Hyper-V + reboot:

Unable to create Hyper-V VM: The input object cannot be bound to any parameters for the command either because the command does not take pipeline input or the input and its properties do not match any of the parameters that take pipeline input.
at Set-IPAddress, <No file>: line 290
at Set-SwitchIPAddress, <No file>: line 320
at New-MobyLinuxSwitch, <No file>: line 260
at New-MobyLinux, <No file>: line 176
at <ScriptBlock>, <No file>: line 800

   at Docker.Core.Pipe.NamedPipeClient.<TrySendAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters)
   at Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup)
   at Docker.Actions.<>c__DisplayClass25_0.<Start>b__0()
   at Docker.ApiServices.TaskQueuing.TaskQueue.<>c__DisplayClass17_0.<.ctor>b__1()

[CaliGlenn]

The windows update reset some configurations , so you need to follow this procedure to make it work again : #1221 (comment)
On the laptop i tried the fix it was not for "Code flow guard (CFG)" i had to uncheck "override settings" so uncheck this uncheck it for all .

Tried this. Didn't work.

I solved my issue like this:

1. Disable Hyper-V (Windows features)
2. Reboot
3. Enable Hyper-V
4. Reboot

Tried this too. Didn't work.

Suggestions are welcome. Been looking to this issue for to long today :(

[Levity1]

I've found a workaround temporarily. It seems Docker Version 2.0.0.3 still works if you want to give that a try.

[CaliGlenn]

I've found a workaround temporarily. It seems Docker Version 2.0.0.3 still works if you want to give that a try.

Nope, still same error for me :'(

[CaliGlenn]

After more than half a day of testing, googling more testing and just whining...
(One of those days that you looked at page 5 at google, and looked at every link...)

I decided to force the latest windows update again on my machine (while preserving my files and apps: https://www.microsoft.com/en-us/software-download/windows10). Hoping that would restore Hyper-V back to normal settings. In my eyes that error has nothing to do with docker, but is a problem on Hyper-V level.

Also I noticed that 1 Network adapter was missing, and I couldn't find to reinstall it (after many, many, many times of rebooting and disabling/enabling Hyper-V). The other one looked fishy, so I deleted it. And ran the above 'update' for the night.

And yes... Tis morning I had a 'halelujah' feeling 😂
As I hoped: Hyper-V is stated back to normal! Everything works again!

for now....

Good luck to whoever has this nasty little bug.

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

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

[docker-robott]

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