Acronis EFI Loader Delay
Dear Acronis Forums,
this question is about the "Acronis Startup Recover Manager" Module of ATI 2013 Home. Is there any way of changing the time the Acronis EFI Loader waits for a keypress to a more "noninvasive, lower value"?
The 30s delay really gives me the creeps, especially with a Samsung SSD inside which normally boots up the whole machine in under 10s.
I would personally go for something like 5s, which is more than enough time for pressing F11.
Thanks,
MZ
Marvin,
In the folder "C:\Program Files (x86)\Common Files\Acronis\TrueImageHome" there is a file with the name "f11-efi.xml.
I have not tested this yet!, but it appears the "F" key and the "delay" value can be changed.
Open the f11-efi.xml file in notepad and change the "delay" value.
In order for the changes to take effect, you will have to deactivate the ARSM and then re-activate the ARSM for the new (edited) file to be used.
This method works for non EFI systems by editing the "f11.cfg" file instead of the "f11-efi.xml" file.
Please post here if this works for your system.
Thanks,
James
Hi Marvin,
It works. After editing the f11-efi.xml file you need to de-activate Acronis Startup Recovery Manager before re-activating to read the new config details. Thanks for pointing where the config file was.
Kumar
Note: This worked on my 2015 version as well. Thanks James.
Hi all
Not working on 2016 version with Windows 10 pro x64... no such files f11.cfg or f11-efi.xml...
Methode here : https://kb.acronis.com/content/49958
Show hidden & system files, searching for f11-efi.* (I'm on EFI BIOS) -> nothing found :(
Nothing in the Registry Base... Boot time is very long (30 sec), we have to reduce this delay in options !! Acronis please !!
I have the same Problem with 2016!
But my Boot_time ist to short! 1 or 2 s. So it is difficult to press F11!
I am having the same problem. My startup time has TRIPLED since adding Acronis 2016 to my Win 10 laptop.
Acronis , PLEASE help. 2 to 3 seconds is all I need, not 30 seconds.
For the 2016 version there is a solution for this issue as well, however it requires a program that is able to either edit or copy files to/from the Efi system partition.
I use the paragon rescue media for this.
in the Efi partition you will find an Efi folder and inside an acronis folder with the file asrm.xml. Copy that file to your system drive so you can edit it.
In Windows open it in notepad and change the delay value to whatever you please, save, and copy it back onto the Efi partition, overwriting the original file.
tested and works like a charm.
Acronis must have heard my plea because suddenly I no longer get the F11-message at all. I did not do anything myself. I'm back to a 15 sec boot. Yea.
Thanks to Christian for pointing out a valid workaround to this issue.
Another way of accessing configuration file with timeout value is below:
1) download and unzip PsExec from https://technet.microsoft.com/en-us/sysinternals/bb897553.aspx. It will allow to modify configuration file in protected EFI partition without reboot
2) open Start menu, type cmd, right-click found result and select "Run as administrator"
3) type diskpart and assign a letter to your EFI partition. See https://technet.microsoft.com/en-us/library/cc757491%28v=ws.10%29.aspx for instructions how to assign a drive letter to a partition from command-line interface. When your are done and EFI partition has a letter, type exit to exit from diskpart utility. At this point you will still be in command-line window, launched "as administrator"
4) type or paste path to PsExec.exe, for example "C:\Users\Rob\Downloads\PSTools\PsExec.exe", then add parameters -i -s and finally type the name of text editing application, e.g. Notepad:
"C:\Users\Rob\Downloads\PSTools\PsExec.exe" -i -s notepad.exe
This will open Notepad under SYSTEM account. Then just click File - Open, browse to the EFI partition, select EFI subfolder, then Acronis, and finally open asrm.xml for editing
5) change default 30 seconds to any other number. You can also modify text that appears in Acronis UEFI boot menu by editing that asrm.xml file
6) click File - Save and close black command-line window. Now Startup Recovery manager will use your custom delay value.
Regards
Thats not bad, but isn´t there an easyer Way to fix the problem?
My Startup time is 1s, so its to short. But I didn´t know where to find the EFI Partition?
Edit: I found the partiton, but without Acronis Folders :(
Regarding Slava's solution:
Using Acronis True Image 2016 BUILD 6571 on Windows 10 Pro x64
It was easy to assign a drive letter to the EFI partition in Disk Management and gain access to its contents. Following the procedure using PSTools to open Notepad under a System Account was not helpful, because Notepad was unable to read from most of the directories. However, simply browsing to the EFI partition using its drive letter, it was possible to search for asrm.xml, using Windows 10 search or a more powerful Norton search facility -- no such file is present. In fact, list the full contents of all directories, it was possible to see that there is no .xml file at all anywhere in the partition. Apparently Acronis have moved the Startup Recovery Manager configuration settings once again.
It would be nice to know where they are hidden now, so that the delay time for pressing F11 can be set as desired. On upgrading to Windows 10, it was reset to less than a second, not enough time to press F11 unless you know exactly when it's coming before you see it.
Robert, please see post: http://forum.acronis.com/forum/119326#comment-362862 where this was raised for ATIH 2016 recently.
I would recommend submitting Feedback to Acronis development using the feedback tool in the ATIH GUI Help section on this issue as this should be an option that can be set when activating ASRM rather than having to edit hidden partition files!
Thanks for the suggestion, Steve. I have sent Acronis a feedback message as you suggested.
Note that I have been in touch with Acronis Customer Support on this issue. They assigned a case number to the problem (02748667), and rather ungraciously suggested that I purchase a Technical Support Package in order to resolve the issue!
Hopefully someone else will figure this out, since help from Acronis does not appear to be forthcoming.