I run Hyper-V on a Windows 10 Pro machine. It is used lightly for some testing scenarios.
Before I enabled Hyper-V and created the virtual switch, my workstation properly requested and received a DHCPv6 IP address and registered itself with the DNS server (all running on OpenWRT).
After enabling Hyper-V and the virtual switch, my main network connection now makes use of the bridge and virtual switch. The switch is setup as an internet connected bridge.
However, now my workstation no longer gets a DHCPv6 address, instead it has an SLAAC primary and temporary address. Nor does the name register in DNS.
There was a bug like this once in the main IPv6 code for Windows 10, but it was fixed a while back. I wonder if it remains in the vSwitch driver.
Can anyone else confirm?