Using tib files

ADKM, welcome to these User Forums.

Some comments in response to yours above:

Initialising a drive taking a long time: 

Sorry but what exactly do you mean here?  There is an option in the application to 'Add disk' which will prepare a new drive for use by ATI but I can only think of a couple of occasions when I have actually used it in all the years of using ATI.  I am sure that it worked very quickly on those occasions, but it is just as quick to initialise a drive in Windows when needed.

Has anyone had any success restoring a drive from a .tib file. Are they actually real images intended to restore a drive?

Most definitely - this is a core function of ATI and I wouldn't be here as a MVP or User if this didn't work when I have needed to recover a drive or partition or files etc over the years.

ATI creates two different types of backup image files, both shown as .tib files.  Disk & partitions backup image capture an exact snapshot of the whole drive & partitions as it existed at that precise moment in time.  These image files can be mounted to a Windows drive letter if needed and this type of file is required in order to recover a Windows OS drive complete with all applications and user data intact.

The second backup image type is for Files & Folders, and again this captures an exact snapshot of the selected Files & Folders at that moment in time.  These image files do not contain any partition structure, so cannot be mounted to a drive letter.

Both image file types can be opened using Windows Explorer on any computer where ATI has been installed - this provides the necessary Windows Shell integration to all you to explore the .tib file contents and use Copy & Paste commands if needed.  All .tib files are Read-Only containers for the data, so cannot be changed once created.

I had validated the tib file successfully and the operation reports success, but when trying to boot all you get is "No operating system was found".

This is normally caused by not restoring the backup image file correctly / not matching the correct BIOS mode used by your Windows OS when booting.

If you have an UEFI boot system (you can confirm this by running the msinfo32 command in Windows and checking the BIOS mode information shown in the report produced), then any recovery done using the Acronis USB Rescue media must be done with that USB media booted in the same UEFI mode.

If you boot the USB media in Legacy mode on a UEFI system, the restored disk will be created in Legacy/MBR format and your Windows OS will not boot.

When you boot the USB media in UEFI mode to perform a recovery / restore, then ATI will automatically create a GPT partitioned drive to restore the OS data to.

Hi Steve,

I really feel ATI software, simply does not work well and gives false hope to people who may be relying on a backup. In some ways we'd be better off without it as they may then find/use something that *does* work.

However, that  *some* people have success (under the exact right conditions?) suggests its just not very robust and it would pay to be very wary, first establishing the exact conditions for success. Certainly you cannot just make a tib file and trust it to restore a drive. I say this after weeks of trying in conjunction with the Chat Help. I must have run the recovery program 20 or more times.

Perhaps its worth seeing why my tib files are no good?   I've still got all the .tib files (created with Aronis 2018). These validate ok.  A previous failure with recovery was explained to me as an error with the files not validating. Although why was never established.

I can't try mounting these now as I've since uninstalled the acronis program. But I have recovery media on a flash drive and boot with this, with a new HDD (sata) and the .tib file on a USB Drive.  I used Add Disk as the drive was new and I presumed it needed initialising. I selected MBR to match the orig. disk, then GPT, when that didn't work.  With the GPT partition no progress bar showed and I gave up trying after 90 mins.  (I also tried formatting the drive on another computer).

The recovery proceeds normally and reports success.  But booting into windows 10 with the recovered drive just shows "No operating system found'.

As you say, it may be something to do with BIOS mode or the partition type but there was no indication of that or warning. Looking at the drive in a different computer's Disk Management showed 3 partitions, one unallocated. That made sense, as new HDD is 1TB and original source drive was smaller. The partition with the drive letter did not have a Windows Folder.  The other allocated partition I couldn't see (explore). Screen shots and log/reports were sent to acronis who suggested to use the 2019 version and gave me a link.  Results were the same as 2018 version.

I've since bought a new Win 10 and up and running no problem having resigned to losing the original (and all my work/programs).

I wasn't aware of the UEFI factor and maybe this is part of the problem?  I used a flash drive as there's no optical, not expecting there to be any difference.  Wouldn't the Chat people know about this? We even went through the whole process taking photos of each screen and uploading them, it took hours...

>If you boot the USB media in Legacy mode on a UEFI system, the restored disk will be created in Legacy/MBR format >and your Windows OS will not boot.

>When you boot the USB media in UEFI mode to perform a recovery / restore, then ATI will automatically create a GPT >partitioned drive to restore the OS data to.

Afaik Both legacy and UEFI modes were attempted with both MBR and GBT partitions.

If you have some different steps I should take for success, I can swap to another HDD and try again.

Regards, ADKM

ADKM said: " However, that  *some* people have success (under the exact right conditions?) suggests its just not very robust and it would pay to be very wary, first establishing the exact conditions for success. "

I'm one of those that has had success and, I can assure you, there were no special "just right" conditions.  During the past 2 months I was testing several different pieces of software and several times restored from ATI backups to go back to a known stable configuration.  I restored my test PC 3 (or maybe 4) times with no trouble.  And several months ago I restored my "production" PC after some software got corrupted.  I've also pulled individual files from backups - both disk and partition backups and files and folders backups - many times.

" Certainly you cannot just make a tib file and trust it to restore a drive. "

Certainly I can - and have - done just that. 

" I wasn't aware of the UEFI factor and maybe this is part of the problem?  I used a flash drive as there's no optical, not expecting there to be any difference. 

I don't remember the Acronis Linux recovery medium, but all the tools that build Acronis WinPE recovery media (that I've seen) allow you to boot either UEFI or CSM ("legacy") mode.   On my computers the CSM version does not mention "CSM" or "legacy" in the boot menu but the UEFI version clearly says "UEFI" so it's easy to see which is which.  (I suspect this display may be BIOS-dependent.)

" Wouldn't the Chat people know about this? "

Umm, some members of the Acronis support team are very good.  Others tend to follow a script - maybe they know about the flavors of the boot environment; maybe not.  This is impolitic for me to say, but I suggest taking the explanations and advice of Steve and the other MVPs over that of the support people on chat unless it is clear the support person really knows what he or she is talking about.  (I've probably just lost all hope of getting help from Acronis support. :-) )

Hi Patrick, I'm using an Asus PRIME B250M-K motherboard.  The BIOS offers Auto, Legacy or UEFI. I've tried all 3.

The flash drive has an iso 2019 image (as per acronis chat instruction) burned with ISOtoUSB.

The .tib file was created from an SSD with a MBR partition. That is I *think* it was MBR and I've never knowingly used GPT. I don't have the drive anymore (its shot); only the .tib from it)

> all the tools that build Acronis WinPE recovery media (that I've seen) allow you to boot either UEFI or CSM ("legacy") mode. 

From Steve > If you boot the USB media in Legacy mode on a UEFI system, the restored disk will be created in Legacy/MBR format and your Windows OS will not boot.

>If you have an UEFI boot system (you can confirm this by running the msinfo32 command in Windows and checking the BIOS mode

The above isn't all that clear to me. Is the UEFI boot system only used by flash drives?

> When you boot the USB media in UEFI mode to perform a recovery / restore, then ATI will automatically create a GPT partitioned drive to restore the OS data to.

Although I'm sure I have already done this I will try again and report back.

Maybe getting advice to my steps through the procedure would be worthwhile?

I have booted in UEFI mode.

I'm offered 4 things to recover

NTFS (Unlabeled)(Y:) Pri,Act 100 MB 63.32 NTFS
NTFS (Unlabeled)(Z:) Pri 111.3GB  86.91 GB NTFS
MBR and Track 0
Recovery Partition Pri 449 MB 354MB NTFS

I set -

New Location for Y:  = 100MB partition
New Location for Z: = C:
New Location for Partition 2-3 = Recovery Partition

Next it wants a MBR of Disk2. The only options are Flash drive Disk2 (the Boot one) or USB Disk3 (drive with tib file)

I choose Disk 2 and proceed.  Operation reports success.

This time there was a different outcome. Instead of "No Operating System Found", it boots straight into the BIOS. I have 2 choices in boot menu (even though only one drive is connected) and tried both.

The flash drive has an iso 2019 image (as per acronis chat instruction) burned with ISOtoUSB.

You should not need to use ISOtoUSB to create the Acronis Rescue Media - the program can write directly to your USB stick without going through this step of creating an ISO file first!

The .tib file was created from an SSD with a MBR partition. That is I *think* it was MBR and I've never knowingly used GPT. I don't have the drive anymore (its shot); only the .tib from it)

If the above is correct (about being a MBR partition backup image) then this was a Legacy boot system and the Rescue Media needs to be booted in the same mode (not using UEFI).

I've since bought a new Win 10 and up and running no problem having resigned to losing the original (and all my work/programs).

As your new Win 10 OS is working fine, then I would strongly recommend leaving this alone and if your are willing to attempt any further recovery of the old SSD backup, that this should be done to a spare drive just for that purpose.  As your computer is UEFI capable, I would expect that your new Win 10 OS was installed using that mode but running msinfo32 in Windows would confirm this by what the BIOS mode shows in the output report.

I have booted in UEFI mode.

I'm offered 4 things to recover

NTFS (Unlabeled)(Y:) Pri,Act 100 MB 63.32 NTFS
NTFS (Unlabeled)(Z:) Pri 111.3GB  86.91 GB NTFS
MBR and Track 0
Recovery Partition Pri 449 MB 354MB NTFS

I set -

New Location for Y:  = 100MB partition
New Location for Z: = C:
New Location for Partition 2-3 = Recovery Partition

Next it wants a MBR of Disk2. The only options are Flash drive Disk2 (the Boot one) or USB Disk3 (drive with tib file)

I choose Disk 2 and proceed.  Operation reports success.

Again, if the original SSD backup was for a MBR system, booting the Rescue Media in UEFI mode will result in a GPT partition drive, which could work in the right circumstances, but doubtful when doing manual partition placement.

The recommended process for recovering your MBR backup is as follows:

Boot the Rescue Media in Legacy/CSM mode.

Recover at a Disk level by just selecting the top-most entry for the SSD - this will automatically select all the partitions for that disk and will not require you to select or resize those partitions and their placement.

Please see forum topic: [How to] recover an entire disk backup - which was written to show this type of backup with screen shots of the steps needed.

One further point:  after recovering a Legacy/MBR system - the SSD drive needs to be selected as the Boot device in the BIOS settings.  If recovering a UEFI/GPT system, then the Windows Boot Manager needs to be selected as the Boot device (not the drive!).

Steve, thank you for all the info. I used IsoToUSB on the advice of Acronis support. I didn't have ATI available at that time to recover to a new HDD.  It's from/to the same motherboard (which is UEFI capable) using a new HDD.

I'd not heard of UEFI until setting the flash drive
as boot (and seeing UEFI as part of it's name). I assumed it was something to enable booting from a Flash Drive, now I understand it's the modern equivalent of the whole BIOS program.

I'll keep my new Win10 but if the former will restore I'd rather use that, and have another HDD for recovery attempts.

I will follow all your instructions and try again now. Certainly not selecting the partitions individually may help as it might be assigning the drive letter to the wrong partition.  Looking at the recovered drive (in another computer) shows the 100MB partition has the drive letter, and Explorer doesn't show the larger partition. What you see is:

Boot
Recovery
System Volume Information
bootmgr
BO0TNXT
BOOTSECTBAK

I had expected to see files common to C:\ and a Windows Folder.  Would you agree ?

Also, can you tell from the tib file if it's UEFI/GPT system or not? Could it be UEFI/MBR or Legacy/GPT ?

Looking at the recovered drive (in another computer) shows the 100MB partition has the drive letter, and Explorer doesn't show the larger partition. What you see is:

Boot
Recovery
System Volume Information
bootmgr
BO0TNXT
BOOTSECTBAK

I had expected to see files common to C:\ and a Windows Folder.  Would you agree ?

The contents shown above for the 100MB partition look like they are from the System Reserved partition used by Legacy systems, where the Boot folder holds the Windows Boot Configuration Data store (BCD).  So, no, would not expect to see any C:\ files or folders here, plus too small to hold such.

Also, can you tell from the tib file if it's UEFI/GPT system or not? Could it be UEFI/MBR or Legacy/GPT ?

I would expect to see an EFI partition in the tib contents for an UEFI system and indications of this in the contents of that partition.

See webpage: Frequently asked questions about the GUID Partitioning Table disk architecture - for a lengthy set of information using questions / answers.

It cannot be UEFI boot using MBR for the OS drive, this has to be UEFI with GPT, but can have other drives using MBR on the same system.

Steve, I find the motherboard will not let me select UEFI or legacy modes without removing either Flash Drive or the USB drive (with my image file) from it's list of available drives. 

I will try with another computer  (with a standard BIOS).

Another informational webpage: MSR and EFI Partitions Are Only Supported on GPT Disks

ADKM wrote:

Also, can you tell from the tib file if it's UEFI/GPT system or not? Could it be UEFI/MBR or Legacy/GPT ?

There is some very confusing terminology that, I think, has led you (and me, and many others) astray.  As near as I can tell, UEFI is just a user interface of firmware on your motherboard and a set of standardized functions implemented by that firmware. 

The format of your bootable partitions on your device and (I think) the control blocks pointing to those partitions is either MBR or GPT.  That is, the partition contains either a Master Boot Record or a GUID Partition Table to point to the bootstrap code (among other things).

UEFI firmware natively boots GPTpartitions but can boot MBR (legacy) partitions through the use a Compatibility Support Modules (CSM).   So your (UEFI) motherboard can natively boot a GPT device and can boot a legacy MBR device through using a CSM.

So I think the question you wanted to ask is whether your can tell if a .tib file is a backup of a GTP device or an MBR (legacy) device.  I don't think UEFI figures into that question at all.

Too bad I don't know the answer to that question.  :-(

> Recover at a Disk level by just selecting the top-most entry for the SSD - this will automatically select all the partitions for that disk and will not require you to select or resize those partitions and their placement.

I've now booted from CD ROM on a different system and at the Archive Selection stage. There are 2 entries, top one has a blue icon and the one below looks like its one level down. Both same / similar names. After  "Recover Whole Disk" and in the "What To Recover" screen I still have to select 4 items, then led to a  new location prompt.. There is no automatic selection as Steve indicated.

NTFS (Unlabeled)(Y:) Pri,Act 100 MB 63.32 NTFS
NTFS (Unlabeled)(Z:) Pri 111.3GB  86.91 GB NTFS
MBR and Track 0
Recovery Partition Pri 449 MB 354MB NTFS

Where should the New Location for each be ?

The contents shown above for the 100MB partition look like they are from the System Reserved partition used by Legacy systems, where the Boot folder holds the Windows Boot Configuration Data store (BCD).  So, no, would not expect to see any C:\ files or folders here, plus too small to hold such.

Would you expect a drive letter in this System Reserved Partition and NOT in the other one ?  This is a new thing, I would expect the reverse.

Patrick, using this 2nd computer UEFI / CSM is not mentioned but I can't assign the various partitions to targets with any confidence. The summary does not mention  a C: drive an it isn't clear what all the others are, ("Partition 2-3" for example ???).

Anyway it's proceeding and will, no doubt, report Success, but I will be amazed if it works.

No, it didn't work. Seems identical results to the last try.

I'll try uploading an image. If it succeeds Disk6 is the Acronis-recovered one.

Disk 4 is from another similar Win 10 comp. It's BIOS mode is Legacy.

Notice the 100 MB partition does not show a Drive letter and the 237GB one does.
This is what I'd expect on Disk6 but it isn't so.Does anyone else agree or am I wrong ?  If this is correct perhaps the next step would be to see why ATI does not assign the drive letter correctly.

I have proved (via Disk Management) that Disk4 is MBR and Disk6 is GPT.

I haven't any other OS on GPT disk to compare.  Can I force Acronis to use MBR and see results from that? Or is that determined by the  tib file and you can't change it?

This sidetracks slightly but demonstrates how difficult it is to do anything with this Acronis software..

 I want to change my GPT partitioned drive to MBR. I boot with the Acronis Recovery stuff on a flash drive and from "Add New Disk" answer all the prompts in the logical way right through to "Proceed".

At that point I get "Clearing Disk (reboot required)"
Hard Disk: 1

(1 of 1)...

A progress bar shows and one option - "Cancel".  I've waited up to 90 mins and nothing more happens. Clicking 'Cancel' does nothing. If you close, another dialog appears says "Preparing" and hangs there for ever. Power down is only way out.

One more Try. I have a newly formatted drive (MBR) and attempting recovery on a Win 10 BIOS
machine.  Hopefully this removes any GPT/UEFI issues.

I've got screenshots of each stage and my inputs in the attached image

I can't get past "Setting of Partition Z' stage. It only offers Disk 2
which is the USB drive called "Storage" with the .tib file on it.  
Wouldn't the new partition location be on the drive I am restoring to ?

Am I doing anything obviously wrong?
Thanks.

I have proved (via Disk Management) that Disk4 is MBR and Disk6 is GPT.

Sorry but Disk Management does not show whether a disk is MBR or GPT - both display the same as being Basic disks.  You would need to use a different partition management tool to prove this, such as the one shown in my screen shot below that does show GPT & MBR drives.

In the description of the partitions shown above, one says GPT (EFI System partition) as required for an UEFI system to boot correctly.

I can't get past "Setting of Partition Z' stage. It only offers Disk 2
which is the USB drive called "Storage" with the .tib file on it.  
Wouldn't the new partition location be on the drive I am restoring to ?

Am I doing anything obviously wrong?

Sorry, but if you are being asked to configure the settings for individual partitions, then this suggests that you did not just click/select the very top Disk 2 selection box shown in your screen image.  Selecting the top Disk entry will automatically select all partitions but does not require those partitions to be configured manually.

Disk 1 is the correct target location for your Recovery because as shown in your screen shot this is an empty drive regardless of the drive letter shown for it.

298 GB Free Space from 298.1 GB Capacity for Disk 1.

The reason why Disk 1 is no longer available for your partitions recovery is simply because you have not resized the first partition Y: correctly as 100 MB, instead you have given it 298.1 GB leaving no space for any other partitions!

What you should have been looking at for this Disk recovery is as shown in the image below:

Note that there is no left menu options for setting the Destination Settings of Partition Y, Z etc - this is because ATI will do this automatically and correctly for you.

Hello Steve,

>but if you are being asked to configure the settings for individual partitions, then this suggests that you did not just click/select the very top Disk 2 selection box shown in your screen image.  Selecting the top Disk entry will automatically select all partitions but does not require those partitions to be configured manually.

Now I get that! You had told me before but I misunderstood, Sorry. I thought you meant the top item here

I found both seemed to do the same thing.

Selecting each partition individually was the instruction given by the guys at Acronis chat, so that reinforced my mistake.

> Sorry but Disk Management does not show whether a disk is MBR or GPT - both display the same as being Basic disks

You may be right, although I was getting MBR/GPT settings from right clicking here in Disk Management

then Properties-Volume-Partition Style.

Now better informed I'll have another attempt. I am a bit stressed by all this and not sure which BIOS setting to use. Or which computer, the target one with UEFI (flash drive recovery boot), or my wife's older one with a standard BIOS and CDROM recovery. The UEFI machine can lose either the backup or flash drive from its list of drives, so you're limited in trying some configurations.

I have booted into Win 10 rescue and used DiskPart to clean the destination drive, then formatted it in an XP computer to MBR. So that should be a given.

btw thanks for all your help and advice.

Steve, looks like the images I pasted with last msg have gone west, sorry.

I'm unable to try another recovery right now as the HDD has started to give errors. I'll get another but it won't be till saturday.

Steve was sort of right, selecting the whole disk instead of individual partitions DID restore a GPT bootable disk.  
But I need MBR. Possibly because of UEFI  if you boot with a flash drive it will recover a GPT disk (whether CSM is disabled or not).  I find GPT assigns drive letter "D" to a partition which conflicts with an existing drive D: (Also file sharing with an XP machine is wanted and I believe XP won’t read GPT disks)

Attempts to make an MBR partition have been interesting.

The first problem is the motherboard (Asus B250M-K) , I could not get it to boot from an optical drive, so I switched to a computer that would.   But that had problems, ATI would freeze partway through partition recovery, then started reporting "A hypertransport sync flood error occurred on last boot". Some incompatibility with that machine, I guess

I did have another non-UEFI machine and using that, the operation reported success.

But it was far from successful.   Looking at the disk shows it is MBR but has the same issues as when selecting partitions individually.  The partition with the drive letter is wrong, showing the same 6 items as mentioned earlier. And of course, no operating system is found.

A little bit more, if anyone is interested.

EFI is the problem. Acronis will restore/create an extra 100mb partition with drive letter D: containing files called Boot, Recovery and Folders called bootmgr,BOOKNXT and BOOTSECT.BAK.

This is in addition to a 100MB EFI partition and 2 others.

If you have an existing D: you might want to reconnect, you're in trouble.

I found the only fix is to use a different (NON-EFI) computer to recover from tib (without selecting individual partitions as Steve said) and move the HDD back to the EFI comp afterwards.

A bit weird I agree, but it worked here. Possibly it's just my motherboard, or an incorrect setting in EFI. I did reset defaults  though.

Thanks for sharing your latest findings.  It would suggest that anyone with an EFI capable system would be best advised to migrate from a Legacy/MBR configuration to using EFI/GPT or else get ready to jump through hoops in a recovery situation!

I have seen a number of posts telling of the benefits of going to EFI in terms of performance, security etc, and there are MS tools available to facilitate such migration without data loss.

My only issue personally is that I have not yet bought an EFI system and while my older hardware is still working OK for what I use / need it for, am not in a hurry to do so!  (I have access to EFI systems when needed but haven't really seen very much difference other than in the BIOS and disk partition formatting - if anything EFI tends to complicate things, i.e. getting an ACER laptop to boot the Acronis WinPE Rescue media when Secure Boot was enabled!).

It was quite a relief to actually see a recover work as there are four computers "backed up" with tib files should they ever be needed.

There would have been 20-30 attempts and 12 or more hours talking to ATI chat support (over 2-3 weeks) before stumbling on a solution.  It'd be interesting to hear how others manage in similar circumstances.  The tib file was created on MBR system but restored to GPT because I could only get the system to boot with a flash drive. Maybe that's a factor? 

With respect, the chat people seem to have stock answers and don't inspire much confidence. Certainly the reps instructions were to select all partitions  (and confirmed after seeing a screen shot) whereas now they tell me "Recovery can be indeed done checking the disk (this in turn checks/selects all partitions) of the disk. Selecting individual partitions is pretty much the same (the only time we suggest selecting partitions and not disk if a user wants to recover only a specific partition)."  I'd argue that "pretty much the same" in this case was anything but.

I wasn't that "EFI" system-aware, only that it was different and complicated compared to usual BIOS.  The Asus user guide has very little information.

The subsequent "extra" partition created and assigned a drive letter by ATI needs explaining. And when initialising a disk to GPT or MBR and told "Reboot Required" needs fixing,  so it does something rather than just hang.

Thank you Steve (and Patrick), your advice was the path to success!

ADKM wrote:

The tib file was created on MBR system but restored to GPT because I could only get the system to boot with a flash drive.

You referred to that before, but I don't understand.  All my recovery devices - both HHDs and USB flash memory devices - are MBR devices.  I've been using Acronis recovery media on MBR flash memory for years and have had no trouble.

Then it may be peculiar to this motherboard or EFI configuration.  Booting into ATI (2019 version)  with a flash drive, (even after Adding the target drive as MBR) made no difference. The result was GPT formatted disk.

I assumed this was because of the flash drive, had it been possible to boot from CD/DVD I would have tried that to compare.

ADKM wrote:

Then it may be peculiar to this motherboard or EFI configuration.  Booting into ATI (2019 version)  with a flash drive, (even after Adding the target drive as MBR) made no difference. The result was GPT formatted disk.

A flash USB recovery medium created by ATI (or the MVP Custom WinPE Builder) will have both
UEFI boot (clearly marker UEFI in your boot menu) and a CSM boot (which isn't labeled with anything implying CSM or legacy in my boot menus). You have to boot the non-UEFI version to get support an MBR recovery (I think).

Hi Patrick, the EFI BIOS on this board is far from simple, but I checked again.

CSM is enabled. This gives 3 options under "Boot Control"; UEFI & Legacy OPROM, Legacy OPROM Only, and UEFI Only.

If Boot Control is on Legacy OPROM Only, no OS is found on the flash drive. The other 2 give you a GPT system, which bares out what you say You have to boot the non-UEFI version to get support an MBR recovery

There's also Boot From Network Device, Boot from Storage Device, Boot from PCI-e Device. These all are "Legacy Only' and I've not ever changed them.

The flash drive was written/made by ISOToUSB, from the Acronis iso file, as linked to and advised by Mr Chat. Maybe that's part of it.  You don't want to swap motherboards, do you :)

All the Acronis Rescue Media is capable of booting in both Legacy/CSM or UEFI modes but this has to be selected for the actual device where the media will be booted from.

The BIOS settings are simply a means of enabling this selection choice at boot time.

As Patrick indicated above, for the boot media device you should see this listed twice, once with UEFI against the device name, and once without.  This is the only indication normally given.

See screen shots below that show examples of this form of boot device selection (from boot override menu panels).

See also KB 59877: Acronis True Image 2017: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media - which has further screen images of differences seen when booting.

From that link I will be using legacy mode as I've never seen anything except "Starting Acronis loader..."

My board has a "Boot Override" option but no matter what I do, it remains greyed out. If I boot into the EFI screen with just the ATI media USB drive there's 2 items to boot from.  But only one works.. see image

Your screen image shows only UEFI boot override options which looks similar to issues I had with an Acer laptop where Secure Boot had to be disabled to get any other boot options to work!