The error you’re seeing (0x8007000D – “The data is invalid”) usually points to a mismatch or corruption in the virtual machine configuration data being passed between the source and destination hosts. It’s not typically caused by the VM itself, but by how the cluster nodes are communicating during the migration.
First, I’d recommend checking that both nodes have identical Hyper‑V versions, patch levels, and firmware updates. Even small differences can cause planned VM creation to fail. Next, verify that the cluster network designated for live migration is healthy and that firewalls aren’t blocking RPC or SMB traffic. Running Get-ClusterLog -UseLocalTime can help pinpoint where the handshake is breaking.
It’s also worth validating the VM configuration files on the source host, sometimes exporting and re‑importing the VM can clear out invalid metadata. If storage paths differ between nodes, make sure the destination host has access to the same volumes and permissions. In some cases, deleting the planned VM object on the destination and retrying the migration resolves the corruption error.
If you continue to see failures, testing with Quick Migration can confirm whether the issue is network‑related or configuration‑related. For production clusters, I’d recommend running a health check with Test-Cluster to ensure all prerequisites are aligned.
I hope the response provided some helpful insight. If you find this answer useful, please hit “accept answer” so I know it addressed your concern.
Jason.