I am a legitimate ltsc user and I just found out that I can no longer create recovery media/emergency disk. Why the hell was this removed. Hasleo was the best imaging tool I have used and it was putting macrium reflect to shame, but now I am unable to create a boot disk for data recovery. At least they've removed the expiry date but why on earth did you remove the iso creation tool

I also can't create a boot menu!!! How am I supposed to use this thing?

For context, I am a single PC, NON commercial user who happens to be running the Enterprise version of Windows (like a lot of people who run it for personal use). I had a major crash tonight, and when I went to restore I was met with the message stating that my version is no longer supported. Honestly, Hasleo has been a pretty decent software up until this change, but this was a real shock to me, and the timing couldn't have been worse. I guess shame on me for not keeping up on the terms/changes, but I never would have expected that.

I genuinely thank your team for the software experience up until this change, but since I am not using this software in any commercial capacity whatsoever, I do not believe I should have to pay for the license all of a sudden. If I actually had money I would gladly donate to you guys.

Why is delta restore not working when restoring to bitlocker encrypted drive.  It automatically does a full restore in windows re even if I leave delta restore checked when initiating restore from windows. After restore bitlocker is automatically disabled and I must encrypt the drive again.

Being nosy: when creating an OS backup, HBS creates the folder mentioned above, and keeps it even when the backup is finished. What is this folder needed for?

Thanks.

(Win 7 Pro SP1 64-bit.)

Hello all,

inside DiskCloneService.exe I've seen a reference to DiskCloneUtils.exe but I was unable to find this executable among those installed by current/latest Disk Clone v5.6.2.0.

Any idea why ? Could anyone be so kind to tell me something more about it ?

P.S.  I have a Professional license. 0:-)

Thanks in advance for your attention.

Best Regards
Rob

Hello all,

could anyone please be so kind to give me a definitive confirmation that Disk Clone fast cloning also indeed properly manage a fully complete and exact copy of disk signature (for MBR disks), disk GUID, & partition GUIDs (for GPT disks) ?

I'm indeed already expecting this to happen properly, but this weird doubt came to my mind after carefully reading following sentence excerpted from page '[Solved] How to Clone a Disk to Another SSD/HDD Sector by Sector' :
"Fast cloning only copies the sectors containing data from the source disk to the destination disk, making the process very fast. In contrast, sector-by-sector cloning copies all sectors on the source disk, one by one, to the destination disk. As a result, the destination disk is an exact copy of the source disk after the successful cloning, including the disk signature for MBR disks, disk GUID, and partition GUIDs for GPT disks. If you are worried that fast cloning may cause data loss, sector-by-sector cloning is your best option."
Because of above wording it may, unfortunately, even seem that "... disk signature for MBR disks, disk GUID, and partition GUIDs for GPT disks." might just be included in the cloning process only when sector-by-sector is the chosen cloning method, "...in contrast..." with what instead fast cloning copies (since it "...only copies the sectors containing data from the source disk to the destination disk.").

P.S. I know that by asking to have such additional clarification I may a little look like I'm playing devil's advocate, but I believe that above message is not so fully crystal clear as it should instead be, and so I'd like to suggest to also add there a little clarification that might possibly avoid anyone else to have a doubt similar to the one I had.   0:-) 

Many thanks in advance for your so kind attention.

Best Regards
Rob

Hi,

Just update to version 5.6.2.0 to confirm what I am about to describe still exists in the latest version.

I made a Disk/Partition backup and selected whole disk. The disk includes partition which has volume letter D. Backup itself finishes without errors.

Next I choose restore, then select task to restore, and select the backup task I just created. I click Next. I switch to the File mode. I select root folder and set the restore to -location as C:\. The backup inclues some files with very long path and file names. Those do not restore successfully. For example:

Hi there.

Before I move on to a different backup solution, I want to see if there is a fix for this:

Error while trying to do a System backup:
The system cannot find the file specified. (0x0095007F00000002)

Latest Hasleo Backup version but, started happening with several versions back.
Happening on several PCs.
This does NOT happen with other Backup software (Macrium Reflect finishes the backup without error).

From the Hasleo Log (below), it shows the shadow files being the issue:

2026-02-04 15:55:57 T:0000B37C 87 - Deleting shadow copy set {4d54d302-e714-4936-80d4-d67c73cda2b4} ...
2026-02-04 15:55:57 T:0000B37C 87 Error while deleting shadow copies...
2026-02-04 15:55:57 T:0000B37C 87 - Last shadow copy that could not be deleted: {00000000-0000-0000-0000-000000000000}
2026-02-04 15:55:57 T:0000B37C 87 ERROR: COM call L"m_pVssObject->DeleteSnapshots(snapshotSetID, VSS_OBJECT_SNAPSHOT_SET,FALSE,&lSnapshots,&idNonDeleted)" failed.
2026-02-04 15:55:57 T:0000B37C 87 - Returned HRESULT = 0x80042308
2026-02-04 15:55:57 T:0000B37C 87 - Error text: VSS_E_OBJECT_NOT_FOUND

I can see shadow copy created when backup started shows up, nothing else.
vssadmin list shadows
After backup finishes, shadow list shows empty.

Already tried VSS Repair, checkdsk /f, dism /restorehealth and sfc /scannow.


Hasleo Log:

...
2026-02-04 15:55:57 T:0000B37C .\ImageMaker.cpp 630 nRet=0x0095007F00000002
2026-02-04 15:55:57 T:0000B37C .\FilePublic.cpp 1807 nRet=0x070E007F00000002
2026-02-04 15:55:57 T:0000B37C .\IncompleteBackupHandler.cpp 172 nRet=0x070E007F00000002
2026-02-04 15:55:57 T:0000B37C .\ImageWriterCluster.cpp 173 nRet=0x070E007F00000002
2026-02-04 15:55:57 T:0000B37C .\DiskBackup.cpp 447 nRet=0x0095007F00000002
2026-02-04 15:55:57 T:0000B37C 149 - Mark all writers as succesfully backed up...
2026-02-04 15:55:57 T:0000B37C 149 Completing the backup (BackupComplete) ...
2026-02-04 15:55:57 T:0000B37C 127 (Waiting for the asynchronous operation to finish...)
2026-02-04 15:55:57 T:0000B37C 127 (Waiting for the asynchronous operation to finish...)
2026-02-04 15:55:57 T:0000B37C 87 - Deleting shadow copy set {4d54d302-e714-4936-80d4-d67c73cda2b4} ...
2026-02-04 15:55:57 T:0000B37C 87 Error while deleting shadow copies...
2026-02-04 15:55:57 T:0000B37C 87 - Last shadow copy that could not be deleted: {00000000-0000-0000-0000-000000000000}
2026-02-04 15:55:57 T:0000B37C 87 ERROR: COM call L"m_pVssObject->DeleteSnapshots(snapshotSetID, VSS_OBJECT_SNAPSHOT_SET,FALSE,&lSnapshots,&idNonDeleted)" failed.
2026-02-04 15:55:57 T:0000B37C 87 - Returned HRESULT = 0x80042308
2026-02-04 15:55:57 T:0000B37C 87 - Error text: VSS_E_OBJECT_NOT_FOUND
2026-02-04 15:55:57 T:0000B37C .\VolumeShadowCopy.cpp 979 nRet=0x03D2015080042308
2026-02-04 15:55:57 T:0000B37C .\VolumeShadowCopy.cpp 217 nRet=0x03D2015080042308
2026-02-04 15:55:57 T:0000B37C .\DiskBackupWrapper.cpp 422 nRet=0x0095007F00000002
2026-02-04 15:55:57 T:0000B37C .\DiskBackupWrapper.cpp 866 nRet=0x0095007F00000002
2026-02-04 15:55:57 T:0000B37C .\DiskBackupWrapper.cpp 2332 nRet=0x0095007F00000002
2026-02-04 15:55:57 T:0000B37C .\DiskBackupWrapper.cpp 2342 nRet=0x0095007F00000002
2026-02-04 15:55:57 T:0000B37C .\DiskBackupWrapper.cpp 1682 nPos=100
2026-02-04 15:55:59 T:0000B37C .\BackupWorker.cpp 282 nRet=0x0095007F00000002
2026-02-04 15:55:59 T:0000B37C .\BackupWorker.cpp 1540 nRet=0x0095007F00000002
2026-02-04 15:55:59 T:0000B37C .\WorkerPublic.cpp 1236 nRet=0x006E001600000000
2026-02-04 15:55:59 T:00008758 .\BackupWorker.cpp 1351 nRet=0x0000000000000000
2026-02-04 15:55:59 T:0000B37C .\BackupWorker.cpp main 1657 End...


=====================

vssadmin list shadows

shadow copy created when backup started shows up, nothing else.
After backup finishes
Shadow list shows empty.

Hope this can be fixed as I like Hasleo and want to support them.
Thanks.

What is the difference between the two software tools

Hasleo Backup Suite vs. Hasleo Disk Clone?

They seem to cover a similar functionality.
Is one a subset of the other?

What can I do with Disk Clone what I cannot with Backup Suite?

Assume I want to transfer the content of an internal m.2 SSD with multiple partitions (with one of them Windows 10) to another (bigger) SSD (which shoule later replace the first).

What is the Hasleo tool of choice for this task?

The EasyUEFI domain works fine but the SUBJECT domain is now inaccessible.  Most web references now fail... (don't know when this started)