I tried it with a boot meny and usually there where no problems, but here is another story. I attempted a restore with Hasleo that did not work, so i used IFW usb boot media instead for my IFW image and went back to before Hasleo was installed. When booting up the Pc where stuck about 15sec longer in the boot sequence with a black screen, over and over after testing it. Figured that it could have something to do with Hasleo boot meny. So i reinstalled it and added a boot meny, removed it and restarted. Voila, problem was gone. I have never before experienced that a backup program leaves something from the boot meny that creates this type of problem when going back to before it was installed, it should not either. Very strange. I do not use it anymore, since my experiences is that it is still a Beta because of all the problems i have meet. The experience above was just one to many.
For me, HBS always removed the boot menu when I uninstalled or updated it. You have to re-add the boot menu after an HBS update. I test every HBS release and have done many restores using the boot menu with zero failures or issues. You restored the system to the point before HBS installation with IFW. The HBS boot menu was present on the system after the IFW restore. How is it an HBS issue?
The ultimate uninstall is to restore a whole system to a point before something was installed, if that does not work then something is not right. But this may be a technical issue that i do not understand but as i see it, it should vanish. If it does not, well, then the way Windows is working, or HBS, is not quite right Nevertheless, i have had a couple of other issues, so many that i did not bother to report them on their forum because i thought they where so many that it was better to give it up.
Brian. I do not remember if it was on the second Os of a dual boot config or the first. HBS do not back up everything for the second Os so, you may be on to something here. But anyway, i translated the program to make sure i will get a free license in the future when it is going paid (because it will), but for now i skip it.
Thanks for sharing that @pb1 Part of the reason I tend to shy away from boot menu entries, (some programs are not thorough in removing some entries) and I asked Froggie about that he did say Hasleo removed the boot menu entry fine, and that the feature worked well for him. He ended up using EasyBCD to add the WinPE bootable media from Hasleo to add it to his boot menu. Probably the better choice maybe? I suspect the issue is having to restore with a IFW image due to the failed Hasleo restore, you never removed the Hasleo boot menu entry nor did you uninstall the program itself. You applied an image file from before Hasleo was installed, but you have to either remove the boot entry from Hasleo, or restore your ESP partition. At least that is the way I am seeing it. Perhaps even had you been able to uninstall Hasleo, you may still have to remove the boot entry from Hasleo interface before uninstalling Hasleo backup? I have no idea, just a thought. I know it sounds odd, I am not sure if Hasleo would actually uninstall its boot menu entry if you uninstall the program before using it to remove the boot menu from within its interface. I would hope it would. Maybe Froggie or someone will offer more ideas, but I think Brian's question is the bottom line...restoring the ESP or EFI partition would solve the boot entry issue. On my GPT disk, the first partition is called EFI, some call it ESP, I think the proper term is ESP. I will do a quick backup before using any new software, especially imaging software. I DO like Hasleo, but I am very cautious with any new imaging software. IFL or DS are incredible solutions to me, Macrium also of course, they have a history of reliability, I hope Hasleo can accomplish this also. Thanks pb1 for the information. I've worked on computers since 1997, and I always learn something on this forum, it is a great place with some great people who lend their knowledge so graciously.
Brian. Wrong answer from me in post #380. Yes IFW restored the ESP, i hope, because i always back up and restore Windows 4 partitions. The 2 before C:, C: and the recovery partition.
You are aware that you CAN use BOTH! HBS is fine tuned and actively developed. It's my number (2) imaging solution and flawless/fast for me so far. Backupper by Aomei is my #1 and Drive Snapshot i am using as a supplemental.
Just tried Hasleo Backup for the first time on a brand new laptop. The interface is very clunky and laggy. I created the recovery USB then when I chose backup running Windows, I just got a loading spinning icon forever so I had to end the program from task Manager. Tried it twice with the same result Then the third time I ran the program, I got this message: Here is the log file: https://workupload.com/file/Z7XQxApAD7L Not gonna come near this program anymore.
Hi Alex! I'm probably the one who has been doing the most testing with this product to date, and my position would be as follows... Since December 2022, the application has quickly moved from being somewhat usable to an almost complete (maybe even complete) and very usable implementation. Since I'm in the middle of testing it with fringe cases at the moment, I'm not ready to make a declaration as to its "perfectness" (which no app really has ) but I am currently using it as my main secondary imaging System behind Macrium REFLECT. My testing has gone very well and the EasyUEFI development team has been very responsive to all the anomalies I've discovered along the way... always a nice thing to have when you embark on a mission like this. My recommendation would be for you to start using it as a backup to your primary imaging System, getting used to its UI and uniqueness in the meantime. It is a reasonably full function product with automatic locked partition restoration capability (even without a BOOT menu item configured)... and it has BOOT menu capability as well as ISO/USB/CD-DVD creation for emergencies. The scheduling capability is rudimentary but more than adequate, and it can CLONE as well... file restoration is also available although a bit rudimentary at the moment, mounted images are in the near future. That's a lot of capability for a FREE solution. I personally believe it has come far enough along to be a very useful imaging solution.
Glad to hear how it is going Froggie. Also how responsive they have been, I was glad to see you were on their forum the other night and knew you would let them know of any oddities you encountered and happy to read how they would address these matters. I am still very cautious, but impressed so far. I always create a backup with Macrium or DS before testing it out. Thank you for your input, it is always greatly appreciated and helpful.
HBS functioning flawlessly on this end with backup imaging and most important successful restores. The rest of it's many more options are a Bonus!!
Please check whether there is a BackupService.exe.xxxx.dmp or Crash_x_xxxx_xx_xx_xx_xx_xx.dmp file in the bin folder under the installation directory of Hasleo Backup Suite, please send this file to us. Thanks.
the log file above is the only thing I had. I installed it on a brand new laptop as a test yesterday to try it and the laptop has been reset to factory and sent to a customer. I can't install it on my personal machine which is running perfectly
When creating a boot menu in HBS one is given the option to add drivers, i can not do that. The only thing that gets visible when i go to the driver, is the inf.files in the drivers folder. Anyone knows why this is, and how to fix it?
INF files contain all that is needed for a given DRIVER and its use (files and configuration), there should be one for every different driver on your System. You just need to know the names of the ones you think you need (I needed none for the testing, all needed drivers were in the base WinPE WIM).
Ok, thanks for the info. I have 2 Pc:s, and on 1 it works but this one, no. But now i added ALL the INF files i found on 2 new downloaded drivers, 4 of them, and it worked. But since adding them is a job that has to be done EVERY time, i will stick to IFW with it`s automaticity which equals speed. But i of course wonder how it can be that it works on 1 Pc, but not on another: What is the cause of that?
Are both your systems similar or same in regards to hardware configuration? I assume not if 1 works and the other does not using the standard driver inf files available in the WinPE.wim created by Hasleo. If they are the same hardware wise, it is strange having to add drivers for one and not the other.
Disimilar. One is an Asus the other a Acer. Both have Samsung 980 discs, one 980 Pro. The Asus with 980 works, but the Acer with 980 Pro do not. The fact that the boot menu do not work in Pre-Os even though i add the drivers as requested when creating it from the main Gui on the desktop is something i do not understand. When booting to the Pre-Os i have to do it again to make it work. And again and again. How it is with a Usb i do not know, have not tried it since it do not interest me.
It is likely the Acer has some proprietary hardware config, pretty common with some mfgr's such as Dell, HP, etc. Apparently the Asus is driver friendly in regards to how WinPE interacts with it. I wonder if there is a script that could be created to add drivers when you enter Pre Os boot menu. I agree, having to add it constantly is a negative, perhaps if you created a USB boot media and add drivers to it, that should take care of having to keep adding the drivers I would think as it would be written to the USB when created.
