Hasleo Backup Suite V5.8.2.1 Released!

[admin]

Hasleo Backup Suite V5.8.2.1 Released!

What's new in this version:
1. Fixed a vulnerability in the disk backup image mounting driver
2. Fixed an issue where WinPE created under Windows ARM64 26H1 did not work properly
3. Fixed a backup failure caused by NTFS file record corruption
4. Added a global setting to create VSS snapshots without using VSS writers
5. Fixed other minor bugs

Here are the download links:
X86/X64
ARM64

[garioch7]

@admin,

Thank you for the new version.  It installed smoothly.

Have a great day.

Regards,
Phil

[pt58]

Great to see that the .exe is now digitally signed
Shouldn't this be mentioned in the new features?
It's something that's been talked about for a long time.

[yastil]

Thank you very much for the smooth update. The Secure Boot USB worked as well. I wish you every success in your work.
Best regards,
Yastil

[xeroid]

Great to see that the .exe is now digitally signed
Shouldn't this be mentioned in the new features?
It's something that's been talked about for a long time.

Yay! 

[al3x]

Hasleo Backup Suite V5.8.2.1 Released!

As always: No problems with the new version, working perfectly.
Thank you for the update! 

Great to see that the .exe is now digitally signed
Shouldn't this be mentioned in the new features?
It's something that's been talked about for a long time.

Oh, thanks for the info, didn't notice. Big step indeed! That hopefully helps preventing false flags from now on.

[admin]

Hello everyone,

Thank you all for your feedback and testing on the new version! We're glad to hear that the new version installs and works smoothly. And yes, the new executable now includes a digital signature. If you encounter any other issues or have suggestions while using it, please feel free to let us know.

Have a nice day!

Best regards,

[Epictetus]

Hello everyone,

Thank you all for your feedback and testing on the new version! We're glad to hear that the new version installs and works smoothly. And yes, the new executable now includes a digital signature. If you encounter any other issues or have suggestions while using it, please feel free to let us know.

Have a nice day!

Best regards,

Worked well for me too. Deleted the qt.conf file as a first step after installing HBS and the created ED worked well both on a stand-alone USB disk and as an iso on a Ventoy-bootable SSD.

[michaelreed]

This is actually a really common confusion and worth clarifying for anyone else who runs into the same issue.
When you use disk backup in the emergency environment, it creates a sector-by-sector clone of the disk. The problem is that this method doesn't always capture the boot configuration correctly especially on machines that use eMMC storage alongside a secondary SATA drive. Your Medion notebook setup with DISK0 and DISK1 is exactly the kind of dual-drive configuration where this gets tricky.
What you should use instead is system backup. Here's the difference in simple terms:
Disk Backup copies everything on the disk physically. But boot files, BCD (Boot Configuration Data) and EFI partitions sometimes don't restore cleanly to a different disk or even the same disk in emergency mode.
System Backup specifically designed to capture your Windows OS, boot files, and system partitions together as a unit. When restored, Windows knows how to start itself properly.
For your specific case next time, boot from the Emergency USB, but choose System Backup instead of Disk Backup. Make sure you're selecting the correct target disk (your eMMC DISK1 where Windows was originally installed) during restore.
One more thing worth checking right now go into your BIOS and verify the boot order. After a restore, sometimes the boot priority resets and it tries to boot from the wrong disk entirely. That alone can cause the "NO system found" error even when the restore was technically successful.
Hope this helps and great that the Hasleo team keeps improving the software with each version.

[al3x]

This is actually a really common confusion and worth clarifying for anyone else who runs into the same issue.
When you use disk backup in the emergency environment, it creates a sector-by-sector clone of the disk. The problem is that this method doesn't always capture the boot configuration correctly especially on machines that use eMMC storage alongside a secondary SATA drive. Your Medion notebook setup with DISK0 and DISK1 is exactly the kind of dual-drive configuration where this gets tricky.

Are you referring to this old post from 2021? Please keep in mind that there was almost 5 years of development (and 58 pages) between that post and yours.

The problem you describe was almost certainly fixed already. Sector-by-sector cloning has to be enabled specifically in the options and is not automatically enabled with the disk backup method.

Also, the main difference between system backup and disk backup is that system backup offers an easier method to select all necessary partitions of your Windows to get back to a bootable state in case of a needed restore. If you choose the correct partitions (or all) in disk backup, this will also work. Please also have a look at the FAQ here: https://www.easyuefi.com/backup-software...ackup.html

Q: What's the difference between system backup and disk/partition backup?
A: System backup only captures Windows OS partition and boot-related partitions. Disk/partition backup lets you select ANY disks and partitions for protection, including data drives.

If, for some reason, you can still replicate the mentioned problem of the original post with the current version of HBS, could you please give us some more details about the steps you took and what error you got?

Thanks!