EVENT-ID: 1230, 1146 & 1069 

Server 2016 3 Node Cluster. Validation wizard passes. 

When live migrating VMs between host a VM will hang up in a "re-starting" or "processing" mode. The VM does belong to either host and cannot be removed from the Failover Cluster Manger, and doesn't show on the HyperV manager. The Failover Cluster Events then cycle the EVENT-ID: 1230, 1146 & 1069 events. All VM on the host become completely unresponsive. 

The only way to correct the cluster is hard shutdown the host server experiencing the Event-IDs. Then import the original VM which began the issues.