Previously on My Life Sucks, I could not get the Cluster service to start:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/7a6431c1-3fec-437e-b733-092f5b056cb5/cluster-service-will-not-start-hyperv-2016?forum=winserverClustering
After resolving this issue, I was able to start the process of clustering my 2 nodes.
About 15 seconds after beginning the cluster process, the cluster management GUI crashes and the cluster fails to create.
I tried ensuring that the iscsi targets were identical thanks to this article:
https://www.asp.be/hyper-v-2016-cluster-crash-troubleshooting/
I did have a similar issue, where, on one node, the 2 SAN volumes were listed twice each (4 items). I removed 2 items and now both servers had the same number of targets. I confirmed that the SAN volumes were still online on what I wanted to be the primary node.
Just to be sure this wasn't completely the issue, I unchecked the box for "add all storage" to the cluster during the Failover Cluster wizard.
It still crashes about 15 seconds into cluster creation.
I'm using my Windows 10 Pro PC to create the Failover Cluster because there's a plug-in for RSAT that allows for this. Unfortunately, these are currently the only 2 Server 2016 servers in the domain. The whole point of this is to get our Hyper V Machines into High Availability so we can eventually remove our Server 2012 servers from the network.