Hi warrior99 Please see my previous post on the solution that the Hasleo Support Team emailed me re. this: Hasleo Backup Suite Cheers, Balders
Yes Cyberlock will cause this (and am already in discussion with Dan about this) but if one follows the advice in the referenced post then one does not need to remember to upgrade I Install mode.
Hi All Just a quickie to say that it appears that the issue with the registering of bcdedit when adding the Boot Menu was indeed down to a bug in Cyberlock, which I do use. The developer, Dan, has today issued a new version that fixes the issue (am sure that a link to the latest version of CL has already been post over on the CL thread here at Wilders). Cheers, Balders
@Baldrick Posted the new CL link in the thread just now. https://www.wilderssecurity.com/threads/voodooshield-cyberlock.313706/page-771#post-3234892
I've said this before, but HBS is REALLY impressing me! I imaged my entire system, using the default HBS settings (56 gb of data), in 34 seconds! That's nuts. Reflect X was able to do the same thing in 36 seconds. My trusty IFW does the same task in 1:37 seconds. Yes, I image to and from two nvme drives (Samsung 990 Pro), but that's still very impressive. HBS even added a feature I requested, different power options for when an image is created versus when one is restored. More testing to follow.
I have 2 large HBS files on C:, the first is an Win.iso and the other is Winpe.wim in WDAK, now, which one can i erase? I suppose it is the iso since the other should be for the boot menu.
The .iso can be deleted, but I suggest you move it and not delete it. The iso is an emergency disk, so keep that on a flash drive. But the .wim for sure needs to stay, for auto-reboot restores.
The iso is in the Bin folder, removing it caused HBS to want to create a new boot menu when trying to restore. So that did not work ok. Now i am going to test with removing the other. Ha.
* When creating rescue media, winpe.iso will be created. * Run recovery from live Windows, HBS will create a one-time boot record using winpe.iso, and the computer will boot into the one-time recovery environment. * Add HBS to the Windows boot menu, winpe.wim will be created. Booting from this menu will use winpe.wim. Now you can painlessly delete winpe.iso, it will not take part in further backup/recovery operations. * Only if you run the recovery from live Windows again, or want to re-add HBS to the Windows boot menu, will winpe.iso be created again.
None of them can be removed if one wants the automated live recovery option, that was the result of my testing to remove any of them. When only removing winpe.wim, after going through the step in the live Os of executing a specific restore, it booted into the recovery environment as usual but nothing happened there by itself based on the former done steps. I had to do all the steps again to make the restore happen. So the automatic restore that one can start in the live Os and go away knowing that it will be executed all by itself, got lost with the removal of winpe.win. So my intention to slim the Os to get faster restores, could not be accomplished by removing large files as the mentioned. Both files has to kept for automatic restores initiated from the live Os.
When doing a backup, there is a slider on the page where the backup actually happens with the option - Priority. But never mind, it was not greyed out now.
5.4.2.1 was released. There are later builds that deal with specific issues that have not been generally released yet.
I just discovered Hasleo Backup and looking to use it. I noticed though that when I do a System or Disk/Partition Backup, then I go to restore a single file in File Mode, it doesn't list all the files and folders. Most importantly, the OneDrive for Business folder that holds my Documents, Desktop, etc. But if I use the File Backup, I can see all the files and folders when I go to restore. I went through all the backup and restore options and I don't see anything that would cause this. Here's a picture: https://i.ibb.co/4nLvMvdC/Screenshot-2025-07-19-103502.png
I'm not sure I would use FileMode for restoration of anything from an IMAGE vs a FILEBACKUP operation. The best way to dig files out of an image is to use the MOUNT option under the "Action" DropDown and actually mount that image as another DriveLetter. At that point you should see everything for access purposes on the newly mounted DriveLetter..
I tend to agree with this above simply because that extra FEATURE might end up recreating yet a different new issue for its standard purpose as a reliable backup image solution as originally designed when they have to yet again recode the whole program just to fix a file/folder feature
