Skip to main content

F11 Acronis Boot / UEFI Loader does not work.

Thread needs solution
Posts: 3
Comments: 3



I have a problem that the Acronis Boot function - UEFI Loader / F11 key does not work.

See Attachment.

What needs to be changed and how?

Attachment Size
IMG_20200702_230652_1.jpg 777.9 KB
0 Users found this helpful
Forum Hero
Posts: 207
Comments: 5018

Is this a new problem - you could do it before but nit no longer works. Or is this the first time you attempted to do it?

What operating system are you using, for example Windows 10 Pro x64 build 2004? What build of ATI 2019 are you using.

Does the PC have secure boot enabled?


Posts: 3
Comments: 3

OS: Windows 10 64 bit - Version 2004 Build 19041.329

PC: HP Omen 15-dn1055ng

CPU: i7-10750H

GPU: NVIDIA GeForce RTX 2060

Chipsatz: Intel HN470

Acronis True Image 2019  - Build 17750


The notebook is new.

Secure boot is on.

Boot via Acronis Windows BartPE is working okay, only not via Acronis Linux.

Posts: 110
Comments: 28569

Steffen, if your HP Omen laptop is similar to my own, then it has an NVMe M.2 SSD (plus I have a SATA HDD second drive in RAID mode).

ASRM that gives the F11 key on boot is based on a small Linux kernel OS that doesn't have support for the above devices (NVMe M.2 and RAID), so you need to use the WinPE version of the rescue media.

You do not need to use the older BartPE tools to create WinPE media - use the 'Simple' option of the Acronis Rescue Media Builder tool and this will create the media from your Windows 10 Recovery Environment.

Posts: 0
Comments: 1

hello, I don't mean to hijack this thread but my problem is very similar...

I use NVME in a RAID setup, creating the WinPE bootable media with the added driver works well I see my drive and can successfully create images.

The problem is activating the F11 shortcut recovery key. While it does bring me to Acronis, it won't apply the same driver and I won't see my RAID drive, why?

any help appreciated, thanks!