Greetings, Team!  Quick question about the thread SUBJECT item... when using the "USB drive plugged in" event AND you have the "Run only once a day" option set, does that mean the NEXT allowed image must be a minimum of 24-hours from the last allowed image, or are we talking CALENDAR DAY images... i.e., only one image in a calendar day (but any time distance apart... as in 11:59pm and 01:02am)?

I'm new to the Hasleo Backup. Creating and booting from the Emergency Disk worked like a charm.

Creating a Partition Backup from my Win10 bootdisk works for all partitions (e.g. RECOVERY) but not from the C:\ drive itself. It leads into an Error 0x0073007000000005 after a few seconds.

I did a chkdsk on the C: drive as well but still the same issue.

What kind of error is that and how to solve?

Greetings, team!  While testing your scheduling features, I chose DAILY and set the interval to start at 9am and end at 8pm... I expected 12 images to be generated on the hour but only got 11.  Turns out the finish time of the interval needed to be set to at least 8:01pm for the 12th image to be generated at 8pm... I don't think that should be the case.  If the ending time is at least the same time or earlier then the scheduled task, it should run successfully (just a l'il math anomaly )

The SUBJECT term is sometimes slightly misunderstood by users of software that use such a mode.  Sometimes that term refers to bringing up a WinPE-based separate Windows environment (like your Emergency Disk) to run the user's application, and other times the application is actually being run before bringing up the full LIVE Windows System in use (kinda like a partial reBOOT).

In the case of Backup Suite's automatic LIVE restoration of a locked partition (like the LIVE Windows environment), which of the above modes is being used for this function?  Thanks in advance!

Being a newbie here I figure this would be a great place for this discussion.

Item #1: A modern UEFI configuration these days includes at least one large disk which many times includes the FOUR necessary partitions for successful UEFI BOOTing (EFI, MSR, Recovery & OS) plus a separate DATA partition to be used as the user requires.  Your "System Backup" mode correctly includes those very same partitions and does not include the extra DATA partition.  This presents a significant problem during the restore operation.  Since the "System Backup" is not necessarily a Full disk backup, the System restore should not be one as well.  The System Restore should allow a user to select the partitions to restore (multiple, if necessary) without changing the geometry of the disk as far as resident DATA partitions are concerned.  Currently a System disk restore restores all the necessary BOOT partitions but blows away any partition on that disk that isn't included in the image... quite a big surprise when I first tested this feature.  I don't see a significant reason for having this type of restore do anything other that a non-destructive partition restoration... just like it does with the Partition restore mode.  When presented for restoration during a System disk recovery, all the included partitions should be selected for restoration, allowing the user to unSELECT anything he doesn't want to restore (like an OS-only restore).

Item #2: the Partition restore mode could do this as well but currently allows only a single partition to be restored non-destructively.  This makes a System configuration restoration require four separate partition restores to insure the non-backed up DATA partition remains untouched... a significant process and possibly very error prone.

Some initial observations... more to come.  Thanx for your consideration!

Good morning,
i have an issue; i would like to clone my disk on an empty SSD disk that i have connected via USB but if i do that it proposes me to install WINtoUSB, but this isn’t the application that i need, i only want to clone my main HD.

good morning
I am a blind user and was thinking of purchasing Hasleo WinToUSB for my work
However, I can't use Hasleo WinToUSB with 'nvda, jaws, narrator' screen readers.
After a programmatic analysis of the problem, I found that WinToUSB
was designed by qt5 Widget
This pattern is not compatible at all and cannot be used with screen readers
So, could you please recreate the GUI of the program with accessibility in mind
Here are some guidelines and you can find more
https://doc.qt.io/qt-5/accessible.html

i have an isssue with my backup... i need to shutdown automatically my pc after my scheduled backup is taken.
i've tried to add a command (i've made a script "shutdown.bat") into advanced backup option. the script works well, but it doesn't work automatically, gives me an error after the backup

Hi There,
As first I like to thank WinToUsb creators for the wonderful software.

I like to ask a question:
I have made a bootable WinToUsb of Windows 10 to an ssd harddisk through an USB connector. It works as expected and I love it.
I like to place this ssd into a pc and connect it with sata cable, just like an ordinary harddisk. 
Will this installation work through sata connection just like it do through USB connection?
Or will it not boot at all?
If this works it will save me time reinstalling a pc...
Thank you in advance for your answer(s),

FreeDuck

Hi guys,

hope someone can help me with this.
i am trying to clone my windows to go to a SD card.
I have an 1 TB SSD and now i bought an 512 GB SD card.
i am trying to follow the steps but i keep getting the error "Disk or partition space is insufficient (0x005700c201960000)".

First i thougt it made sence because my SSD was much bigger so i made 2 partions on my SSD where one is 130 GB with windows installation and the rest is for the second partition.

But i keep getting the same error.
How can clone my windows partition to my SD card?