So, I too have this problem as a few other people. With the can’t create DockerNAT.
For some reason there is a ghost adapter called vEthernet (DockerNAT), which makes it impossible to use this name. I can’t find this adapter anywhere, but it’s easy to check that it’s there, as I can’t rename any adapter to be this name, as I get an error that this adapter already exists. Docker creates the switch in hyperv, and hyperv, because it can’t create vEthernet (DockerNAT), as it already exists, creates an adapter called vEthernet (DockerNAT) 2 instead. Docker is searching for an adapter called vEthernet (DockerNAT), but it’s a ghost so Docker can’t find it. Docker doesn’t get, that the adapter it wants to use is called vEthernet (DockerNAT) 2.
I’ve tried digging in the command line, in the registry and in adapter/hyperv settings.
I’ve reset hyperv, I’ve reset network setting (a function available in newest insider), reinstalled docker a few times, tried to create the switch manually. Whenever I create the DockerNAT switch manually, it gets the name vEthernet (DockerNAT) 2 in adapters. Have no idea what to do further.