Win 10, 21H1

I have a laptop that has WiFi built-in, but I also connect a USB based Ethernet adapter to it sometimes. When I have the Ethernet adapter connected, I'll sometimes notice odd behavior on the network. For example, if I try to connect to a share on that laptop from another machine on the network, I suddenly won't be able to access the share. Try to ping the machine and I can't even do that.

After some troubleshooting, I finally discovered that the laptop seems at some random point in time to switch to WiFi as the active connection, but it seems to fail to register that action with DNS. If I do an NSLOOKUP against the router (which is the local DNS server), it returns the Ethernet address.

Taking the testing further, I simply disabled the WiFi adapter altogether and that resolves the problem.

As a further test, I performed the same actions on my desktop computer which also has both Ethernet and WiFi. I don't really need WiFi on that machine, but I installed it anyway just to make sure I had my machine fully equipped. I get the exact same behavior on that machine.

One other common item between these machines is that I have Hyper-V installed on both systems. I can't easily remove it because I have something necessary running in Hyper-V.

Okay, on to the questions:

1) I thought that having interface metrics to set the priority to the Ethernet adapter should prevent this sort of behavior, causing the Ethernet connection to always be the active connection so long as it was connected but apparently it doesn't. Any idea why?

2) Is it possible that the Hyper-V virtual adapters are causing any of these difficulties?

It's been a while since I've done this, but previously I had laptops configured to give priority to the Ethernet adapter when at my desk all networking was done over the Ethernet adapter, but when I undocked it would automatically switch to WiFi. This has always worked great, but those machines were not running Hyper-V and that was back in Win 7 days.

Any thoughts?