Thread Rating:
  • 3 Vote(s) - 4.67 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Hasleo Backup Suite V5.8.2.2 Released!
@michaelreed, @al3x,

Now many computers have BitLocker encryption enabled on the Windows partition by default. If you perform a backup under WinPE, these partitions are in a locked state, and Hasleo Backup Suite can only back up in sector-by-sector mode. During restoration, since the partition is still encrypted, Hasleo Backup Suite cannot modify the data in the operating system partition to match the restored partition, resulting in the system being unable to boot.

In addition, if the Windows partition is not unlocked under WinPE, HBS cannot even recognize the operating system, making it impossible to perform a system backup.

Therefore, we do not recommend performing backups under WinPE. WinPE should primarily be used for restoration operations.

Best regards,
Reply
That's good, latest version with a digital signature, I've reactivated Smart App Control in the Windows Security Center  Wink
Reply
Hasleo Backup Suite V5.8.2.2 Released!

What's new in this version:
1. Improved creation of bootable media that supports the UEFI CA 2023 certificate
2. Fixed an issue that caused system restore to fail
3. Fixed an issue where file backup could not list drives under Windows ARM64
4. Fixed an issue that caused backup of MacOS files/folders shared via Samba to fail
5. Fixed an issue that caused "Smart Backup" to not work properly
6. Fixed other minor bugs

Here are the download links:
X86/X64
ARM64

Note: This version includes important improvements that require users to recreate the emergency disk.
Reply
@admin,

Thank you for that timely release.  Today is the turn of HBS in my tri-weekly testing schedule.  Also, since I have now managed to get 2023 Secure Boot Certificates added to my old, but venerable 2019 Dell XPS 8930 SE, I will create new EDs for both it and my laptop.

Have a great day.

Regards,
Phil
Reply
@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,
Reply
Everything went fine here. Updating went flawlessly. Recreating the boot menu went as expected too. Imaging, full and differential, as well as restoring went smoothly as well. Essentially, I have to errors to report with this new version.
Reply
(06-27-2026, 03:31 PM)n8chavez Wrote: Everything went fine here.  Updating went flawlessly.  Recreating the boot menu went as expected too.  Imaging, full and differential, as well as restoring went smoothly as well.  Essentially, I have to errors to report with this new version.

I report NO errors too. All boots well both from the HBS ED ISO on a Ventoy disk and a free-standing bootable USB ED.

But thanks @admin for the warning about the possible need to disable SB in future.
Reply
Just upgraded to version 5.8.2.2 and I have to say — this is exactly what a backup solution should be. Fast, reliable, and rock solid. Backup and restore work flawlessly without any issues. The team clearly put serious effort into this release. Well done, Hasleo — keep up the excellent work! Thank You Very Much
Reply
We truly appreciate all users for testing and providing feedback on version V5.8.2.2.
It makes our team very happy to see friends like garioch7, n8chavez, Epictetus, and yastil reporting that the new version runs smoothly.

If you encounter any issues or have suggestions for improvement while using the software, please feel free to post on the forum at any time. We will listen carefully and continue to optimise.

Once again, thank you all for your support and trust!
Reply
(06-27-2026, 12:51 PM)admin Wrote: @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"
Reply


Forum Jump:


Users browsing this thread: 4 Guest(s)