Skip to main content

Acronis Startup Recovery Manager problem

Thread needs solution

Hello together,

I use a PC with Windows10 and the actual version of ATI2017.

I have a onboard-Graphics card and a Nvidia Graphics card. Primary card is the PCI-Nvidia Card. When I start the Acronis Startup Recovery Manager with F11, there comes a load-Screen and then a black screen and nothing happens. I have to press the reset-button to restart the computer.

I can also enter an "e" and press enter with the same result. I can't get into the Recovery manager.

Also booting from USB or CD doesn't work!

Any hints?

Greetings

Peter

0 Users found this helpful

Peter, if you are able to boot correctly from both USB or a CD then I am surprised that the ASRM (via F11 prompt) is not also working correctly, as it uses the same standard, Linux OS based, environment as the standard Acronis Rescue Media.

I would recommend opening a Support Case for this issue directly with Acronis Support to let them investigate this further.

ASRM is not widely used as far as I am aware, and I no longer use this myself due to some side effects I had with earlier versions of ATIH where some hidden partitions were being revealed and given drive letters when ASRM was activated.

The alternative approach that you could use would be to create the Acronis Rescue Media as an .ISO image (or if using the Windows PE Rescue Media as a .WIM image) and then use a utility program such as EasyBCD to add this to the Windows Boot Manager as an additional option instead of having the F11 prompt before the boot manager is shown.  See attached document showing how to do this for an ISO image.

Note: if you have an EFI / UEFI system, then you should use the Windows PE .WIM method.

Attachment Size
403823-136264.pdf 332.79 KB

Hello Steve,

 

I checked it and your are right: Booting from CD and USB has the same effect: Black Screen. So any hints, that it works?

Greetings

Peter and sorry for the confusion!

Peter, that sounds more likely that both the CD and USB rescue media gives the same issue as ASRM.

This would suggest that your computer does not like booting from the Linux OS environment present on this Recovery media / ASRM, which may be for several reasons:

If you have UEFI BIOS with Secure Boot enabled, try disabling the latter and see if it makes a difference, if it doesn't then you will need to change to creating and using the Windows PE version of the Rescue Media.

To create the WinPE Rescue Media, simply choose this option in the Bootable Rescue Media Builder and it will first prompt you to download and install the Windows 10 ADK - the ADK is a large download of over 3GB but you only need to install the top 3 options shown.

Once the ADK is installed, choose the same WinPE media option in the Builder which will allow you to create either USB or CD media.  This media can be used with Secure Boot enabled, plus you can also create a .WIM file and use this with EasyBCD as advised earlier to add to the Windows Boot Manager menu instead of using ASRM.

Note: ASRM is only available in the Linux OS variety!

I just upgraded from ATI 2016 and encountered the same issue.  ASRM worked fine prior.  I can enable ASRM from Windows 10 but after booting with F11 and selecting Acronis True Image from the menu all I get is a black screen.  Please tell me there is a solution.

I can only repeat the advice I gave to the previous poster in this topic.  Test to see if the standard, Linux based, Rescue Media gives you the same issue when booting from it?  If it does, then it may be that the Linux kernel used for both the Rescue Media and ASRM is causing the issue here.  If you have a UEFI system, try disabling Secure Boot in the settings and test again, if this is enabled.

Beyond that, the Windows PE Rescue Media should work fine, but otherwise you should open a Support Case directly with Acornis Support for this issue and reference this forum topic.

I came across this post while searching the forums and found it to be considerably more functional than ASRM.

https://forum.acronis.com/forum/127282

The addition of DD12, Universal Restore, and WiFi connectivity makes it an all-in-one solution.  I was already displaying my boot menu by default for 3 seconds, for safe mode options, so it was simply a matter of adding another BCD entry for the customized WIM file (467MB in my case).  I preferred ASRM because of the convenience and this is the perfect alternative!  I hope this is helpful to the OP and anyone else facing this issue.

Thanks to Steve for pointing me in the right direction.

Thanks for the feedback and glad to know that you have found a working solution that is best for you.

Hello together, here some news from me:

Today I wanted to Clone a Notebook HDD to a SSD on my PC. So I Started Windows, connected the 2 new drives and started Acronis Clone Disk. After done all settings, the system asked me for a reboot :( . So I did and it came like I expected: Like described above: After some Boot-Messages: Black Screen.

But today I had some more time and so I disassembled my PCI-Express Graphics Card and changed the BIOS-Settings to Use the onboard Graphics Adapter and started the Cloning again! And now it worked!

This means, that the ACRONIS Recovery Manager has a Problem if an onboard graphics card AND a PCI(-Express) card are installed! 

Can this be fixed?

Now I have some other Questions:

1) Why asks Acronis a Reboot for cloning the disks? Both are not accessed! (I checked this, there was no handle accessing the both disks).

2) I downloaded the "127282: MVP Tool - CUSTOM ATI WINPE BUILDER". Where can I find a description how I create a bootable USB-Stick with this? I never created a Windows PE before. (I don't want alwayst to disassemble my Graphics card to be able to work with Acronis :)

Greetings

Peter

Peter, please see post: 128231: [IMPORTANT] CLONING - How NOT to do this!!! for reasons why starting a clone from within Windows is not recommended by the MVP's in this forum.  One of those reasons is the limitations of support for some devices in the standard, Linux based, Rescue Media environment which may contribute to why you are seeing a Black Screen.  We have seen other users with issues due to multiple graphics cards being involved at a BIOS level, though it shouldn't be necessary to physically remove such cards.

The reason why Acronis needs to reboot when cloning is that this type of action cannot be done from within an active Windows - it has to be done from a dedicated, standalone environment.  The only time when a Windows clone is possible is if both drives are connected externally and neither disk is locked by the Windows OS for any reason, otherwise a reboot is required.

The MVP Tool - Custom ATI WINPE Builder will create a Windows PE version of the Rescue Media on USB stick which overcomes some of the limitations of the Linux version of the Rescue Media.  A prerequisite for this tool is that you must first install the Windows 10 ADK kit which provides the core WinPE functionality.  If you launch the normal Acronis Bootable Rescue Media Builder (from the Start Menu or from the ATIH GUI) then select the Windows PE version of the Rescue Media, it will automatically direct you to the Microsoft download web site for the ADK - this is a large download of around 6GB but when you install the ADK, you only need to install the top 3 options shown in the install panel.  Once the ADK is installed, then you can use the MVP Tool.