2020 Rescue Media boot CD only results with hanging WIndows Start screen

Steven, welcome to these public User Forums.

One significant difference between the ATI 2010 rescue media and ATI 2020 versions you listed above is that ATI 2010 is based on an older Linux kernel OS, and 2020 is now defaulting to using WinPE.

You can still create Linux rescue media using the Advanced option of the media builder tool, so would suggest giving that a try first.

Hi,

One thing you might try with the WinPe based Rescue Media is to open "Boot Options" at startup\restart...

Usually Esc, F9, F11, F12, and look for a "UEFI" version of your Acronis boot media..

My first experience with this is that the WinPe Rescue Media is created for UEFI Bios based machines whether the machine it is created on is using UEFI Bios or not..

Most computers will try to boot from CD\DVD and Flash Drives in "Legacy Bios" mode unless instructed differently with Boot Options..

I personally prefer the Linux based version..

Thanks for the responses,

Since I posted my problem I created another Rescue Media "Using Windows AIK to create bootable media".  That one worked, albeit I'm disappointed with its performance.   A restore of my system took over two hours, a system that Window 7 was able to restore in less than an hour.

I think my problems with the two Acronis rescue media builder options I first tried are that my computer only supports “Legacy Bios” and not UEFI, but that’s not right.   I think Acronis should support older systems or at least warn you that they don’t.

I think I might try the Linux version and see if that performs any better.

I had the same issue with my Win7 computer and TI2020. It was mentioned here, and I found, that TI2020 Build 22510 creates issues in the boot disc and Win7. When I went back to TI2020 Build 21400, and created the boot disc with that build, it worked.

Hi, I'm facing the same problem:  Rescue hangs up. 

This discussion tells to give a solution.

Where can I find Build 21400 ?

And when I'm running Windows 7.  Can I use a Linux rescue boot, to recover my W7 system-backups ?

I Did a test on my new W10 workstation (Legacy, not Uefi), every thing worked fine. I have a 3 PC licence for ATI standard.

My W7 workstation is Legacy.  Does the latest WinPE only work for Uefi?  My rescue builder reports WinRE.

Look at Mustang's post which is pinned to the top of this forum. Sounds like the same issue.

https://forum.acronis.com/forum/acronis-true-image-2020-forum/how-repair-ti-2020-build-22510-boot-disk-created-windows-7-using-simple-option

I have spent numerous hours building CD rescue disks and USB drives and F11 option of rescue boot for ATI 2020.   I have used Linux and Win PE options and none work.  I am running Windows 10.  I need to restore my drive and am ruining out of time.  I have also tried PCI=nobios and  opcmcia options for kernel and the only thing I get is “Acronis True Image is Loading...”.  I have waited up to 40 mins and nothing happens.  
 

What’s up with this software?  

I am getting closer to the point of regretting this 2020 upgrade.

Pedro, welcome to these public User Forums.

Sorry but more information is needed here to understand why you are seeing a problem here?

What make / model of computer do you have?
How does it boot from the BIOS into Windows 10?  UEFI/GPT or Legacy/MBR?

What is the problem that is leading you to need to restore your drive?

The kernel parameters are only used by the Linux based rescue media, which is what is used when you use the F11 key to invoke ASRM (Acronis Startup Recovery Manager).

Do you have a second PC available for testing?

The answers to the above will help us to try to understand why you seeing a problem.

If your computer is still able to boot into Windows 10, then run the command: msinfo32 to find the BIOS mode used by the OS to boot.  This will show as either UEFI or else Legacy or the disk drive name of the OS drive.

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

See KB 63226: Acronis True Image 2020: how to create bootable media and use the Simple method which creates WinPE media using files from your Windows Recovery Environment.

You can check that the WinRE environment is good by opening an Administrator level Command prompt and typing the command: REAGENTC /INFO and looking at the result.

C:\WINDOWS\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: f613c408-ab3e-11e9-ac1c-a86daa71efa2
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

If you have a spare / test computer to use, try booting the WinPE rescue media on that PC to show if it will boot correctly to the offline ATI application panels.

I had a similar problem a while ago where it was determined that the Acronis Rescue Media Builder was consistently using the wrong recovery partition. In my case, I'd updated from Windows 7 to Windows 10 and the builder was using the Windows 7 recovery partition.

Here is the thread that describes it. Response #20 is where I got to a solution.

https://forum.acronis.com/forum/acronis-true-image-2020-forum/failure-create-working-winre-rescue-media

Hi Steve,

First, thank you for giving me some of your time in solving my problem.

In regards to my system, it is legacy system.  Not a brand computer though.  It is a gigabyte motherboard with a Xeon CPU, 8GB Ram, and HD-5970 video card that I use as workstation and media server at home.  The hardware is 100% stable and I know it is legacy.

Until now, it was running Win 7 Pro x64 and my main backup/restore tools have been Norton Ghost 15 (NG15) and Macrium Reflect Free (MRF).  I had ATI 2015 in Win 7 but I always preferred NG15 over any other software.

With my recent upgrade to Win 10 Pro x64, I cannot rely on NG15 unless I upgrade to Veritas.  Then, I have MRF and I decided to look more into ATI 2020 because of the incremental backups.  So, I bought it to give it a try.  With my online upgrade to W10, not clean installation, I have been upgrading other software for 2D and 3D design.  In this process of uninstalling and installing, not only my main apps but other software I don't use anymore, some of the recent setup programs I need are not running correctly.  That is why I want to go back to a known good image and that happens to be in ATI2020.

I do have the option to still boot with either Windows, W7 and W10.  Some days ago I did another W10 image recovery/restore using MRF and it worked perfectly.  In W7 I did my HD to SSD and later an SSD upgrade with NG15 and the process was a breeze.  Now, my most recent image is in ATI2020 and I cannot boot the PC up because I have failed in created the rescue media.  I tried to restore booting up in W7 using ATI2015 but the image is reported as corrupted.  In W10 with ATI2020 the image is validated as good.

As my next step, I will read the two references you sent me and will follow the instructions.  Then, I will report back my results.

As far as reagentc /info, it is reported as disabled.  Is it the additional partition created by W10 in the main drive?  if it is, I will fix it.  I had to change the BCD when I decided to add back another drive with W7 in hope of doing something with ATI2015.

Million thanks again,

Pedro Gonzalez

BrunoC wrote:

I had a similar problem a while ago where it was determined that the Acronis Rescue Media Builder was consistently using the wrong recovery partition. In my case, I'd updated from Windows 7 to Windows 10 and the builder was using the Windows 7 recovery partition.

Here is the thread that describes it. Response #20 is where I got to a solution.

https://forum.acronis.com/forum/acronis-true-image-2020-forum/failure-create-working-winre-rescue-media

Hi BrunoC,

After I upgraded to Windows 10, I removed the Windows 7 recovery partition of the drive after the 10 days go back trial period.  Leaving only the most recent Windows 10 recovery partition along with the main partition on my SSD.

I will check out the link you mentioned.

Pedro

Pedro, some comments on your latest updates:

First, any backup created by ATI 2020 is likely to be using .tibx file format which none of the previous versions of ATI have any idea of how to use, so will report as being corrupt!

Secondly, having a dual boot system can cause issues with the Windows Recovery Environment used by the ATI 2020 'Simple' method of creating rescue media.  I have seen this myself on a laptop where I have 2 copies of Windows 10 (Home and Pro) plus Ubuntu 18.04 LTS.

To resolve the WinRE issue, I downloaded and installed the Windows ADK and PE files then used the ATI 2020 Advanced method to create WinPE rescue media which uses the ADK & PE files.

See forum topic: Important change for Advanced Acronis Media Builder starting with Windows 10 1809 for more information about the ADK & PE files.

Note: the MVP Custom PE Builder script (link in my signature) can also create the WinPE rescue media using the ADK files with a more comprehensive desktop environment and extra utilities incorporated.

Steve,

The image of W10 I created with ATI2020 is a .tib file because I imported the backup I had from ATI2015.  I believe that is why they report the same extension.  I understand that forward compatibility is not guaranteed even though they have the same extension.

Thanks for the new directions.  Right now, I am working on getting my Windows RE hidden partition back into BCD.  I can see Winre.wim file in the \Recovery\WindowsRE\ folder. It is timestamped with day and time of my W10 upgrade.

Steve and BrunoC,

I am happy to report that I was able to create the bootable recovery media in USB.  First, I fixed the hidden recovery partition: 1) changed partition type to 07, 2) assign drive letter R, 3) “reagentc /setimage /path r:\recovery\windowsre”, 4) reagentc /enable, 5) remove drive letter and change partition type back to 27.  After successfully adding and enabling (reagentc /enable) the hidden Windows 10 recovery partition,  I removed Windows ADK from the apps and created the USB bootable rescue media (advanced) with Windows PE and Windows RE selection; no drivers added.

I was able to reboot and perform the image recovery with success.  Now, I am fixing back the recovery partition in the old image that I just recovered.

Thank you for your help!!!!

Pedro

Pedro, nice to hear you got it back in shape!