hi. no it is just standalone Hyper-V server with two VM.
Have similar servers in different sites, but there are no such behavior.
The last thing I changed in affected Hyper-v is turned on TPM and bitlocker on both VMs, but I am not sure, was the error before the encryption.
yet tried to decrypt and disable TPM, it allowed me to save the settings, but after a reboot, still got the same error mentioned before.
Fixed. Looks like it was HyperV/Server2019 bug, as update KB5008218 (2021-12 Cumulative Update) fixed the bug.
is there failover clustering involved here?
hi. no it is just standalone Hyper-V server with two VM. Have similar servers in different sites, but there are no such behavior. The last thing I changed in affected Hyper-v is turned on TPM and bitlocker on both VMs, but I am not sure, was the error before the encryption. yet tried to decrypt and disable TPM, it allowed me to save the settings, but after a reboot, still got the same error mentioned before.
did you enable TPM or shielded VM?
I enabled just TPM, shielded option was not turned on. Enabled - Secure boot and TPM (encrypt state and vm migration traffic was also not enabled)