I have seen that since Wing 220.127.116.11 there is something broken with network and Hyper-V. If I install Wing 18.104.22.168 or newer on a Hyper-V Host (testet Server 2012 R2 and Server 2019) the Interface is Down (seen in “Show interface ge1” and “show interface swtichboard”)
If I add in Hyper-V Manager an Legacy Network Adapter to the VM, I get a connected Interface. But using legacy virtual network adapter shouldnt be the solution, as it was working till Wing 7.2.x.
BTW Wing 22.214.171.124 doesnt even start on Hyper-V, but there is already a techdoc on this case.
Best answer by Chris Kelly
Martin, this sounds like something that GTAC needs to reproduce and get into the system to be fixed. I don’t run Hyper-V in my lab so I can’t test this, but It doesn’t sound like you’re doing anything wrong here. I’d rcommend reaching out to GTAC.