We have compiled the ARM64 version of Hasleo Backup Suite, which means it is a native app for Windows 11 ARM64, you can now run HBS in Windows 11 RAM64 to back up your data, here is the download link:
https://www.easyuefi.com/backup-software..._ARM64.exe

Hello,

I am having an issue with recovering my backups.

I have this backup of my windows machine and every time I try to recover the files from its backup in bulk it gives this exact error: "The system cannot find the path specified. (0x0086008500000003)", I have been having this error with every single one of my windows backups, If I try recovering a singular file from it then its fine but the second I try recovering for example the Users folder or Program Files then it gives this error. 

But after some testing I found out that this is only a problem with the windows system backups and if I just do a file backup of my drive it works, I'm just confused why though.

Before version 4.9.5 I could make a hasleo iso on a uefi computer, put it on a ventoy usb key. The iso booted on the uefi computer of course and also on a legacy bios computer. With the latest hasleo version the iso does not boot on the legacy bios computer. I have to do the opposite, make the iso on the legacy bios computer, and it boots from a ventoy usb key on a uefi and legacy bios computer.

This is not really a problem. I would like to know if it is possible for all future hasleo builds to make an iso from a uefi or legacy bios computer always work on both types of bios from ventoy, to avoid making 2 isos for each type of bios.

Kind regards.

Hello,
I want to clone my system SSD (256GB) to a new empty SSD (1TB) but after starting the cloning it fails instantly with the API Error 0x00B4001500000000.

I attached the exported log files. 


Any help will be highly appreciated! 

Attached Files

  disk-clone-log-20241128114120.zip (Size: 12.23 KB / Downloads: 1)

Hey there,

I have a scheduled task that automatically runs a snapshot of c:\ twice a day. Command is:
wmic shadowcopy call create Volume='C:\'

Windows then stores these snapshots in C:\System Volume Information.
This enables the "Previous versions" feature in Explorer to be able to go back to an older version of a folder/file.

But what happens with those files on an image backup/restore scenario?

I tested different scenarios, here are the results:

--------------------------------------------------------------------------------
1. Image backup with HBS v4.9.5:

Behavior:
- All files in C:\System Volume Information are copied and kept in the image backup.
- On restore those files will be recreated but as empty 0-byte files.

Result:
- Restored Windows will not have Previous versions available in Explorer.
- No additional space is wasted in C:\System Volume Information.

--------------------------------------------------------------------------------
2. Image backup with HBS v5.0.0, VSS files filtered out (default):

Behavior:
- VSS files in C:\System Volume Information are NOT copied in the image backup.
- On restore those files are not available, no empty 0-byte files.

Result:
- Same as with HBS v4.9.5

--------------------------------------------------------------------------------
3. Image backup with HBS v5.0.0, VSS files NOT filtered out:

Behavior:
- VSS files in C:\System Volume Information are copied in the image backup.
- On restore those files are restored as well.

Result:
- Unfortunately Windows will NOT use those restored VSS files but still show 0 byte usage.
- Restored Windows will NOT have Previous versions available in Explorer.
- Those restored VSS files will be kept forever, resulting in less space available on C:\

--------------------------------------------------------------------------------
4. Image backup with Macrium Reflect v8.1.8311:

Behavior:
- Same behavior as scenario 2 (HBS v5.0.0 with VSS files filtered out)

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

So what do these tests show exactly?

I think the default behavior of HBS v5.0.0 (scenario 2) is perfect, as those files are not backed up anymore. This is also the default in Macrium.
If you change that filter option in HBS v5.0.0 and you keep VSS files (scenario 3), this will result in permanently wasted space after restore.

(?) For scenario 3, Windows will not use those VSS files after a restore anyway. So if the user removes that filter option this should maybe trigger a warning for the user? Or maybe this option should not be removable at all?

If Windows could be somehow convinced to reuse those snapshots in scenario 3, this wouldn't be a problem at all. But this is probably impossible..?

I have been running v5.0 beta for the last week or so... no problems.

However, I though it would be appropriate to go back to the official releases
so installed 4.9.5

For some reason, when running a backup, the Hasleo Suite just closes.

I guess there maybe some left over from v5.0 that is interfering?
Any thoughts.

Meanwhile, I switched back to 5.0 beta with no problems.

JD

Hello,

newbie question:
I have Macrium Home v8 installed. Can I iinstall and run Hasleo OS Backup/Restore on the same PC (incl. entries in boot menu) without these programs interfering each other?

Thanks.

PC: Win 7 Pro SP1 64-bit.

I have Hasleo Backup Suite Free, version 4.9.3, installed.  I verify the integrity of a backup image by selecting the below. By doing so, I expect the program to remember my choices.  Acronis and Macrium Backup systems do but Hasleo does not.  I have to enter these selections each time I do a backup.  Is there a way to make the selections stick?  I welcome all replies and thank you in advance.
  
1.  Select Disk/Partition Backup
2.  Select Backup Options
3.  Select Advanced
4.  Select Check the integrity of the backup image files on completion
5.  Select Complete image check

Hello,

I experimented around a bit with HBS 5.0 Beta and I think I found a bug which really should be looked at.

This is the scenario:
- A full disk backup is taken.
- You need to restore to a new disk which unfortunately is a little bit smaller than the original disk.
- This shouldn't be a problem as long as the current usage is below the new disk limit, right?

Unfortunately you cannot restore partitions with a smaller size, you get error 0x012C000A00000000.



I documented the whole process with different examples in a video:



Timestamps:
- 01:30 - Backup is taken (Windows 10)
- 04:58 - Disk restore #1 - Delta mode (successful)
- 06:06 - Disk restore #2 - Full mode (successful)
- 07:25 - Disk restore #3 - Full mode, smaller C: partition (error)
- 10:10 - Partition restore #1 - smaller C: partition (error)
- 12:50 - Partition restore #2 - smaller C: partition (error)
- 14:58 - Disk restore #4 - Full mode, smaller C: partition (error)
- 17:20 - Partition restore #3 - smaller System-reserved partition (error)

Hope that helps!

Hello,
  When i restart a server and Hasleo is running it doesn't detect the shutdown and it keeps backing up cause the PC to wait for the Hasleo service to finish.
I guess adding a timer detecting if the machine is shutting down or something to cancel the active backup should be ok.

Thank you

Attached Files

Thumbnail(s)