This has happened to me twice now, I've uninstalled and reinstalled the hyper-v feature and it occurs each time.

Environment: Windows 10 Professional

Problem: I create an external virtual switch and allow it to share connection with the physical host. The host has a single physical network adapter and it is tied to to a router in my home network. I also create an internal virtual switch.

I give my guest a static ip that is in range of the gateway of my Ethernet adapter and tie it to the external switch.

At that point I can ping the guest and the guest can see the internet. I activate windows on the guest, install a few updates, then switch it to the internal virtual switch.

I can then rdp to the guest and get full audio and video.

Some time later, no defined period, this last time it was an hour later, I can't rdp to the machine anymore, it's unable to connect and I get an ip address conflict on the guest.

This gives me two problems: even if I give the guest a new ip I can't rdp to it and if I give it the old ip and switch to the external switch I can't see the internet or rdp to it.

The other problem is that even after shutting down the machine and deleting all virtual switches and uninstalling ghosted network adapters I can still ping the ip that I made up originally.

How can I clear this ghosted ip and allow rdp functionality to my guest again?

Thanks