Hasleo Backup Suite

Following....

 

When I created the emergency disk and chose download winpe components, if I recall, I pointed it to my USB UFD, and it downloaded the components, created the UFD rescue media. I tested that, it worked fine, no boot errors as I did not use the WinRE environment.

I noticed after that, there was a winpe.wim file not a ISO file because I had it create the USB rescue media. Had I not chose a USB drive then it would have created an ISO file.

@khanyash Thanks for the comments, glad Hasleo is working well for you. Definitely follow Froggie's advice and download those winpe components, make sure to delete the current winpe iso or wim as he mentioned before creating the rescue ISO so it gives you the proper option to download winpe, that solved my boot errors caused by a faulty WinRE.wim file in the recovery partition. That was caused by a June update to the WinRE.wim file.

I think you should be good with the winpe components...worked great for me. Let us know how it works for you and if you can boot on your Win 11 machine.

Thanks also @TheRollbackFrog and your comments on the boot menu. I didn't use that yet, but great information. Their reboot to restore kind of spoiled me.

 

Downloading WinPE seems to have fixed the issue. I appreciate your help and time. Thank you! @Jim1cor13, it worked great here too.

 

@Jim1cor13 - what actually happens is if you have rid yourself of the C:\boot Hasleo wim/sdi entries and any residual WinPE.iso from the Hasleo BIN folder, when you create the Emergency Disk with the Download files option, Hasleo creates the boot.wim for the UFD as well as a complete ISO in the Hasleo BIN folder (the UFD requires all the same files as the ISO contains for BOOTing purposes). The next time you create anything (a new UFD, an additional ISO or a BOOT menu item), Hasleo uses its resident WinPE.wim it first created to make anything new... it extracts whatever it needs from that ISO.

That's why you need to clear everything out to get that "Download files" option in the "Add driver" window. When I did the above operation, I found no WinPE.wim file anywhere following the download files creation, only a WinPE.iso in Hasleo's BIN folder.

 

I stand corrected on my above post... a WinPE.wim file is created in Hasleo's WADK folder...

 

Be aware though... the WinPE.wim in Hasleo's BIN/WADK folder is the naked (no apps installed) WinPE environment... Hasleo has to DISM that WinPE to add its application environment.

 

Thanks for the information @TheRollbackFrog

I know when you first told me about what to get rid of, so I would have the option available to download those components for winpe, making the rescue using winpe rather than it using the WinRE
environment took care of my rescue media boot problems.

I wonder how long it will take MS to actually issue a fix for their recovery boot UFD problems that some have? I can see the list growing of people mentioning the boot error I had and the missing ntoskrnl.exe
message, yet the only thing I have read is the advice to make a complete Recovery UFD drive, including all files necessary to reinstall windows, not just creating a "repair" boot UFD or disk. That in itself sounds like an admission
they screwed up the recovery partition WinRE.wim file.

 

I tried to restore a disk backup last night with Hasleo (latest version). Somehow, the restore scrambled my UEFI boot order so that the Windows Boot Manager was 3rd in line behind IPv4 and IPv6. I've successfully backed up and restored disk backups with previous versions of Hasleo, so why the restore went wrong this time is a mystery. Fortunately, I was able to fix things, but this one is weird!

 

That's an UEFI Firmware issue, not really a BOOT Mgr issue... for UEFI Systems, that's where the BOOT order is determined for those options.

I've seen my BOOT order change (not Hasleo related) sometimes when a BOOT was attempted without a real BOOT target determined (no EFI partition available), and when that happened, once a real target had been established, the scrambled order remained until I manually changed it in my UEFI firmware. I have no idea why it worked that way (HP OEM System firmware).

To maybe help the next time... if you don't use network BOOTing (IPv4 or 6), I would disable it in your UEFI firmware so it doesn't get in the way next time something like this happens.

 

You're welcome @khanyash !

Glad the download winpe worked, I know it worked great for me also. I don't want to create any more rescue media from the winRE environment if I do not have to. Since June update, Recovery media from WinRE will not boot
on my machine and apparently a growing list of others.

@TheRollbackFrog advice on that fixed my non-booting winre created USB UFD issue.

I like the winpe hasleo boot USB flash drive, it works and gets the job done quickly outside of windows, disk or partition backup is the choice outside of windows. Hasleo has been solid and very fast.

Just have to remember if you are going to only restore a single partition, make sure to choose "Partition Mode".

I hope they change this in the future to be a more fluid process to just choose whatever parts you want to restore or the entire disk, etc, like is common in other imaging apps. Not a big deal for me though.

 

I attempted to use Hasleo to create an emergency usb stick with WinPE. I used Hasleo's utility to download the WinPE files from Microsoft. When I attempted to install the WinPE files (again using the Hasleo's utility) it stated that my usb needed to be reformatted. I clicked ok or yes. At that point the process started and then Bitdefender kicked in and stopped the process and Hasleo quit. At that point, there was no Start menu or icon for Hasleo. Apparently, Bitdefender stopped the process and Hasleo from working. I attempted to re-install Hasleo, but it found another instance of Hasleo on my PC. So, I hit Yes to uninstall the old version and it errored out. Then, I attempted to delete the entire Hasleo folder and it stated that I didn't have administrator privileges to do that. So, now I have a version of Hasleo on my system that doesn't work and an inability to reinstall the program. This was all on a Windows 10 machine. So, I went to my laptop which is running Windows 11 (and Bitdefender) and the same thing happened to my laptop. So, now both of my computers have a defunct installation of Hasleo Backup and both have an inability to delete the Hasleo folders or reinstall the program. Any assistance would be appreciated.

 

@Alexhousek - if bitdefender didn't copmpletely mungle the Hasleo installation, AND the unInstall LINK is still in the Hasleo START folder, try and use the unInstall link by <right-click>ing it and select "Run as administrator"... no guarantees . If the START menu LINK is missing, go to the Hasleo installation folder and try the same with unins000.exe.

 

The start menu link is gone. Upon right clicking the unins000.exe file in the Hasleo installation folder, and running as administrator, I receive the following error: Hasleo Backup Suite\unins000.dat does not exist. Cannot uninstall.

It looks like I might have to try Revo or Uninstaller to try to get rid of the remnants?

 

If you're able to clean up the AV mess, I'd make sure you protect any new installation from BitDefender... sounds like it's pretty aggressive.

 

I noticed that TheRollbackFrog commented in the Hasleo Forum that you can not subsequently change the destination for the backups.

However it seems that you can not have backups with different destinations. If you do not use the default destination in settings, the backup will fail saying the path does not exist.

 

Just perform an overinstall of Hasleo, but first add the installer to the exclusions of your security software. After installing Hasleo, exclude the Hasleo folder in Program Files too.

 

Improved GFS (Grandfather/Father/Son) image scheduling/retention in Beta v4 available HERE...

 

Have set up the new Hasleo GFS scheduling to duplicate my Macrium REFLECT GFS scheduling starting today (1st of the month)... 2-monthly FULLs, a weekly DIFFERENTIAL and 7-days of INCREMENTALs (which merge forward to keep the image chain in tact). I use DAYs for Incrementals because I'm always adding MANUAL Incrementals into the chain when I'm snapshotting my System while testing/updating, etc. and the number generated during 1-week's time varies from week to week.

I will report back with any anomalies discovered.

This effort by Hasleo has almost duplicated Macrium REFLECT's effort in the disk imaging arena. The last major feature missing is the DELTA restore capability (very fast) which will be a tough one... we'll see.

 

Since it executes fast restores already, Delta restore on top of that would be - WOW.

But they have some issues to fix, which can be seen in this thread, before it is reliable enough to depend up on trustfully. If they can do that, this one is a real contender to MR and IFW, for instance.

 

Hi @TheRollbackFrog

I was just wondering how things have been going with the GFS model of imaging with Hasleo.
Looking forward to reading your experience thus far. Thanks!

 

It's only been 6-days... so far so good. This coming Sunday will be my 1st DIFF and the automatic INC merging should start on Monday. Once the merging starts and INCs begin to disappear, I'll do some restoration testing with the merged image chain. I'll drop a line on Wednesday or so with first weekly rotation and restoration results.

 

Sounds great, appreciate the testing and look forward to your thoughts and how it handles GFS.

 

My system has some problems. And it appears the issue mentioned is because of the system and not Windows. I'm testing the latest beta and added the boot menu with default WinPE. Sometimes I experience the issue mentioned and sometimes not. I faced the same issue with the downloaded WinPE too. So, the problem seems to be with my system and not Windows.

I noticed that if I tilt the system or shake it, sometimes the process moves and everything goes well. chkdsk and sfc scan found no errors. HDD is placed and fitted well.

 

Thanks @The RollbackFrog

 

Hi @khanyash

This sounds like either hardware issue, or perhaps a Win 11 install issue? Perhaps memory modules that need reseating or perhaps something that is loose as your system reacts to shaking it or tilting it?

Did you install Win 11 on a system that did not really support it by bypassing some criteria or is it a regular install, all supported hardware such as TPM, CPU and Video graphics?

I think the boot menu issue using the Winpe and its failure sometimes may have to do with your boot manager? My boot problems had to do with allowing the use of WinRE to create their "pe" rescue media. The WinRE environment at least on Win 10 was broken from an update to the recovery partition in June from what I understand. More folks are finding this out, yet MS has done nothing that I am aware of to fix it. Downloading the PE components from the option in Hasleo took care of my boot error, which was claiming I was missing "ntoskrnl.exe" on the boot media.

Are you getting an error or it will just not boot?