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? 

I'm new to Hasleo Backup Suite - but just started using V5.8.2.0 and would like to know where to find the log files please. If I've selected Power Plan = Shutdown, how do I know that the backup completed successfully?

Thanks!

Hasleo Backup Suite V5.8.2.1 Released!

What's new in this version:
1. Fixed a vulnerability in the disk backup image mounting driver
2. Fixed an issue where WinPE created under Windows ARM64 26H1 did not work properly
3. Fixed a backup failure caused by NTFS file record corruption
4. Added a global setting to create VSS snapshots without using VSS writers
5. Fixed other minor bugs

Here are the download links:
X86/X64
ARM64

Hello everyone,

Recently, a vulnerability was discovered in the driver used for mounting system/disk/partition backup images. Specifically, sending a particular driver control command can trigger a BSOD (Blue Screen of Death). We have created a temporary patched version that replaces the driver file.

Since this driver involves low-level operating system operations, the fix needs to be validated in various environments. We sincerely ask for your help in testing, with a focus on whether the "mount image" functionality works correctly.

Test Items:

1. Download and install the patched version. During installation, check whether Windows gives any driver signature warning.
   
2. Check whether you can successfully mount an existing backup image (system/disk/partition backup).
   
3. After mounting, is reading and browsing files within the image normal?
   
4. Is unmounting the image normal?
   
5. Do you encounter any BSOD, freeze, or other anomalies?
   

I haven't seen this error for a few years, but it seems to be back again. Any one else? Is this from a recent Windows Update?

The task failed with 0x28EF0036000000E9 (Specified partition not found)