Usually, the user expects the uninstaller to remove all traces of the program installation. In our case, the uninstaller works sloppily. The program folder with logs inside, <ID>.SDI and <ID>.WIM files, registry keys are not removed. This is despite the fact that the program is light and does not dig deep into the system.

It's not about the date format, it's about the fact that the time stamp displayed in WinPE is completely incorrect. Below is an example with a backup created from under Windows.
In HBS v4.4 under Windows, the time stamp is 08:35 on March 30, which is the actual correct time.
When booting into WinPE, the time stamp is distorted: 22:35 on March 29.
This is extremely confusing for the user, causing a lot of inconvenience by having to calculate and match the false time to the correct time.
In my opinion, this is a serious flaw. The same problem was originally in Macrium Reflect, but the developers have successfully solved it.

Hey guys, first time user and lover of WinToUSB but I have some problems that I would like to seek guidance on.

I have created a USB-C Windows 11 installation using WinToUSB and everything appears to be working as designed. I am using this on a Lenovo Thinkpad T14s Gen3 device. The issue I have is when I reboot or shutdown the laptop from the Windows 11 WinToUSB installation the machine will stay powered on, that is, black screen, no activity. The only way to power off is to hold the power button for 5-10seconds, and then upon power on I can select the USB-C disk again and it boots into the WinToUSB installation normally (no errors about incorrectly shutting down or anything)

I am convinced this is likely a BIOS / Configuration issue in some way - can anyone assist?

Thanks

Hello Hasleo Admin Team,

we know this doesn't really fit into a product like Disk Clone and maybe another product or a product rename would be necessary, but has Hasleo ever considered to integrate a File Clone feature (just like the File Backup feature in Hasleo Backup Suite)?

What is the background? Well, we would like to clone files from one drive to another drive directly, without having to first backup the files into a File Backup image and then having to restore data from it again, instead why not having a File Clone feature, which offers to clone files from one source to another target directly? Yes, that would be some kind of Robocopy replacement!

Maybe Hasleo Clone Suite would be a perfect name for a product to clone disks or clone files directly to another target?

Just a thought.

Regards,
Marcy

After updating to version 4.4 (from 4.0), the Backup Suite crashes when attempting to use the command line, necessitating a reinstall.

However, the same tasks run successfully from the suite on demand and on schedule.

Nevertheless, I prefer to utilize the command line within a PowerShell script that executes additional backup steps.

"C:\Program Files\Hasleo\Hasleo Backup Suite\bin\BackupCmdUI.exe" /a run /g $guid /t 0

Attached Files

Thumbnail(s)
   

  backup-suite-log-20240321113231.zip (Size: 31.64 KB / Downloads: 2)

Hello Hasleo team,

are you aware that restore request cannot be stopped even in version 4.4?

The cancel request is not working, even with PE Boot, the restore cannot be stopped, if you click “Cancel”,
all partitions have already been deleted and you need the Hasleo USB stick to restore the image.

A user may have forgotten to back up data and is unable to stop the restore process.
That could be a problem. 

Do you get the update notification only when you open HBS?

The update re-enables the check for updates option.

I updated to v4.4, and it didn't notify me to recreate the boot menu.

The tools "Clone" does not work for me. I have windows 10.

Today I tried this for the first time... and it was somewhat successful.  What was very strange was that HBS wanted to leave the OS and reBOOT into the pre-OS environment in order to accomplish this imaging operation... I have no idea why.

The UFD being imaged was a BOOT device but not active in any way (that I could tell), just plugged into the System.  The target device for the image was the same as I use for all the rest of my LIVE OS imaging.

I don't see why that operation should be any different than my normal System imaging operation... remember, I'm IMAGING, not RECOVERING.

Do we have a problem here that I'm not aware of...?

Hi!
I got an error doing 'system clone' (I guess so in english, right?) in 'Hasleo Backup Suite'.
I was trying to copy system from a wd sata ssd 240GB to sk hynix Gold P31 (1TB).
It says...
Failed to run system API.(0x07F1001502AF0059).
Attatching log files below.
Please help me.

Attached Files

  backup-suite-log-20240307130043.zip (Size: 17.2 KB / Downloads: 2)