Backup WinToGo Drive

[Bespoken]

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.

[al3x]

Disk/partition backup should work, yes. I use normal disk backups (instead of system backups) for my PC since over a year and also restored a couple of times already.

Disk backups are very similar to system backups, with the difference being that you need to make sure you select all relevant partitions yourself.
If you just select the complete USB disk with all partitions, you should be good to go.

A quick note about licensing: To perform a restore to a USB drive, you need at least the Home edition. See this comparision chart: https://www.easyuefi.com/backup-software...rison.html

[admin]

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.

You should install Hasleo Backup Suite when running WTG and perform a system backup to ensure that Windows can start normally after restoration.

[al3x]

What does a system backup do that a disk backup does not? I was under the impression that disk backups are full clones of the drive and will restore just like system backups do. Couldn’t find more information on this unfortunately.

[admin]

What does a system backup do that a disk backup does not? I was under the impression that disk backups are full clones of the drive and will restore just like system backups do. Couldn’t find more information on this unfortunately.

Hello al3x,

That's a very good question. Let me clarify the core differences between a system backup and a disk backup.

1. Different backup scopes

• System backup: Only backs up partitions related to the currently running operating system (e.g., system partition, boot partition, recovery partition).
  
• Disk backup: Backs up all partitions on the selected disk, regardless of whether they are related to the current system.
  

2. Key difference: Partition type identifiers and boot repair capability

• System backup writes the type identifier of each partition (e.g., system, boot, recovery) into the image. During restoration, the program uses these identifiers to locate the corresponding partitions and automatically modifies the BCD file and registry entries. This ensures that the Windows boot loader can correctly find the partition containing the system files. This step is critical when partition locations, sizes, or identifiers have changed, especially when restoring to a different disk.
  
• If all partitions of the current system reside on the same disk, performing a disk backup of that disk will also write the partition type identifiers into the image. As a result, after restoration, such a disk backup can usually guarantee that Windows boots properly, similar to a system backup.
  
• If you perform a disk backup on a disk that does not contain the currently running operating system, and that disk has another Windows installation on it, the backup tool will find it very difficult (or even impossible) to obtain the partition type identifiers of that offline system. During restoration, the program cannot correctly modify the BCD and registry files, so there is no guarantee that the restored disk will be bootable.
  

I hope this explanation can help you!

Best regards,

[al3x]

Hi,

thanks for explaining the key differences, I think that helps a lot already.

I wasn't aware that HBS actually updates the BCD in some cases. So it does this only during restore of system backups, correct? So using disk backups keeps the data completely untouched which can cause problems in case partition layouts / identifiers etc. changed.

The typical commands that you can find online to restore boot capability usually go something like this:

• mount EFI partition with diskpart, sel disk x, sel vol x, assign letter=k (or just mountvol k: /s)
  
• restore entry: bcdboot c:\Windows /l {language} /s k: /f UEFI
  
• rebuild BCD: bootrec /rebuildbcd
  

In my tests that was all it took to get the system back on its feet, but maybe it's more complicated in some scenarios. May I ask if HBS uses additional other commands to restore boot capabilities?

I never thought about using system backups so far as I usually have additional partitions (or even other disks) that are included in my backups. Would it maybe make sense to include a fix button in the Tools section (just like the Rebuild MBR button) to try to repair a non-bootable system?

Anyway, thanks again for your explanation!

[Bespoken]

Lots to learn and take away for the replies. Thanks everyone!

[garioch7]

@Bespoken,

I know that I speak for the Forum Team when I say that we always welcome constructive feedback and questions.

We are pleased that you have chosen to use the Hasleo Backup Suite as your backup/imaging program.  You only joined us a month ago, and already you have made significant contributions here.  Thank you.

Have a great day.

Regards,
Phil

[admin]

Hi,

thanks for explaining the key differences, I think that helps a lot already.

I wasn't aware that HBS actually updates the BCD in some cases. So it does this only during restore of system backups, correct? So using disk backups keeps the data completely untouched which can cause problems in case partition layouts / identifiers etc. changed.

The typical commands that you can find online to restore boot capability usually go something like this:

• mount EFI partition with diskpart, sel disk x, sel vol x, assign letter=k (or just mountvol k: /s)
  
• restore entry: bcdboot c:\Windows /l {language} /s k: /f UEFI
  
• rebuild BCD: bootrec /rebuildbcd
  

In my tests that was all it took to get the system back on its feet, but maybe it's more complicated in some scenarios. May I ask if HBS uses additional other commands to restore boot capabilities?

I never thought about using system backups so far as I usually have additional partitions (or even other disks) that are included in my backups. Would it maybe make sense to include a fix button in the Tools section (just like the Rebuild MBR button) to try to repair a non-bootable system?

Anyway, thanks again for your explanation!

In cases where partition geometry changes or disk/partition identifiers change, the BCD file and registry file usually need to be modified to ensure Windows can boot properly. The bcdboot command essentially recreates the boot files, including the BCD. Hasleo Backup Suite does not call third‑party commands to modify the BCD, it directly modifies the BCD file and registry file to achieve a similar result.

The idea of adding a feature to repair a non‑bootable system is very constructive, and we will consider it. The only caveat is that such a feature can only fix boot problems caused by incorrect BCD or registry settings, it cannot resolve all possible system startup issues.

[Gork]

https://www.easyuefi.com/forums/thread-1...l#pid11053