Thanks @TheRollbackFrog for testing it- Since the bulk of my own imaging & restores chiefly are DISK MODE. that concerns me, but only if it distorts another imaging app i would think. Also makes me wonder why Hasleo imager can't just reset the SAME Partition ID as the image it takes unless it means to lock a user to that particular product by also switching Partition ID numbers?
I think it's just a mistake on their part... I don't think they're trying to perform any kind of "product lock." As it is, it doesn't even work properly, in disk restore mode, for their own product specs (currently, if you image a non-System disk with multiple partitions, after the Disk Mode restore they will have newly generated Windows' DiskLetters to be dealt with). That almost identical issue existed with System Backup back in December. When brought to their attention, they provided a fix and allowed System Backups to work as expected. Hopefully, the same thing will happen here... especially since they've acknowledged the issue publicly.
It's really not a difficult issue. Most imaging apps offer "System Backups"... the main reason is to insure the correct partitions are imaged to provide for proper BOOTing configurations to be returned to System disks (many, if not most, users have no idea what partitions are needed to BOOT a System properly <Legacy-MBR vs UEFI-GPT>). The next most popular imaging app selection mode is roll your own... pick whatever partitions you want in your image (mostly for users who know what they're doing). Both of these scenarios require the same type of restoration operation... with the same information being restored for each partition, it's not rocket science here. The only time a partition serial # or partition ID should ever change is if the partition itself changes (size or format change, mainly)... at that point it needs a new ID structure (it's a different partition after all). The restoration mode for both of the above scenarios should be exactly the same as far as partition specs are concerned... not different.
3.4 fixed the crash issue for me. This revision included some changes. It appears they didn't fix the stated issue in this version.
Thanks @khanyash for the heads-up. @TheRollbackFrog too. Maybe i will hold off a bit and keep using the old version (which does work for me) until they fix the kinks.
This revision crashed for me, and the dump files are empty (the issue is similar to the one with 3.2). I am reinstalling 3.4, which is available on the website, as it worked well with no crash issue.
It's probably safe enough to assume that V.3.4 is the safer bet then? Since that revision release apparently didn't pan out as expected. I'm itching to update my own (now older release) so that the Emergency Disk can be redone again too but don't want to get ahead of things until everyone reporting issues @TheRollbackFrog and yourself are confident that HBS is resolved malfunctions.
@EASTER - v3.4 (current release) has the exact same issue that I'm seeing as what existed in the release you're using... upgrade should be safe. @khanyash issues concerning crashes have also existed in the release you're using, you should be safe moving to v3.4 if you haven't seen any crashes. @khanyash issues associated with application deactivation may eventually be solved but are usually activation algorithm issues with the application itself... they wind up using activation criteria that is really not related to protecting the app against phony activation. If the app uses Partition ID or Serial # in their process, that makes no sense. That information changes quite often during the life of a System (partition reformatting/resizing, etc.). You should be OK to move to v3.4 (current release on the web site)...
Thanks @TheRollbackFrog- As i already have BOTH the revision 'and' 3.4 release from @Hasleo then i'll soon try it out myself as you suggest. Regards EASTER
Current issues associated with improperly restored partition information while in Disk Mode (above Post #342) have been solved. See this POST in the Hasleo Forum for the newly fixed installation (v3.4.1 Build 230313).
@khanyash - It looks as though Hasleo may have solved your problem. See their Forum for a new release to try.
Hi @ Wilders When it's installed it shows (v3.4.1 Build 230313). NOT (23032013) Is this a problem or misnaming? Terry
Hi @ Wilders My bad!! "(When it's installed it shows (v3.4.1 Build 230313). NOT (23032013)" I should have said:- When it's installed it shows (v3.4.1 Build 130313). NOT (23032013) This is from About in the software. Terry
Hi All. We agree, my first post was incorrect, my second was correct. The issue I was concerned about was that the download was shown as (v3.4.1 Build 230313). The date shown in About is March 13 2023. However it appears that the concensus is that there is no problem. Sorry for the confusion Terry
Just began to test Hasleo Back up Suite, and I just wanted to say I really appreciate all the comments and instructions. Also thank you to Froggie as always for the depth of your tests and advice. This is a very useful drive image tool that has a lot of features for its price. Speed of backup has been admirable, right up there with DS and Macrium, Terabyte Image for Linux, at least for me. I was happy to hear they fixed the restore issues Froggie described, and I didn't try it until last week when they came out with the latest 3.41 version that fixed the disk/partition restores renumerating, etc., if that is the proper term. Last night, I checked their website, and see their free download file is 114KB smaller than the release they offered last week, yet it does state version is 3.4.10 after I downloaded it. No "build" number, as far as details on the properties of the install file, but 3.41 version. Anyone else notice this? Not a big deal, perhaps they tweaked their installation file, I tried to open the exe file using 7-zip which usually is able to open up many exe and other files / archives, but it was unable to open this for me to check or compare files. I am curious if they added another feature, but I do not notice anything obvious on their site about it. For a free option, I think they are doing their best to offer a very capable suite that some features are almost always a paid for feature. I have no problem paying for quality software, I own Terabyte, etc., but this Hasleo has my attention for now. I like the boot menu option, but chose to build a USB WinPE flash drive which works great, but does not offer "System Backup" though does offer disk/partition backups as well as restore. I still love the simplicity of DS and its reliability, as well as the reliability of Macrium, Terabyte, etc., and I am intrigued with this Hasleo as well as all the comments. I hope Hasleo continues the development and continues to improve it, it appears they are. Thanks again to everyone for the discussion about this, nice to see backup drive imaging solutions that are not huge installations that literally take over your system, and still provide most or all of what is needed for data protection. Have a great week!
The standalone download you mention from the site is internally dated 10Mar2023, the one offered for testing was internally dated 13Mar2023... I know not what the differences are. I am using the 13Mar2023 version since I know it contains all the fixes mentioned above. If I get a chance, I check out the 10Mar2023 version to see if it is functionally equivalent.
Some good points raised. I am also with the 13MAR2023 release and i must agree it's speed is impressive.
I believe Hasleo provides an improved or fixed version on the forum. After testing, they release the same version or a new version on the website. It appears the version available on the forum, 13MAR2023, includes fixes for the Partition Information issue reported by @TheRollbackFrog and the GOM Player Plus Deactivation issue reported by me.
Thanks for the comments and thank you Froggie. Also, I just saw that you asked about this file Froggie on their forum, I appreciate that and your comments @khanyash . I rechecked and both files I have say 3.4.10 for version, but makes sense the March 13 release would be larger if that took care of the disk/partition issues. I would think they would have made sure to offer the latest update on their public download. Thanks again, and this is turning out to be quite a reliable and lean back up utility for a free version. @EASTER I agree friend, the speed of Hasleo is impressive, many free versions sometimes limit backup/restore speeds to encourage to purchase, but Hasleo is right up there with DS, Macrium, etc. as far as speed. Do any of you guys use the Boot Menu feature/entry? I created the bootable USB drive, a boot menu entry would be really convenient to use. Just wondered if it works as expected. I tend to shy away from menu entries, though I used to use EasyBCD quite a lot years ago. I guess my question is if I try it and decide not to use it, does it actually remove the boot menu entry from the BCD store also? Thank you!
@Jim1cor13 - I tested the BOOT menu option and it worked as expected, both during manual creation & removal. I ended up adding the WIM created during their ISO creation to my BOOT menu via EasyBCD... use it when I need to use it. Their 1-time use of the BOOT menu for automatic restoration of locked volumes (OS in particular) works as well... very fluid. It's really a fairly complete package. I'm working on testing edge cases at the moment... at least as they're related to how I use imaging programs. They've been very responsive to discovered issues so far, hopefully that will continue.
I really appreciate your experience with this Froggie and taking the time to respond and help. It really appears they are doing a good job with this development, and I agree, definitely a more complete solution than anything I think that has come along for years offering these features for no charge. My system is UEFI, non-CSM booting. I actually just converted the system late last year. Rather than using a MBR to GPT conversion utility, I used Macrium instructions doing this manually, using diskpart to clean my ADATA SSD drive then manually creating the EFI part, MSR, then dragging a macrium backup of my C: OS drive. I had to adjust my C drive to allow for the WinRE partition then use reagentc once I booted into windows after changing the BIOS from legacy to UEFI, so I could set the recovery part properly. Took me some time, and a lot of reading to get it right, but not that bad. I don't use Secure Boot, just UEFI and non-CSM, so no legacy booting. Worked using their instructions, but I was nervous, using MBR for so many years, and knowing it well, but GPT I think offers some advantages especially for partitions, etc. Sorry for being so wordy, just letting you know where my system is at now in regards to the Hasleo discussion. I'm going to give the boot menu a try, but actually, I like your idea of using easyBCD that way you could boot into that entry even if you do not have Hasleo backup installed on your system. I like the lightness of this suite, lean and gets the job done. I am really looking forward to the results of some of your edge or fringe type testing...that will tell you just how flexible an app can be I guess or how it can handle uncommon tasks, etc. Thanks again for your time...very much appreciated!
