OS: Windows 11 25H2
Hasleo Backup Suite: V5.8.2.1
ADK: 10.1.26100.2454 (December 2024) installed
WinPE Add-on: installed

Error: Failed to create (start) process. (0x01CF001E000000C1)

copype.cmd works manually only when WinPERoot, OSCDImgRoot
and DISMRoot environment variables are set manually in CMD.
Hasleo seems to not set these variables when spawning its process.

Hi,

I was experimenting a bit with Windows 11 Canary version 29585.1000 (Insider Experimental Future Platforms) in VMware Workstation.
I made an HBS image backup to a second internal drive, which I now tried to restore from within Windows.

Restore process started successfully, Windows rebooted into WinPE. But it then took a few extra seconds to load up HBS, showing only the screenshot tool in the meantime.
When HBS finally showed up, the restore process didn't start automatically. Instead I was given the normal HBS window in "Home" tab:



Logs from the WinPE HBS are attached, maybe this helps with the diagnosis. Using the current HBS version v5.8.2.1.

BTW: After manually starting the restore from the backup task, it finished without a problem, so this is only a hiccup with the auto select.

I couldn't reproduce this behavior on current Windows 11 or any older versions so I think this might be something new, possibly introduced by MS.
Please note: I haven't tested the outcome with the current latest Canary version 29599.1000 so far, but I'd assume it's still the same.

Hope that helps 

Attached Files

  backup-suite-log-20260531224012.zip (Size: 10.54 KB / Downloads: 1)

This post is quite long but that is necessary to explain the experiences.

HBS File Backup was scheduled for five different backups of folders on the D: drive. Incremental backups were scheduled for weekly with a full backup to be done after 4 incrementals. The target of the backups is a OneDrive folder on my C: drive. OneDrive automatically duplicates any changes in this folder to the cloud. The plan was to use the Explorer option "Free up space" on the folders to save space on the C: drive and to prevent this data from being included in the System Backup. "Free up space" keeps a small stub of the file/folder on the C: drive with the full version retained in the cloud. The step was applied after the completion of one full backup and two incrementals, not after each backup. Some unexpected results were experienced on the next scheduled run.

HBS did not like the stub versions of the previous backups.
- In four cases a new Full backup was created (an incremental was expected). The backup created was named "File Backup yyyymmddnnnnn_yyyymmdd_Full_V1_1.DBI". The first yyyymmdd was when the first full was performed, and the second is the date of the recent backup. This resulted in two files with the sub name of Full_V1_1. It is now impossible to mount that backup. The workaround was to rename the file to use the next number in the sequence, e.g., Full_v4_1.
- In one case the backup failed, reporting "No backup image was found (0x00B5013000000012)". Trying to manually run an incremental backup on any of the five backup resulted in the same error.
- The Error Log did not show any errors

Some solutions:
- not to use the "Free up space" feature, but then the System Backup will contain those files. Only the paid version of HBS allows a custom filter to be set.
- relocate OneDrive from the C: drive to another drive, but that only solves the System Backup file/folder inclusion

 I had previously used a program called Perfect Backup for backup of the data files. It successfully performed full and incremental backups even with the "Free up space" applied. It was smart enough to know what files were changed or deleted, so that a restore at any incremental point recreated the reality at that time.

Still trying to decide how to proceed, but suspect that going back to Perfect Backup is the solution.

Hi everyone,
I’ve recently been working with multiple OS installations and testing environments for different web and community-related projects, and managing boot entries has become more important than I expected.
I came across EasyUEFI while trying to organize boot options and troubleshoot some EFI issues after Windows updates changed my boot order. So far it’s been useful for managing entries without constantly going into BIOS settings.
Most of my work is related to online community platform projects and testing different server environments, so having stable boot management really helps during development.
Curious how others here handle multi-boot setups, EFI backups, or recovery situations when boot entries disappear unexpectedly.

When using the "Emergency Disk" tool to create a bootable USB disk to boot from for Restore or other work I noticed the following behavior.

Hardware: SanDisk Ultra USB 3.0 64GB 


The Flash drive is recognized and shows as 57.29GB 

   

However, the Flash drive is formatted to 31.9GB thus losing 30GB of usable space. 

   

Similar Backup programs that create Rescue Disks format to the full size of the Flash drive. Why is Hasleo not using the full size?

Yes, I can create a new partition and use that if I want to copy other files to the disk but it's an unexpected extra step.



DISKPART> list disk

  Disk ###  Status        Size    Free    Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 8    Online          57 GB    25 GB


DISKPART> select disk 8

Disk 8 is now the selected disk.

DISKPART> list part

  Partition ###  Type              Size    Offset
  -------------  ----------------  -------  -------
  Partition 1    Primary            31 GB  1024 KB



Volume 15    K  HASLEOBS    FAT32  Removable    31 GB  Healthy

Hi everyone,
I recently started using WinToUSB to create a portable Windows setup for gaming and testing software on different PCs. One thing I noticed is that PS2 emulators like PCSX2 sometimes behave differently when running from a Windows USB environment compared to a normal installation.
On one system the emulator works perfectly, but on another I get slowdowns and BIOS detection issues. I wanted to ask if anyone here has experience optimizing portable Windows setups specifically for older game emulators.
I have been testing different BIOS files and settings from this resource ps2biosonline.

So far it helped me understand compatibility better, but I still want to improve stability and loading speed when booting Windows from USB.
Does anyone recommend specific WinToUSB settings, drive formats, or performance tweaks for gaming/emulation use?
Would really appreciate suggestions from experienced users here. Thanks!

I had a backup job running for over a year that consistently took 3 hours for the full, and 3 hours for the incremental.

I had to delete and recreate the job (I took screenshots of all settings) and made the job the same. 

Now the full took 1 hour, and incremental takes 5 min. 

Why would there be such a major difference all of a sudden??

System:

• Gigabyte B650M GAMING X AX
  
• Ryzen 7 7700X
  
• Samsung 990 PRO 1TB
  
• Windows 11 25H2
  
• Secure Boot ON
  
• TPM ON
  
• Hasleo Backup Suite (full system restore)
  

• BIOS still detected the NVMe SSD and rescue USB correctly.
  
• Selecting either Windows Boot Manager or the USB device returned directly back to BIOS with no error message.
  
• Rescue USB also could not boot.
  
• Windows only booted again after:
  
  1. BIOS factory reset
     
  2. disabling Secure Boot
     

• System now fully stable
  
• SFC/DISM clean
  
• EFI OK
  
• WinRE OK
  
• Secure Boot can now be enabled again successfully
  

I have an external WTG drive that is USB connected and would like to make a System Backup.

System Backup states that it is for backing up the currently running Windows system. If a Disk/Partition backup is made of all three partitions will it be possible to restore the image allowing the drive to be booted?

The obvious alternative is to install HBS in the WTG when it is running and do a System Backup, but I would prefer the WTB to have no network connection/exposure.

Hello, I've just done my first proper backup to a USB WD Elements drive with Hasleo but after a few minutes it stops on error. I've never had issues backing up my drives the USB WD Elements with Macrium Reflect. Any ideas please?