Hasleo Backup Suite V5.9.2.3 Released!

[admin]

Hasleo Backup Suite V5.9.2.2 Released!

What's new in this version:
1. Fixed an issue that caused file backup image merging to fail
2. Fixed an issue where backup failed when the image was stored in the root directory of a drive

Here are the download links:
X86/X64 Free
X86/X64 Trial
ARM64 Free
ARM64 Trial

[garioch7]

@admin,

Smooth installation.  The improvements just keep coming!  No competitor in the backup market that I know of is issuing new versions as quickly as Hasleo.  My congratulations to the Hasleo Development Team. 👍

I would prefer it if the updates also included the version number in their download name.  I don't know what others think ... ?  Just a suggestion.

Have a great day.

Regards,
Phil

[al3x]

Update installed - no issues as usual! Nice! 👍

I would prefer it if the updates also included the version number in their download name.  I don't know what others think ... ?  Just a suggestion.

I actually like that the update URL stays the same for every update.

But I would have no problem with a server redirect, something like:
Hasleo_Backup_Suite_Free.exe -> Hasleo_Backup_Suite_Free_v5.9.2.2_260901.exe

Cheers,
al3x

[admin]

@garioch7 and @al3x,

Thank you very much for your kind words and valuable suggestions.

Regarding the download file naming, we have carefully considered your suggestions. While we acknowledge the convenience this could bring, we have decided not to change our current practice at this time.

The main reason is that we have been using the fixed‑name download link for a long time, and many existing users as well as older versions of our software rely on this fixed URL to automatically fetch updates. Changing it now, even with a redirect, could potentially disrupt these automated workflows and prevent older versions from successfully downloading updates.

Nevertheless, we will keep your suggestion in mind for future major version releases, where we may have an opportunity to redesign the update mechanism more comprehensively.

Thank you again for your valuable input.

Have a nice day!

Best regards,

[garioch7]

@admin,

I think I did not explain myself very well.  @al3x has figured out what I was trying to say.

I am NOT suggesting renaming the link at all.

I am suggesting that the downloaded file name itself be reflective of the version.

My previous HBS download file was called: "Hasleo_Backup_Suite_Trial_5.9_Beta.exe".

This most recent downloaded update file was called: "Hasleo_Backup_Suite_Trial.exe".

I prefer that the name of the update file reflect its version number.  I have no interest in changing the download link whatsoever, and I was not suggesting that.

Have a great day.

Regards,
Phil

[admin]

@garioch7,

Thank you for your explanation. We will consider making improvements in the future, provided that they do not affect the program's functionality.

Have a nice day!

Best regards,

[garioch7]

@admin,

Thank you very much.  I have just now noticed and corrected my typos in the previous reply to you; i.e., "Backup_Suite_Suite ... " should have been "Hasleo_Backup_Suite ... ".

As I recall, the actual update filename did appear in at least some of the previous version updates that I did.

I think it would be a small improvement, if it can be done.

Have a great day.

Regards,
Phil

[Froggie]

Users should have some responsibility   

When I download a release, I do a RIGHT<click>/Properties/Details to obtain the release # then rename the file to my naming convention of choice... it's really not a big effort 

Probably much bigger on the part of the Developers...

[JayDee]

Users should have some responsibility   

When I download a release, I do a RIGHT<click>/Properties/Details to obtain the release # then rename the file to my naming convention of choice... it's really not a big effort 

Probably much bigger on the part of the Developers...

@Froggie
Did you copy that procedure from me?   ... just kidding.

That's exactly what I do with all my many downloads... not just HBS
that way I have a very consistent method of identifying 
various versions.

JayDee

[admin]

Probably much bigger on the part of the Developers...

Yes, besides changing the website code, we also need to consider the impact of upgrading from the old version to the new version.