![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(131.20000000000002, 14.000000000000002%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZV%3C/text%3E%3C/svg%3E)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 36%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETL%3C/text%3E%3C/svg%3E)
HelloZephyr Vance
That boot failure is a classic issue after a host motherboard update, as the firmware flash often resets the UEFI Secure Boot certificates on the physical node and breaks the trust chain for Gen 2 VMs. Since you are seeing Secure Boot validation errors in the event log, there is absolutely no need to recreate the entire virtual machine. Just shut down the affected VM, go into its settings, and navigate to the Security tab. From there, try changing the Secure Boot template from Microsoft Windows to Microsoft UEFI Certificate Authority, or temporarily uncheck the Secure Boot option altogether to see if it boots. Once the VM is back online, you can shut it down and re-enable the standard Windows template to restore your security baseline. If this quick adjustment gets your server running again, please accept the answer to help other cluster admins facing the same issue.
Tracy Le