Hasleo Backup Suite

I still remember all the excitement of people using AX64. Even after it appeared to be dead, some people were still asking about it.

 

Not AX64 so much myself, but i still to this very day experience pinpoint excellent results locally from Isso's predecessor Defrag Program he was instrumental in with UltimateDefrag development team. OT

Ran into an anomaly my first backup of all things with HBS. I hope to conduct another try and spend additional time to determine exactly what on my end caused HBS to abort 3/4 the way imaging. In the meantime Aomei Backupper performed w/o error after the snafu. Chances are or it might be one of my Security Programs caused the HBS to stop imaging w/ it's abort notice.

If it continues i will Contact HBS with the info/log of the interruption. Caught me by surprise.

 

It appears Microsoft fixed the WinPE issue with recent Windows updates. I have no problem with Hasleo on the problematic system now.

 

Froggie, if you see this.

I had used Hasleo to build recovery media, but I do not have it added as a boot menu item.

when I attempt to a restore from within windows it says that it must build some media before it can continue. I have done that in the past, and it continues, but the next time I am trying to do a restore from within windows it says that it has to do that all over again.

Does it not store that somewhere? Is that what you were referring to?

 

It usually builds a basic ISO and keeps it in its BIN folder. When you re-install new versions, it will have to do that all over again.

I will also check this for you...

 

I do see a winpe folder in the bin folder - it is approx 50 meg.. I wonder why it doesn't just use this? Is this what you were referring to above?

 

No. Hasleo needs to create an ISO file to use for the automatic restore... or any other type of restore (BOOT menu or a UFD). If it's never been created before (no BOOT menu in use or no Recovery Media since the last installation), Hasleo will need to create it for its first use. If that use is with an automatic restore to a previous time point, it will create it but after the automatic restore, it will be gone (since it wasn't in your previous time point. This will go on infinitum as long as you're headed backwards in time.

What I do, following a new version installation, is use the Emergency Media tools option and create an ISO option (not a UFD option if not using Recovery Media... which I would definitely have, BTW). Have it put your ISO file somewhere and let it finish (I use it to create my Recovery Media for HASLEO). After it does, you can delete the ISO file it created for you because it now will have a reference file (WinPE.iso) in its BIN folder. Any image after this will contain that ISO file and will be always available for your automatic restore... no more re-creation.

 

The WinPE folder you see is not a WIM or ISO file, it's elements that are used to build those files.

 

excellent I never thought of that.

I have the emergency media tool, ( but it still told me that it had to build a winpe file before it could restore my image after reboot)

and I don't see how to make this iso option?

 

Ok, I got it. Apparently when I made the emergency media on UFD it did not store it in the bin folder. But now that I found how to make the iso, I checked the bin folder and sure enough the copy is there.

I thank you again!

 

----------------------------

Unable to create WinPE.iso
Hi. I’m a newby and with a Windows 10 22H2 PC, I made some backups with Hasleo v4.0.
Today I realized that WinPE.iso was not present in the Hasleo ‘bin’ folder.
I then launched the emergency disk creation procedure. After about 1 minute, the procedure stops at 63% and there it stays forever (the background Hasleo Backup Suite Service Application process is shown as "suspended"); I cannot close the application and the only way I can break the situation is to reboot the PC.
I tried several times with the same result.
Looking at the contents of disk C: I noticed that a “WinPETem” folder had been created with a new folder inside named 55ce1990-2ca1-4c0e-af66-6c455aad8d84 with subfolders:
C:\WinPETem\55ce1990-2ca1-4c0e-af66-6c455aad8d84\
ISO\boot
ISO\efi
ISO\source
mount\Program Files
mount\ProgramData
mount\sources
mount\Users
mount\Windows
I also noticed that each time I tried to create the emergency disk, a subfolder similar to the one described had been created in C:\WinPETem.
I am Administrator with full control over disc C: and I tried to delete C:\WinPETem. But the deletion is not allowed.
For info I have a second "photocopy" PC where the iso creation worked correctly and where no C:\WinPETem was created.
I tried to re-install v4.0 without success.
I don't know what to do anymore and especially I don't know how to get rid of the C:\WinPETem folder which has reached 16 GB !!...
I don't know what to do anymore. Any advice? Thanks

 

This is a very unique problem to the System you are referencing, possibly an AntiVirus issue. I would suggest you COPY the above Forum post and paste it into a newly created Hasleo Forum post located HERE (after creating a presence). Their developers will respond quickly to your issue much better than we can, I believe.

Wish I could help more...

 

Your process was clearly in the middle of a WinPE WIM build (used in the ISO) when it got hung up.

 

@TheRollbackFrog
Thank you very much for your response. I followed the advice and posted in the Hasleo Forum.
In the meantime I managed with difficulty to delete the C:\WinPETem folder by booting with Linux, but now I am afraid to run the emergency disk creation procedure again.

Thank you anyway

 

hi
is there a rapid (like macrium) or restore changed sector only (like image for windows/linux/dos) similar feature ?
thanks

 

@stapp - sorry I can't find the reference I was speaking about above (I did read something, though ). Their most recent mention of this capability says they are looking into it at the moment.

 

I don't want to cause any confusion on this topic, but I thought I had successfully completed the procedure above (The creation of the winpe.iso file, and the usuage of that to make emmergency media). All seemed well but this morning when I attempted to boot, I had problems. It kept asking me to insert a bootable media and restart. The only way I got it fixed was to restore a previous image.

When I initially let Hasleo create the UFD at install everything worked fine but I did not have the winpe.iso folder in the bin folder

Something doesn't seem right here, but unfortunately I don't have the expertise to help out at all. Just thought I would mention I also had trouble with this procedure.

 

@mantra - that feature is optional (via checkbox) in their current v4 Public release HERE.

 

@jima - it's not clear to me what you mean when you say... "The creation of the winpe.iso file, and the usuage of that to make emmergency media." Exactly what did you do? During this morning's attempted BOOT (just a power up...), it sounds like your BiOS BOOT order is not set to BOOTmgr which will normally BOOT your OS first in the list. There should have been no reason to ever change that.

There is no WinPE.iso folder... when a successful Recovery Media has been made, there will be a WinPE.iso FILE in Hasleo's bin folder.

I'm still a bit confused on what path you actually followed when you first installed Hasleo Hasleo... To get back in sync you can re-install the latest version and have it uninstall the version it finds on your System during this process... that should get you back to ground zero

 

right, sorry about the file vs folder.

When I initially installed Hasleo, I let the program make the emergency UFD, instead of making an iso file and then installing it on a UFD. All worked fine, but I did not have the winpe.iso file in the Bin folder as you described to me earlier. Therefore I reran Hasleo and got it to write the iso. file to my desktop. I then used Rufus to re- create my rescue media. Does this make sense?

I have an image before I installed Hasleo. I will go through the process again with a fresh install as you suggested.

 

@jima - I just did my suggested procedure. On a clean System, I re-installed HBS. From there on, unless you image your System first then try to go back to that image (where the automatically created WinPE will get lost), any operation you perform (automatic restore, UFD creation or personal ISO creation) will produce the WinPE.iso in Hasleo's BIN folder that it will use for any further operations. That's why when you first install HBS, you should create your Emergency Disk before you do any imaging or restoration. After that point, the reference WinPE.iso that HBS uses will always be in any image you create, and will be used for any operation you do.

Be it known... the WinPE.iso it creates will be based on your System's resident WinRE.wim located on your System's Windows Recovery partition unless you check that "Download from Microsoft" option during the creation of the needed media. Recently there have been problems with lots of apps that use the WinRE.wim to build their recovery media. This was a result of MicroSloth screwing up the Recovery Media's WinRE.wim (Sept. time frame) during some System update. It supposedly was fixed by the end of November. Due to this anomaly, I now only use the MicroSloth download to build the initial WinPE.iso (all apps that offer that capability) as long as the basic (rather than extended WinRE) WinPE download runs my Recovery environment without issue... much safer.

 

Thanks for the testing.

Good to know, I was doing a lot of testing of images when I first installed it. I must of done what you said (made and image before I created the emergency disk) and then reloaded that image.

Do you think it would be worthwhile to re-do this if I didn't use the MS download to build the initial winpe.iso?

It's amazing how much trouble and confusion you can cause when you're 75 and just learn enough to do something, but do not have a full understanding of the process.

But thankfully with the help I get here, I eventually get it sorted.

 

hi @TheRollbackFrog
can i ask you is this feature stable and reliable?
can I ask you from where is the company ? just for support
thanks