moby: cannot start dockerd on upgraded server 2016

I have a 2012r2 server in production that I’ve now upgraded to 2016 in order to test the container functionality.

However the dockerd is not starting. If I run it from command line with --debug I get this:

time="2016-11-01T12:34:48.890755600+01:00" level=error msg="Resolver Setup/Start failed for container none, \"json: cannot unmarshal array into Go value of type hcsshim.HNSNetwork\""
time="2016-11-01T12:34:48.901737200+01:00" level=debug msg="Allocating IPv4 pools for network nat (c9baf78a40c8ae87a03ef07942ca9a6c58d244823487bae7c81ba9fd22dcab0b)"
time="2016-11-01T12:34:48.901737200+01:00" level=debug msg="RequestPool(LocalDefault, , , map[], false)"
time="2016-11-01T12:34:48.902737200+01:00" level=debug msg="RequestAddress(0.0.0.0/0, <nil>, map[RequestAddressType:com.docker.network.gateway])"
time="2016-11-01T12:34:48.903736800+01:00" level=debug msg="HNSNetwork Request ={\"Name\":\"nat\",\"Type\":\"nat\",\"Subnets\":[{\"AddressPrefix\":\"0.0.0.0/0\",\"GatewayAddress\":\"0.0.0.0\"}]} Address Space=[{0.0.0.0/0 0.0.0.0 []}]"
time="2016-11-01T12:34:50.429431400+01:00" level=debug msg="releasing IPv4 pools from network nat (c9baf78a40c8ae87a03ef07942ca9a6c58d244823487bae7c81ba9fd22dcab0b)"
time="2016-11-01T12:34:50.429431400+01:00" level=debug msg="ReleaseAddress(0.0.0.0/0, 0.0.0.0)"
time="2016-11-01T12:34:50.431454300+01:00" level=debug msg="ReleasePool(0.0.0.0/0)"
time="2016-11-01T12:34:50.431454300+01:00" level=debug msg="starting clean shutdown of all containers..."
Error starting daemon: Error initializing network controller: Error creating default network: HNS failed with error : Unspecified error

I have all of the updates installed as of 1.11.2016. Docker version: docker version: Version: 1.12.2-cs2-ws-beta API version: 1.25 Go version: go1.7.1 Git commit: 050b611

I’ve also tried with 1.2.13 with the same results.

The VM is running under Hyper-V on Windows 10 Anniversary update.

I’ve also tried doing a fresh install from the same media and there it’s working fine. So it has to be something to do with the upgrade from 2012r2, but I cannot figure what it could be.

I’ve uninstalled the container feature and reinstalled it, but the problem remains. Anything else I can do to help troubleshoot this?

Description

Steps to reproduce the issue: 1. 2. 3.

Describe the results you received:

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker version:

(paste your output here)

Output of docker info:

(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.):