Expected behavior

Docker starts fine after updating to Windows 10 1709.

Actual behavior

Docker fails after updating Windows to 1709 with:

Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Hyper-V encountered an error trying to access an object on computer 'MYCOMPUTERNAME' because the object was not found. The object might have been deleted. Verify that the Virtual Machine Management service on the computer is running.
at New-Switch, <No file>: line 131
at <ScriptBlock>, <No file>: line 385
   at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings, String daemonOptions) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 246
   at Docker.Backend.ContainerEngine.Linux.Restart(Settings settings, String daemonOptions) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 182
   at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.<Register>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

Information

• Diagnostic ID 71BC63BB-E7FE-4D08-910F-237D3872E478/2017-10-18_14-31-46
• Windows 10 1709 on Surface Pro 2017

So to be fair, it doesn't appear that Hyper-V made it through the OS update very well, but since I only use Hyper-V to run Docker for Windows, and since Microsoft support has so far been completely useless, I thought I'd check in here to see if a) anyone else had hit this issue; b) anyone might have thoughts on how to get back into a good state.

I've tried disabling and re-enabling Hyper-V completely (of course with the requisite reboots in between), uninstalling and reinstalling Docker for Windows, installing the edge version of Docker for Windows, resetting the Windows network interfaces completely, and even doing a system restore to the previous state, and at this point it's just not working.

As noted above, the core issue appears to be Hyper-V. The Hyper-V Host Compute Service and Hyper-V Virtual Machine Management service are both reported as Running, but even Hyper-V Manager can't connect to Hyper-V on the local machine to manage it.

Anyone else seeing this? If so, any thoughts on how to get back into a good working state? Thanks in advance!