Acronis True Image 2020 Build 20770 Final

Peter, welcome to these public User Forums.

Sorry but I do not understand your post above?

When using the Acronis Rescue Media, this always should be booted using the same BIOS mode as your Windows OS uses.

See KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media

sorry for my english

I share my video.

1. Boot from my acronis boot part (before windows 10 start) 

2.boot from my usb.

https://drive.google.com/file/d/11v8j4Z-A3t_tbrnVXRBktjp--pkehzlo/view?…

https://drive.google.com/file/d/14ab_XcD8g6G2ZzghFZppydSR3K22NVv4/view?…

my ssd gpt  uefi. windows 10

Dont work on AT 2013, 2019, 2020 

If I start recovery from windows 10 then the Acronis boot partition works. 

3. "active protection disable ico" dont have on AT2020

Hey there,

About being able to disable the icon, you should/can use the feedback though help>send feedback.

About the booting, apparently you can boot and launch the Linux environment correctly, but the application becomes unresponsive when you want to browse for the backup to recover.

Since your system is not supported in either ATI 2013, 2019, 2020, I guess there is a chipset driver issue.

Did you try to produce a WinPE version of the recovery medium? Choose tools>rescue media builder>advanced?WinPE based media > Windows recovery environment

If this version doesn't work, come back to this forum for help on how to produce a more advanced version with manually selected drivers.

Can you share your set up? How is your system disk connected to the computer (connector type and interface NVMe/SATA/...)

3. "active protection disable ico" dont have on AT2020

This was raised many times during the ATI 2020 Beta testing - the new system tray icon is now purely a place to show the status of backup tasks and no longer just for AAP which has to be turned on or off via the main ATI 2020 GUI options instead.

Peter, your second video confirms that you have a UEFI boot system with a Samsung 970 EVO drive, therefore you should not be attempting to boot from the Acronis Rescue Media in Legacy mode as you will not achieve a bootable OS on recovery!

As Pat has already mentioned above, the Linux version of the Rescue Media (including the Acronis Startup Recovery Manager that gives the F11 on boot shown in your video) does not have support for these modern NVMe M.2 drives, so you really need to be creating the Windows PE / Windows RE version of the Rescue Media with the necessary device drivers for this drive.

More information on your backup drive is also needed, i.e. is this another Samsung EVO, or is it an external drive?  How is it connected, how formatted (what filesystem is used, i.e. NTFS, FAT32, exFAT etc?).

The problem occurred when the HDD became 4tb and needed the GPT partition.

Not only when it became an NVMe M.2

Peter Toth wrote:

The problem occurred when the HDD became 4tb and needed the GPT partition.

Not only when it became an NVMe M.2

When I had another motherboard but NTF and UFI. I still had this problem

 

SURE driver why some motherboards boot from USB and I can use it but not GPT partition.

 

Peter Toth wrote:

Peter Toth wrote:

The problem occurred when the HDD became 4tb and needed the GPT partition.

Not only when it became an NVMe M.2

When I had another motherboard but NTF and UFI. I still had this problem

 

SURE driver why some motherboards boot from USB and I can use it but not GPT partition and UEFI particion.

 

Peter, sorry to keep repeating questions but how is the 4TB HDD drive connected to your computer, and is this your backup drive?

Have you tried creating the Windows PE version of the Acronis Rescue Media?

See the following KB documents:

KB 63226: Acronis True Image 2020: how to create bootable media

KB 59947: Acronis True Image Linux-based bootable media boots into black screen after selecting any option in the option menu

KB 61667: Acronis True Image: exFAT partitions are detected as empty by Linux-based media

KB 63295: Acronis True Image 2020: How to restore your computer with WinPE-based or WinRE-based media

If I Create USB media click "simple" not "Advanced"

old:

I have "C" "D" "E" particion. I always backup from "C" and boot particion" to "E:\backup" folder 4 tb HDD is UEFI and GBT

Now:

Disk0 NVMe M.2 drive "'C" particion

Disk1 "D" "E" "f" particion. I always backup from "C" and boot particion" to "E:\backup" folder 4 tb HDD is UEFI and GBT

Peter,

WinPE/WinRE is it's own OS and is not related to your hard drive OS that stores the drive letters you would normally see, in it's own registry and settings.  So, WinPE/WinRE will not always map partition letters (volumes) the same as you would normally see them in your main OS, or even as you might see them when booting other WinPE/WinRE on the same system.  Instead, WinPE/WinRE will try to find the drive letter information in the registry (if possible), but it can't always do this, especially if on a multiboot system, but even-so, on a single OS boot system.  If it can't, it will assign drive letters in order based on the response of the disks and partitions on them.  It could even be that you boot the same rescue media once and get certain drive letters, and boot the same rescue media on the same computer and get a different order of drive letters again.  

WinPE/WinRE will always boot the rescue media OS as X:.  Beyond that, it's a crap shoot.  

The best way to backup in recovery media to make sure you know what's what, is to

1) assign unique partition names so it's easy to identify them if doing individual partition backups or

2) backup an entire physical disk when possible, but still using partition names to help identify a specific disk as well, especially if you have multiple physical disks that are the same make/model/size.