Hasleo Backup Suite V5.8.2.0 Released!

[admin]

It should be the cache issue, I will clear it again.

[admin]

It seems everything is back to normal. I need to go get some rest now.

[Froggie]

It seems everything is normal now, I need to rest first.

Sleep well... we'll be here in your morning    

[Froggie]

...and while you were sleeping, the InAPP download/install now works perfectly.  All seems to be well in HasleoLand.  Sleep well...

[al3x]

And for the sake of completeness, here are the new correct hashes:

Hasleo_Backup_Suite_Free.exe
MD5: 7e31d108cf80f325480f6e73401dfec5
SHA-1: 0c9bea6f83bfc615711c8f4abc39f5e563f72d37
SHA-256: bbbe3d22a518a70c4b852a1ff4e32297ef9a84f969731dec29516a679f05e2b3

All good now

[Klaver7]

Thank you for the new Update, better give Kaspersky an email as it flags it as "VHO:Trojan.Win32.Convagent.gen",my experience is that certain inno installer versions can flag more false hits or C++ code can do some weird stuf on scanners also :-)

[admin]

Thank you for the new Update, better give Kaspersky an email as it flags it as "VHO:Trojan.Win32.Convagent.gen",my experience is that certain inno installer versions can flag more false hits or C++ code can do some weird stuf on scanners also :-)

We always use VirusTotal to scan before releasing, and below are the scan results, so this is a false positive.
https://www.virustotal.com/gui/url/54c7e...?nocache=1

VirusTotal
VirusTotal

[11Bravo49417]

FYI just downloaded V5.8.2.0 Windows X86/X64 and got Microsoft Defender Smart Screen Block for Unknown Publisher. Looked at Properties of downloaded file and no Digital Signatures. It did pass SHA-256 and VirusTotal checks though.

[garioch7]

@11Bravo49417,

Welcome to the Hasleo Forums.  Yes, the problem is that right now, the Hasleo files do not have a current digital signing certificate.  That causes security software to issue a warning.  The files are perfectly safe.

This issue is to be addressed at an unknown date in the future.

Have a great day, and welcome again.

Regards,
Phil

[admin]

@11Bravo49417,

Thanks to @garioch7 for the reply, this issue is indeed caused by the digital signing certificate.

Best regards,