Why does the router not see the MAC addresses of HyperV virtual machines?

Question

Hyper-V

There are several HyperV virtual machines on different operating systems. All virtual machines are united in an External network and this network is united in a bridge with a wifi card by the parent machine.
In the settings of the network cards of each virtual machine, there is a static MAC.
As a result, the router on which dhcp is configured first sees the MAC addresses of the virtual machines, but after a while the router sees each virtual machine under the parent machine's poppy, which causes an address conflict.
Tried to change the network card. A couple of days worked without problems, now the problems started again.

How to fix it?

upd
applied the update, which I usually "clean" subnets with (hyperv feature ...) after which a device conflict occurred (this did not happen). All network devices had a status
Windows is still setting up the class configuration for this device. (Code 56)
the network did not work at all. there was not a single network card
removed a new network card - it didn’t help
a couple of times I reset the network and applied a fix - unexpectedly

the poppies helped now they are being forwarded, but I think this is temporary ..

Answer 1

bridge with wifi card by parent machine

I'm afraid the reason is that when wifi reconnects, the windows network subsystem gets worse.
I can advise strange, try, let the operating system itself not be responsible for the bridge (as far as I know in windows this is done in different ways) i.e. create a loopback network connection (device manager, install old devices, look for a microsoft network adapter loopback), create a network bridge based on it and wifi and select it as a bridge with a virtual machine.
Why this can help, the loopback device is always on, the network bridge is active as long as at least one device is active in it, i.e. the virtual machine will run with an always active network connection

Answer 2

In my case, for a park of virtual machines, a virtual router always rises, a separate subnet for them (inside the virtual machines), and already the "rotary" is connected by a bridge to the Internet ....