Starting Acronis UEFI Loader Error 0x14800001

see file attached

Francisco, try starting the clone from within your offline bootable Acronis recovery instead of in Windows (this is the Acronis recommended method).  

1) Perhaps the default Linux envrionment of Acronis on the local machine does not have drivers for your hardware (can be the case with newer PCIE NVME hard drives).  Booting wiht thhe offline reocvery media will confirm if you can see your drive this way or not

2) your bios may be preventing the Acronis bootloader from running (secure boot may need to be disabled).

3) Are you cloning to the same size disk?  Cloning will fail if the disk is smaller than the original (usable space)

4) Cloing may fail if the sector size of the disks is different.  Spinning drives 2TB and smaller use 512kb sector size.  Spinning drives larger than 2TB and most SSD's use sector size of 4K so a clone will fail.  IN these cases you need to take a full disk backup and save the backup to another location.  Then restore the backup to the new drive.  The results will be the same, but you'll also get a backup in the processs (which is good).

5) If the default Acronis Linux bootable media boots, but does not see your new hard drive, the drive may not be initialized yet.  Use "add a new disk" to initialize the new hard drive first.  If the disk is not found in this process, the Linux bootable media doesn't have the necessary drivers for your new hard drive and you will need to create a WinPE bootable disk instead - try all of the other things before we get to that though.

BE VERY CAREFUL when initializing a new disk - this will format/wipe the one you select - if you choose the wrong one, you can wipe your original data and it will not be recoverable unless you have a good backup to revert to already. 

Thanks for the answer Bobbo,

My main problem is that now the computer isn't able to start from the initial HD. I need a solution for that allow me to start the computer from the HD before I could apply any of the proposed ways to proceed. I will try with Hiren's CD to recover the previous EFI boot file.

Thanks in advance.

Hello again,

I've started with a Hiren's CD and in the HD first partition (FAT) I've found in the EFI\Boot three files:

Boot1

Bootx64.efi

Bootx64.xml

The actual xml file has a LoadKernel section that start the acronis loader followed by a Jobs section with a Rename to restore the original .efi.

It seems clear that I need to restart with the boot1 File, but my question is: Should I modify something in the Bootx64.xml file?

Actual bootx64.xml fie content:

<?xml version="1.0" encoding="UTF-8" ?>
<Config>
    <LoadKernel>
        <Kernel Arguments="product=bootagent quiet force_modules=usbhid" Path="/acroldr/acroldr/kernel64.dat" />
        <GPT Guid="6467ACD5-82B1-45EF-9999-ED61685F81A8" />
        <Ramdisk Path="/acroldr/acroldr/ramdisk64.dat" />
    </LoadKernel>
    <Jobs>
        <RemoveFakeBootNext />
        <Rename FileNameSource="\EFI\Boot\boot1" FileNameTarget="\EFI\Boot\bootx64.efi" />
    </Jobs>
</Config>

After a HBCD Mini-XP boot I've renamed the boot1 to boot1.efi and restart the computer with the "Run UEFI Application ..." from the BIOS starting the \EFI\Boot\Boot1.efi and a Recovery screen appears with:

Your PC/Device needs to be repaired.

An unexpected error has ocurred.

Any suggestions to restart the previous EFI boot in a correct way?
Thanks in advance.

Can you run Windows repair now? Or, can you rename back and Cold boot the system, physically power down to prevent fast boot from kicking in? Cold booting may clear out a temp change in the boot loader being carried over from fastboot, but probably only if the file is as it originally existed before you manually edited it.

Thanks Bobbo_3C0X1,

I can not run Windows repair.

I didn't edited any file. I've only renamed the boot1 file to boot1.efi in order to run them from the bios option "Run UEFI application...", but I didn't edited any file. I think I should edit the bootx64.xml file and replace the actual bootx64.efi with the previous one that now is named boot1, but I did'nt edited the .xml file because I don't know how to do it, and how to modify this file? is the main question that I'm asking for.

Thanks in advance

My suggestion for the acronis software is that it not only save the previous bootx64.efi in the boot1 file but also save the content of the previous bootx64.xml file in another file in order to be easier to recover from an unsuccesfully clone operation as It has happened to me. Now I need to restore not only the previous bootx64.efi file but also the bootx64.xml file and i don't know how to do it for the .xml.

Regards

Francisco: run Windows repair, as suggestet by Bobbo_3CX01, means that you boot from a Windows10 CD or USB-Stick.

Don´t reinstall Windows 10 but use the repair options given there. I´m pretty shure, that this helps to repair your initial HDD (the old one).

You can skip this step if you already have a backup of your old HDD.

Then I suggest not to use "Clone HD" function. I suggest to mount the new Crucial SSD into your computer (remove the old HDD and install the new SSD) and then install Windows 10 from Windows 10 CD or USB-drive. After Windows 10 has set up all partitions on your SSD, you can Restore the contents of your old Windows system drive (old drive C:\) to the new drive C:\ by using an Acronis Rescue Media (either CD or USB, boot from this). If you don´t already have a rescue media, you can download an ISO image from Acronis by logging into your account on the Acronis web site (not this forum!) and goto your purchased products.

Thanks Berti,

I've used a WinPE USB and I have been able to repair my initial HDD as suggested.

Thanks again to Bobbo and Berti.

For the runtime error, initialize ur new ssd as gpt in windows disk manager, and try again

Hello,

I am experiencing the same issue. Any suggestions? I am using build 1780. I attached the error. I am deploying Windows 10.

Hi! Have you already tried the troubleshooting steps outlined in the earlier comments?