@lmolina Latest update candidate edk2 fix applied without issue to my four host home lab pool. I tested one BitLocker encrypted Windows 11 VM with full shutdown and restart. What surprised me is that the VM booted back up fine. I was expecting that anything that changed the Tiano UEFI guest firmware might bork BitLocker unless it was suspended prior to applying the hypervisor host fix. (e.g. PowerShell Suspend-BitLocker -MountPoint "C:" -RebootCount 0 suspends BitLocker for an infinite number of guest reboots until it is explicitly resumed.) Apparently, this particular update doesn't alter any part of the guest firmware that causes a noticeable change to BitLocker. As a result, the boot volume unlocks and boots normally. Note that a firmware update on a physical machine generally is noticed by BitLocker. This is the reason the OEM's firmware installer suspends BitLocker with RebootCount 1 before performing the update's finishing reboot.