Skip to main content

operating system will not boot from the destination disk in the bios

Thread needs solution

I cloned a drive and the system hung when trying to restart to complete the clone. I ended up downloading the bootable version of ATIH 2012 and went to retry the clone at which point I saw the following warning:
"warning after operation completion operating system will not boot from the destination disk in the bios"

I'm not sure if that wasn't there the first time or I somehow missed it, but sure enough it won't boot using either the old or new drive. The source is a 250 GB Seagate and the destination is a 160 GB WD.

Any suggestions are welcome....

0 Users found this helpful

I have not seen your error before. Did you double check the BIOS to make sure the correct bootable disk was selected? On first boot following cloning, only the cloned disk should be attached.

Which version of Windows is involved?

Cloning has been known to fail if the source disk has disk errors. You should check the source disk for errors
From a command prompt
CHKDSK C: /R

After correcting for errors, my suggestion would be to redo the clone when booted from the TI bootable CD.

Boot from the CD.
Use the TrueImage Add disk option and delete the existing partitions from the target disk so the target disk becomes blank. Be careful to choose the correct disk.

Then redo the clone and shutdown.
Reboot with only the cloned disk attached.

If this should still fail, post a screen capture of your Seagate as displayed by your Windows Disk Management graphical view.

If this is Windows 7, do you have a Windows install or recovery disk?

I have seen this and it is basically a warning message to let you know that the UEFI settings in your BIOS need to be updated to allow the clone to boot.

On a Dell Latitude I had to go into the BIOS settings under boot sequence. Then under the UEFI settings it will show the Windows Boot for the old hard drive. It seems to be tied to the serial of the drive. If you click on add new, it will populate with the cloned drive serial, you simply just give it a name (I called it Windows New) and copy the boot location from the existing entry (bottom line). The EFI files it needs to boot with are stored in a hidden partition on the drive (which also much be cloned) - this is what you are pointing to.

Hope this helps someone as it took me some time to figure this out and it is very poorly documented either on this site or elsewhere on the net.

Rob

I saw this error on a new ASUS Essentio series. With guidance from Rob above I went back into the bios and in the end I had to change the secure boot OS type to "Other OS" before the system would boot from the cloned drive.

Bob

I am having similiar problems in NEW Acronis 2015 clone disk.

I get this message....
--------------------------------------------------------------------
WINDOWS FAILED>>>>
Insert installation disk & Restart
Click Repair your computer
0xc000000e
--------------------------------------------------------------------

I just rebuilt 2 systems... new asus mother boards, 2 new SSD drives in each system so cloning backup would be simple,

and ACRONIS will not produce a bootable clone

I have been using ACRONIS for 5 years and the ONLY REASON I BOUGHT THE NEW 2015 version is do co CLONED BACKUPS..

and it does not work....

dan fickes wrote:

I am having similiar problems in NEW Acronis 2015 clone disk.

I get this message....
--------------------------------------------------------------------
WINDOWS FAILED>>>>
Insert installation disk & Restart
Click Repair your computer
0xc000000e
--------------------------------------------------------------------

I just rebuilt 2 systems... new asus mother boards, 2 new SSD drives in each system so cloning backup would be simple,

and ACRONIS will not produce a bootable clone

I have been using ACRONIS for 5 years and the ONLY REASON I BOUGHT THE NEW 2015 version is do co CLONED BACKUPS..

and it does not work....

Yes, I t does work when performed properly. No, you cannot boot Windows from an external drive. You should never leave both drives attached when booting Windows after cloning, as Windows will render one unbootable and it may not be the one you expect.

Please search the forum for "Clone" to find the many posts outlining our recommended procedure. For example, we recommend that you clone only after booting from the ATI bootable Rescue Media, not from Windows. Also, it would be equally effective but safer to perform a full disk mode backup and restore it to the new drive, rather than to clone.

I use Acronis 2011 version and I found that cloning on a UEFI (version of bios) computer is a problem firstly from the increased amount of time it takes.   Also my Acronis rescue cd crashes when trying to boot it up on a UEFI based computer (at the second splash screen), so I tried the Win 7 installed version and it clones, but is very slow and not sure if the clone would actually work or not, since the slow cloning completely turned me off to not going any further.

What I do is to clone everything on a legacy bios computer using the Acronis rescue cd, even when the ssd or hhd is for a UEFI based computer.  They work fine and the cloning is very fast.

To mitigate the opening up of a UEFI computer every time for back up (cloning) I have installed a DSHOT ssd caddy into its floppy slot so I can jerk the drive during down time, clone them in 10 minutes and reinsert them.  The legacy computer with a dual DSHOT caddy allows the same fast connect  interface for both original and copy.

If you have a dual DSHOT in the UEFI computer you can immediately boot to either the clone or the original when a problem occurs (which is what I set up).

Yeah, I know it is not a necessity to have UEFI for Win 7 or Win XP.

 

 

Hello Gerald,

Thank you for your feedback.

Do you experience slow cloning issue on UEFI computer when both disks are connected with SATA cables directly to motherboard, without DSHOT? It looks like some extra job is done per each read/write request. Disk that is inserted in DSHOT may work fast in Windows and be slow at cloning just because in Windows you access it at file/folder level and cloning requires block-level access. The caddy/interconnector may slow it down as an extra step in cloning procedure, especially if read/write requests to 2 disks are not aligned in time properly.

Regards,

Slava

I don't believe Acronis 2011 fully supports UEFI systems? Do you have the plus pack?  I'm guessing since this was the first iteration of UEFI/GPT support, it could be the problem as UEFI was fairly new 5 years ago and only started becoming mainstream about 3 years ago.  More current versions of the bootable rescue media may have better results as EFI support in the KB articles seems to pick up in 2013.  

13644: Acronis True Image Home 2011 Plus Pack

 

and

https://kb.acronis.com/content/24878

Cause

Your system or bootable partition is located on a dynamic or GPT disk.

Standard Acronis True Image Home 2011 does not support backup of dynamic and GPT disks.

Solution

If your system is BIOS-based, you can use Acronis True Image Home 2011 Plus Pack to back up GPT disks. See Acronis True Image Home 2011 Plus Pack.

For dynamic/GPT disks support, please see Acronis True Image Home 2012: GPT & UEFI Support.

Nope, partition style is MBR as noted in Win 7 disk management of UEFI computer.  As I understand it the system boot disk must be MBR.

I do not have the plus pack.

Gerald,

You can boot an OS on a GPT/UEFI formatted drive just fine unless your particular bios has some limitation that prevents it - but it shouldn't if it supports both.If your motherboard supports UEFI and your OS is intalled UEFI, typcially your OS hard drive would be formatted GPT.  

Regardless, if your OS was installed MBR and Legacy mode, then that is just fine and 2011 should be able to boot the rescue media in legacy mode too.  

However, is your bios configured to allow booting of Legacy/CSM/Bios mode if it supports both UEFI and Legacy/CSM mode?  Often times, UEFI capable motherboards, first require that you DISABLE Secure Boot.  Please make sure that has been done.  Then, you usually have to ensure that CSM\Legacy Mode is enabled too.  In some cases, you may also need to ensure that your primary boot device is the USB or CD/DVD (whatever your bootable media was created on).  

Also, we've seen a lot of posts with bad media creation - could be during the creation process (bad burn or something).  Sometimes, it's just the particular UsB drive or disc used.  One user had verbatim discs and usb drives and they all failed - every time.  He switched to different brands for both discs and flash drives and they ALL worked after that - he was using Verbatim discs and flash drives by the way (the ones that always failed)

As long as the bios is configured correctly, the media being used for the creation is good and there was no corruption during the media creation process, there's no reason Acronis bootable media shouldn't launch.  I use the same Acronis bootable media (although a more recent version since 2011 is 5 years old and less likely to work on newer hardware that may be UEFI/GPT only) and it works on multiple Dell's, HP's, Surface Pro's, Asus tablets, Acer tablets, Winbook Tablets, Vulcan tablets, custom Gigabyte motherboards, and basically every computer I've ever used it on.  

Once you've verified all configurations in the BIOS and perhaps tried creating new media on a different device, please also try to boot the media using your one time boot/boot override menu to ensure the correct option is being used during boot (legacy for a Legacy installed OS or UEFI for a UEFI installed OS)

One time boot menu example Legacy and UEFI options (note that it shows secure boot is disabled too)

thank goodness for your OP @David Mitchell!

I also see "warning! after operation completion, operating system will not boot from the destination disk in the bios"

It's 6 years later and still this cryptic warning from Acronis without saying the simple solution. I've attachd image here of restore warning in Acronis Rescue Media 2017 to help others. Yes, the solution above was to go into BIOS and reselect in my MSI boot order my UEFI boot drive. thanks guys!!

How about putting this in the warning message or are we the only 2 humans that don't know you need to reselect bootdrive when restoring a UEFI drive? LOL

 

Attachment Size
410024-138217.jpg 2.22 MB

Erol, welcome to this user forum - the point being that we are all users here, including the MVP's.

If you want Acronis to make changes to their program design, then please use the Feedback tool in the application to send this suggestion to them.

Thanks Steve!

I'm guessing, the message has been there for 6 years. I must be the only one that didn't get why. but maybe I'll find this post again if I forget on the next restore in 2018
:)

 

In reply to by truwrikodrorow…

Erol - well now it is seven years later and I have received that message:  "warning! after operation completion, operating system will not boot from the destination disk in the bios"

I am not a complete newbie, but I am unsure how to resolve this issue. Would very much appreciate you translating the solution for me.  Using a Windows 10 desktop and Acronis True Image 2017.  Desktop is functional but want to recover back to four days ago when printer settings/drivers were working.  Getting this warning when getting set up for recovery.  Is it safe to proceed with recovery?  What is a UEFI boot drive?  My C: drive is Samsung SSD 850 EVO 500GB and the backup was of the complete C: drive.

I change boot order (when using Acronis Recovery disk to boot up) by hitting F12 and selecting the USB flashdrive with the Acronis on it. After I do the recovery do I have to hit F12 and select my C: drive for booting, or somehow get into BIOS another way to permanently change the boot order?

Any assistance will be much appreciated.

 

Did you see my reply in your ATI 2017 forum topic on this same question?

To anyone following this thread, this was easily sorted (after advice from Steve) - just had to be more observant when booting from Acronis Rescue disk (a USB flashdrive).  There was indeed an option to boot in UEFI, and when that option was taken all problems recovering from backup and warning messages resolved.