I noticed my windows VM was saying it was missing the video card after a reboot of the unraid host.  I had the config page set to the xml editor instead of the form view so I switched it back and then readded the passed through 4070 super as a second card behind the vnc one.  then suddenly the entire unraid interface became unresponsive.  I was able to get it back by browsing to it using the host name instead of the IP I typically use in the address bar.  as soon as I selected the vm tab the entire thing became unresponsive again.  I was able to get into the dashboard again by using the unraid connect page to get to it.  I was too afraid to click on vms so I just rebooted the host.  when it came back up I was able to get into dashboard normally but once again it froze anytime I tried to get to the vms tab.  one time I was able to get to it but if I tried to edit the settings of the vm it froze again.  most times I don't even get that far.  how can I troubleshoot whatever setting I must have accidentally misconfigured on the vm in order to return my installation to normal functionality?  I did upgrade the OS to 7.0.0 since the notes said there were improvements to VM administration but this didnt change the behavior I described above.  I tried using the main console to get into virsh but if I issue the connect or even the list command it just never comes back with any output or gives me the cursor back.  I have to ctrl+C to kill the command to do anything else.  

You can try redoing the flash drive, backup the current one first and then recreate it using the USB tool and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), make sure you use the same path for the VM Manager, then start the array and test, if there's still a problem it's likely with the libvirt image.

Quick update:

it was something to do with the specific VM config. After I rebooted a couple times the VM stopped trying to autostart and that stopped the stalling behavior when trying to edit the vm settings page. I redid the hardware pass through and deleted and recreated the VM. I just pointed it at the same virtual disk on the passed through nvme and poof it came back exactly as it was. I didn’t even have to reactivate windows. It was awesome. So now I am back up and running. I stopped the VM from auto starting so hopefully if anything like this happens again I won’t be locked out of the settings.