Hasleo Backup Suite V5.9.2.1 Released!

[admin]

@all,

Now that UEFI firmware checks the Security Version Number (SVN) of boot files during startup, a practical issue arises: Windows security updates may raise the minimum allowed SVN recorded in the firmware, causing any Emergency Disk created before that update to become unbootable because its boot loader is too old. This means we can no longer guarantee that an Emergency Disk will always boot properly with Secure Boot enabled. In such cases, users must either recreate the Emergency Disk or temporarily disable Secure Boot to boot from the old one.

Best regards,

The SVN is only checked if the 2011 cert is revoked.

To make sure you are always using the latest boot files for making rescue media using 2023 is to copy the file from C:\Windows\Boot\EFI_EX as that will always have the latest update to secure boot after Windows Updates.

What I was doing before 5.8.2.2 was just copying the file to Hasleo then creating rescue media within the Hasleo GUI and even if 2011 was revoked this would boot without any SVN mismatch error.

copy C:\Windows\Boot\EFI_EX\bootmgfw_EX.efi "C:\Program Files\Hasleo\Hasleo Backup Suite\bin\WADK\Boot\EFI_EX\bootmgfw.efi"

You're right. SVN is only checked when the 2011 certificate is revoked. For a Emergency USB Drive, replace X:\EFI\Boot\bootx64.efi (or bootaa64.efi for ARM64) with C:\Windows\Boot\EFI_EX\bootmgfw_EX.efi, where X: is the drive letter of the USB drive.