Windows 10 V1903: IP resolution bug in Hyper-V switch

[German]In Windows 10 May 2019 Update (version 1903) and possibly also in October 2018 Update (version 1809) there is a bug in the 'Default Switch' which leads to issues with Windows Sandbox, Mobile Hotspot or with Windows Containers – they do not work. The reason for this is that the default switch probably does not get an IP address. The reason are updates from Windows 10 and from the hardware manufacturer's system updater. But there is a workaround.


First reports

Frank Lesniak posted this for the first time in the feedback hub for Windows Insiders. I myself became aware of the problem a few days ago via the following tweet. 

That was still a question from Frank at the end of May 2019. Later he came across an MSND forum post HNS failed with error : Element not found] when creating network w/ interface name specified from Rafael Rivera, that seems to address the same issue.

'm creating a transparent network device with:

docker network create -d transparent –gateway –subnet -o -o"Virtual Machine Access" -o external

The Docker daemon is returning: Error response from daemon: HNS failed with error : Element not found.

  • Docker server: 17.03.1-ee-3
  • Windows Server 2016 Standard w/ Hyper-V role installed
  • IPv6 is up and running on all interfaces
  • Interface in question is named "Virtual Machine Access" and is used by Hyper-V machines on the same machine. Not currently set up with management operating system access, though I tried with/without this set.


But there was no response to that question. Frank Lesniak continued testing and found the cause.

Hyper-V guests do not receive an IP address

I had the above mentioned tweet on observation. Frank Lesniak then updated his tweets a few days ago with this post.


He was able to narrow down the error. The reason for malfunctions in the Windows Container, Mobile Hotspot or Windows Sandbox area in virtual machines is a bug. The Hyper VMs are never assigned an IP address by the DHCP server.

Updates kill the feature

In further tweets he outlined this issue, which is probably related to automatic driver updates by Windows 10, further updates and the Lenovo system update program.

In the tweet above, he states how he can reproduce this on several bare-metal systems. As soon as drivers are updated and updates are installed and the system updater of the device manufacturer is executed, there is the IP issue back.

The VM no longer receives an IP address from the DHCP server and the event log of the host network adapter contains error 0x80070490 / 0x80070032 under event ID 1030.

Strange workaround

In another tweet Frank posted a pretty crude workaround. You should install the Windows Sandbox.

In this case, the IP address assignment to the VM works again. I don't know if it works on a non English Windows 10 V1903. Because there is the sandbox bug (see Windows 10 V1903: Update KB4497936 breaks Sandbox). But maybe it'll help someone who's searching a branch why Hyper-V guests make trouble with Internet features.

Cookies helps to fund this blog: Cookie settings

This entry was posted in issue, Virtualization, Windows and tagged , , . Bookmark the permalink.

5 Responses to Windows 10 V1903: IP resolution bug in Hyper-V switch

  1. Erwin says:

    Thank you for this! I just installed 1903 today and my Hyper-V's were unable to get IP from DHCP server. Installing Windows Sandbox fixed the issue!

  2. Peter says:

    win 10 1903 (18362.418) — my default switch was gone after an update but adding sanbox feature and rebooting brought it back. thanks!

  3. Raul Saavedra says:

    Win 10 1903 (OS Build 18362.356), had an Ubuntu 18 VM under Hyper-V getting networking and updates perfectly till before the updates. Now it has no networking.
    I was not using the default switch but two virtual switches I had created: one for the fixed networking, and another for wifi. Neither one gets networking now.

  4. Advertising

  5. Sheridan D Turner says:

    Old thread… it.

    Occasionally my machine crashes (BSOD) or I receive some major Windows upgrade, after rebooting, the Hyper-V default switch, changes to "Private network" and stops working for my VM's. I cannot change the default switch settings, as they are grayed out.

    My work around is to remove the Hyper-V feature. Reboot. Re-add the Hyper-V feature. Reboot. The Default switch is now set to "Internal network" and functions properly.

    Windows 10 Pro Insider

    Same problem last 4-5 builds.

  6. Luca says:

    So what option is there left for Windows 10 Home users? You cannot install Windows Sandbox on it.

Leave a Reply

Your email address will not be published. Required fields are marked *