Hyper-V Live Migration cancellation leaves virtual network adapters with inconsistent MAC addresses

Goal

Determine the expected state of a virtual machine's network adapters after a Live Migration is cancelled—whether by explicit Stop-VM or an implicit timeout—so that automation can reliably restore connectivity without manual inspection.

Constraints and uncertainty

• Microsoft documentation does not specify whether a cancelled migration rolls back adapter configuration or leaves a hybrid of source and destination settings.
• Observations on Windows Server 2019 and 2022 show some adapters retaining the source host's MAC address while others adopt the destination host's configuration, causing duplicate-MAC or connectivity failures.
• No public API exposes a migration timeout parameter; external watchdogs are required, but the resulting adapter state remains undocumented.
• Microsoft has indicated that a unified rollback policy for cancelled migrations is still a pending design decision.

Questions

1. What is the authoritative, version-specific behavior of each virtual network adapter's MAC address and switch attachment after a Live Migration cancellation?
2. Is there a supported programmatic way to query or reset the adapter state to a known-good configuration without a full VM restart?
3. Are there any documented workarounds or hotfixes that standardize the rollback behavior across Windows Server 2019, 2022, and the upcoming 2026 release?