Solved Hasleo Backup Suite: Handling dynamic external drive letters for scheduled backups on Windows 11

Environment & Context
• OS: Windows 11
• Software: Hasleo Backup Suite (evaluating alongside Macrium 8)

I am considering switching from Macrium 8 because a Microsoft change stopped this version from being able to mount backups to restore single files from image backups. I am currently running Hasleo in parallel to see if it meets my backup requirements.

Problem
I connect a second external backup disk on a monthly basis. However, Windows 11 assigns drive letters dynamically whenever external storage is plugged in. Because the drive letter changes each time, I cannot reliably set a backup schedule that depends on a static drive path.

What I've Checked
• In Macrium, there is a built-in method to automatically handle dynamic drive letters and locate the backup destination.
• I searched through the Hasleo help guides, but I cannot find any mention of a feature to resolve changing drive letters.

Question
Does Hasleo Backup Suite have a built-in feature or a recommended workaround to handle changing drive letters for scheduled external backups?

I have six external USB drives that I use for Hasleo image backups. When connected individually they are always D: drives. I use MiniTool partition Wizard to change the letter to D: on all of the drives. So when connected they remain as D: I used MTPW to put the letter on the Q drive also. It works for me but your milage may vary.

One thing I forgot to mention I connect these externals before booting to Windows.

Give each external drive a permanent drive letter in Windows Disk Management. Windows normally remembers the assignment for each physical volume, so:

• Drive A → E:
• Drive B → F:
• Drive C → G:

kelper said:

Give each external drive a permanent drive letter in Windows Disk Management.

Click to expand...

I agree and that's what I do. The letters assigned by me then stay the same.

Hi there. Thank you all for your solution. I have now renamed the drive letter, and it appears to keep it when logged off and then back on. Better solution than using volume data to identify it, which I had been doing with Macrium.