F11 Startup Timing - 2016 Version
I've seen articles for 2015 version, but they don't seem relevant to 2016.
In ATI 2016 how do you change the start up delay where F11 is displayed.
W10 *64 - TP build - UEFI.
Thanks Steve, those seem a bit out of date.
It's a bit more tricky with ATI 2016 - the files are now in the hidden system partition - certainly for W10.
I eventually got a reply from Tech support on chat.
Brief summary of the 2 main lines below:
In order to change the f11 timing we need to change asrm.xml file that is there on the hidden EFI partition.
Browse to the EFI partition, select EFI subfolder, then Acronis, and finally openasrm.xml for editing.
Being a techie I mounted the partition, enabled a local built-in administrator account, logged into that account to access the contents of the system efi partition, find the file and change it. This is not something I'd recommend non-techies to do.
Hopefully someone from Acronis will take this onboard and enable a simple GUI change/function within ATI 2017 when that comes on the horizon.
I can't see why such basic functionality is not built into ATI 2016 - to enable a change the 30-second default F11 option.
Thank you for providing this feedback which will help other users asking the same question, though I agree that making the change is not recommended for non-techies.
I am using Acronis True Image 2016 BUILD 6571, and after upgrading from Windows 7 to Windows 10 Pro x64 on a Dell Optiplex 9010, the F11 startup screen flashes for only about 1/2 second on startup. I assigned a drive letter to the EFI Recovery Partition and searched for asrm.xml, but no such file was present in any directory, although I did find an asrm.bin file. There is also no f11.cfg or f11-efi.xml in C:\Program Files (x86)\Common Files\Acronis\TrueImageHome. It appears that the configuration for the F11 startup message delay has been moved again. Acronis Customer Support was of no help; they opened a case 02748667 in which they recommended I purchase a Support Package in order to resolve the issue!
If anyone else figures this out, I'm sure many would like to know, since Acronis seems unwilling to help.
Robert, I may have said this to you or others previously, but I personally have stopped using ASRM and have no intention of going back to using it because of these types of difficulties plus other issues that I encountered that rendered otherwise hidden partitions to be exposed and given drive letters. I reported these issues to Acronis and they could not reproduce them even though I could do so on every attempt!
Since that time, I have adopted an alternative approach that works better, in my opinion.
That approach is simply as follows:
Create either an ISO or WIM image of the Acronis Rescue Media - this can be for either the Standard (Linux based) or the WinPE media. Store this / these image(s) in a folder on your hard drive.
Download and install a copy of the free EasyBCD program and use this to Add an entry / entries to the Windows Boot Manager metro menu for either the ISO image (Legacy BIOS) or the WIM image (UEFI) and then, instead of having to press F11 within x seconds at boot, you will now see the Windows Menu with this/these choices where you can control how long they are displayed for, again using EasyBCD.
See the attached document for details of how I have done the above on my systems. This shows the process for adding an ISO image, but the principle is the same for WIM images.
Hi Steve,
I haven't used EASYBCD much before - are you using this on Legacy/MBR systems or UEFI systems? I've been afraid to try it because I get the attached warning when launching it and decided it was better to just use my USB bootable media instead for fear of causing more harm than good. Curious to know if others with UEFI systems are using EASYBCD reliably on UEFI systems?
I did read this and it looks like it's more of a warning, but was just hoping that others can respond with their results and findings if they have used EASYBCD in UEFI mode as well.
https://neosmart.net/wiki/easybcd/uefi/
Hi Rob, I have used EasyBCD on an UEFI system using a Windows PE .WIM image and not an ISO and it worked well.
Hello All,
Thank you for your input. Development Team is aware of the enhauncement request to allow customization of Acronis Startup Recovery Manager delay time via graphical user interface. However, it has not been approved and most probably we will not see this enhauncement in the next version of the program.
Regards,
Slava
Helllo Slava - is additional testing being done about the hidden paritions being mapped automatically in Windows as well. I have never used ASRM because of the possibilities of bootloader corruption. However, on a recent VM that was installed in legacy mode, I went ahead and launched the full disk backup process from within Windows, it rebooted, laucnhed Acronis backed up, I rebooted into virtual recovery media using UEFI and restored the image. Result was a successful conversion from MBR to UEFI and a bootalble OS. Like Steve though, I found that I had an H: drive listed in Windows explorer, that refrences the hidden recovery parition. Stranger yet, H: shows up in Windows file explorer, but not in computer management! I then use diskpart to remove the volume letter and though it was fixed. However, upon reboot, H: drive is back and still not showing as a mounted volume in computer management. So, the diskpart removal of the volume letter will work, but only as a temporary solution. As a result, I'm inclined to still avoid ASRM for this reason, and the potential for corruptiong the Windows bootloader if ASRM fails to boot up in it's entirety for some reason.
Hello Bobbo,
Thank you for sharing your thoughts on the matter.
There was indeed an issue in Acronis True Image 2016 with hidden partitions obtaining a driver letter unexpectedly. It was supposed to be resolved in the Update 2, build 6571. I have no explanation for why the letter would show up only in Windows Explorer but not under computer disk management console.
If this problem recurs and clean installation of build 6571 or 2017 Beta shows the same behavior, this need to be reported by sending system report through "send feedback" button in the program.
Potential boot problem when ASRM does not load is specific to how it works, loading before operating system`s bootloader. The same issue would occur with any other backup software doing the same thing. Of course, computer would not boot if the loader fails to accomplish its job.
If we put ASRM as a boot option alongside Windows into Windows bootloader menu, that would allow Windows and ASRM boot independently and do the trick. But in such case ASRM would depend on Windows bootloader and would lose one of its main function: work even if entire Windows, including Windows bootloader becomes damaged/corrupted/malware-infected.
Regards,
Slava
I can build another VM and test at some point with a fresh install of Acronis. I'll have to go back and double check, but I believe this was using 2017 beta 1 as well. I need to confirm.
When I get around to it, I will try 2 scenarios. The 1st with fresh Windows and fresh 2017 beta 2 on a legacy machine with a legacy restore and see what the result is. The second will be the same base, but I will then convert from MBR to UEFI and see if the reults are the same or different. If there are any issues, I will submit a system report. I could still submit one for the existing system too since it's still operational, just can't figure out how to get that H: drive to stay permanently hidden!
This is just my suggestion, but I would prefer to see ASRM work with the Windows bootloader to avoid corruption issues that would prevent the OS from booting under regular use. This seems to be the safer method and one less destructive. I like the idea that Acronis wants to make ASRM usable on system that won't boot Windows, but if it's actually causing Windows to not boot and is not loading correctly anyway, it's hard to see the value in the current setup. It would be nice if one could use ASRM without the possibility of corruption on a regular basis, but if the system fails to boot, could then resort to their offline bootable recovery media, which is exactly what it's intended for anyway. Then, users could use ASRM on a regular basis without the possibility of bootloader corruption to easily take offline backups and/or restore on the fly and use the recovery media in the event that neither the OS or ASRM is usable. Perhaps it's something that could be considered - maybe take a sticky with a poll to see what other product users would prefer?
Thanks for the info Steve Smith. I've just gone back to ATI and seen this post updated. I have followed your pdf to update my bootmanager. Good that doing it this way it uses the same method as Macrium to boot programme to recover. Thanks. :)
https://forum.acronis.com/forum/117918#comment-392812
Finally decided to brave it. EasyBCD and iReboot work like a champt on UEFI (using .wims instead of .iso as .iso is not an option under UEFI system). Love it. Thanks for the tip, Steve.