When trying to backup my internal C drive and have ticked destination drive and address I click proceed and I get error message "you cannot backup to the same drive as you are backing up" 

Error message no.: 0x0194005300000000

This backup suite is fantastic and very fast, previously all plain sailing, but just can`t get past this. Please help me. Thank you.

Windows 10 Professional (x64) Version 22H2 (build 19045.5854)

Hello,
I created a rescue ISO on laptop 1 with the current Hasleo version (5.2.2.3) and tried to boot WinPE on laptop 2. However, this didn't work. After a short loading time, the laptop restarts.
On laptop 1, on which I created the ISO, the rescue system loads without problems.
I found an old rescue ISO that I created with a Hasleo version around 4.9.2. This ISO boots on both laptops.
Then I created a rescue ISO on laptop 2 with Hasleo 5.2.2.3, but this ISO also didn't boot on laptop 2.
The cause may be that the CPU of laptop 1, on which the new ISO boots, supports SSE 4.2, but the CPU of laptop 2 doesn't.
Have you changed anything related to the creation of rescue ISOs since Hasleo 4.9.2?

Regards, Markus

Hasleo Backup Suite V5.2.2.3 Released!

What's new in this version:
1. Fixed an issue where drives might not be assigned drive letters in WinPE
2. Fixed an issue that prevented changing backup task destination paths
3. Fixed an issue with the image merge functionality
4. Fixed an issue that could cause slow shutdown
5. Fixed other minor bugs

Here are the download links:
X86/X64
ARM64

Error Messenger

Good day!

I encountered a situation.
I make a backup of the system disk and the program consistently hangs the system at 7-8%.
If I make a backup via WinPE, then everything works fine. That is, there are no errors on the disk.
Maybe the problem is in shadow copying?

Win10 x64 Home, HBS 5.2.2

Everything works stably on other computers.

Hello,
  Seems the latest windows updates have update the EFI partition and now Hasleo doesn't recognize them report "partition not found error".
As you can see from the screenshot of Win2025 it unchecked 2 partitions from the disk.

Attached screenshot and logs

Attached Files

Thumbnail(s)
   

  backup-suite-log-20250514221027.zip (Size: 7.22 KB / Downloads: 34)

Greetings. I have been working with support about multiple backup sets and by their answers I fear that I may not understand how Hasleo handles backups.

My schedule stipulates a new full backup every Sunday night. I also have a differential backup run every Monday, Tuesday, Wednesday, Thursday, Friday and Saturday night.

I am assuming that each of these differential backups relates to this first full backup.

I have scheduled a new full backup to run every Sunday night and then differential backups like before.

Here is my main question:

Do I assume correctly that the second set of differential backups will relate to the NEW full backup and NOT back to the initial backup or is this incorrect?

I fear I may not be clear on your programming with a schedule like this. Can you help me understand this basic question. Thank you for your kind help.

Hey, currently I'm trying to make portable windows with external hdd reason is due to work and I don't want to dual boot windows either. I know in windows there is an app called wintousb to make this a bit easier so is there a similar app on linux too? Because windows can't be installed through a usb I'm a bit at a loss at what to do here

Hasleo Backup Suite V5.2.2.2 Released!

What's new in this version:
1. Fixed an issue that caused the service program to crash
2. Fixed an issue that caused disk backups to fail
3. Fixed an issue that caused file restoration to fail
4. Fixed an issue that caused the progress of checking image files to be incorrect
5. Fixed an issue where Hyper-V didn't work after rebuilding WMI
6. Fixed an issue where months may not be automatically selected in the monthly schedule

Here are the download links:
X86/X64
ARM64

Hey,

I just discovered that I can't connect to my Synology NAS via SMB2/3 anymore when booting from the WinPE rescue media. Pretty sure this had worked in the past already.

Rescue media was created with:
- current Windows 11 Pro build 24H2 26100.3775 (German)
- Hasleo Backup Suite v5.2.2.1

When booting from the created WinPE I get the following error when trying to connect with "net use":
System error 1727, Remote procedure call failed



--

When I try to use the PE network manager, I get these errors instead:
An error occured while starting the TCP/IP Registry Compatibility service (2)! Program will exit now.



--

The program won't exit though and I can try to connect with the same settings I used with "net use". This exits with the following error unfortunately:
The remote procedure call failed and was not executed.



--

I then recreated the boot media with a more recent Windows 11 test build:
- Windows 11 Pro Canary build 27823.1000
- Hasleo Backup Suite v5.2.2.1

When booting from this test build, everything works as expected as shown in this screenshot:



--

Booting from a current Windows 11 image and trying to mount the path directly also works (after an initial "wpeinit"):
- Windows 11 image: de-de_windows_11_consumer_editions_version_24h2_updated_april_2025_x64_dvd_ea86301d.iso



--

So I'm not sure what the problem might be.

Is there a bug in the current Windows 11 version or is something wrong with my Windows 11 build?
Can anyone reproduce these problems?

Thanks!