Warning "After operation completion, operating systems will not boot from destination disk in the BIOS"

David, how are you performing this test, from within Windows or by using the Acronis bootable rescue media?

Starting a recovery from within Windows can lead to an unbootable system because it changes the Windows boot configuration data to create a temporary boot entry for a linux environment to boot ATIH within.

The recommended method of doing a recovery is to boot from the Acronis bootable rescue media on CD/DVD or USB stick, that way, there are no alterations to the Windows BCD store configuration.

Before starting a recovery, you should also go into Computer Management / Disk Management and check the arrangement of all your partitions and the settings for the same, to note which is set as Active to enable it to boot.

I would recommend taking a look at 117004: Great Acronis "How-To" videos and other Acronis Resources which has some good video tutorials on doing this type of activity.

Steve

Thank you for your comments.  They were helpful but I haven't yet been able to solve my problem.  Perhaps you could help me further.

Firstly the behaviour I reported in my first post was after booting from Acronis bootable rescue media.

Following your comment I've been into Disk Management (as administrator) and none of the partitions are marked as active.  Two of them (Windows C: and FAT 32 SYSTEM - EFI System Partition) have a right click menu but the option to "Mark Partition as Active" is greyed out.  But the Win 8.1 system always boots with no problems.  

I've had a look at some of the tutorials you suggest; I'm still digesting what they say.

In the meantime I've found that I only get the warning when I have selected the whole disk at the "select the items to recover" stage.  The documentation (5.1.1.3 Recovering your system to the same disk) shows choosing one partition (with flags Pri and Act) and not choosing "MBR and Track 0".  If I do this (flag Pri only) I get the Finish page showing deletion of the Windows partition and then recovering the same partition.  Fine (assuming the Act flag isn't necessary) but that doesn't address the other three partitions.  Do these need to recovered as well?

I would welcome any comments you have.

David,

Couple of thoughts here, I would recommend getting hold of a spare hard drive to do your recovery tests to, so that you leave your current system drive untouched.

Second, looking at my son's Lenovo UEFI laptop, I don't see an active partition for that either, see attached screen shot from that laptop in case it helps.

Last, a web site with information about the Windows Boot Configuration Data store (BCD) which will help you understand the importance of your EFI System partition to your recovery scenario.

See https://www.boyans.net/RepairWindows/RepairWindowsBCD.html

The message indicates that the rescue media has been booted in CSM/Legacy BIOS mode and the system you're about to recover will only boot in UEFI mode.  If you boot the rescue media in UEFI mode, you will not see that message.  You need to always boot the rescue media in the same mode that is required for the operating system to boot.

If I configure my motherboard to boot in dual UEFI/BIOS mode, I am presented with the options in the screenshot below when I press F12 to access the boot menu to select the rescue media.  Selecting UEFI: SanDisk Cruzer 1.26 will boot the rescue media in UEFI mode.  Selecting SanDisk Cruzer 1.26 will boot the rescue media in CSM/Legacy BIOS mode.

Joey, thanks for giving your comprehensive answer to this post.

Joey

Thanks very much for your posting.  It's helped to make things clearer to me.  

My motherboard is an Asus A88XM-PLUS and the procedure to get it to boot into UEFI mode from a recovery disk seems to be rather different than the one for the Cruzer board you outline.  So I'm outlining the process here for anybody like me that is new to booting into UEFI on the ASUS board.

First enter the UEFI Bios (F2 or DEL on my computer) on the EZ Mode page. The boot priority box at the bottom of the page gives icons for the boot devices: the system attempts boot order left to right.

There are two icons for CD/DVD; one has a blue UEFI below it.  This should be moved to be the first in the boot order.  With this set, exit the bios.

The Acronis UEFI loader is then displayed.  Choose option 1 ATI .......

Start recovery in the normal way and choose "recover whole disks and partitions"
At the "Select items to recover" the whole disk can be selected.  This includes "MBR and Track 0".
Then at the "Select destination of Disk 1" there is no warning about the destination disk not being bootable so I think the process will complete correctly.  

I'm assuming that this will recover the archive back to its original place on the disk.  But I haven't tested this because I don't have a spare disk available - so I can't guarantee these instructions.

"The message indicates that the rescue media has been booted in CSM/Legacy BIOS mode and the system you're about to recover will only boot in UEFI mode.  If you boot the rescue media in UEFI mode, you will not see that message.  You need to always boot the rescue media in the same mode that is required for the operating system to boot."

Does this mean I'm in a Catch-22 position?

I have a Dell Aurora R5 which came from the factory with operating system on a 512GB NVMe drive (and data on with a regular 2TB hard drive) When I start up using the TI rescue media DVD (created on the same machine I'm working on), the NVMe is not visible. According to KB 58006 I need to change the SATA setting so that "RAID On" is disabled. My Aurora R5 does not have an option with the title "disabled", but I can switch the SATA mode from "RAID On" to "AHCI". With the computer in "AHCI" mode, the NVMe drive and its contents are visible when booting from the TI rescue DVD. All seemed good until I proceeded to Restore the system image back to the NVMe. Note: the system image came from the same NVMe and it was a full disk image ("C" plus 3 hidden partitions just as it came from the factory). If I try, TI states. "Warning! After operation completion, operating systems willnot boot from the destination disk in BIOS."

Oh, in case it make a difference, when I boot from the TI rescue DVD, the boot manager is set to boot the DVD drive in UEFI mode. So the computer is in UEFI mode and the NVMe has RAID On mode disabled.

Am I getting the warning when attempting to restore an image because the NVMe is not in RAID On mode, or for a different reason?

From experience, I already know that my Aurora R5 will only boot from the NVMe if the SATA mode is set to "RAID On". TI rescue DVD needs the NVMe in "ACHI" mode and the computer needs the NVMe in "RAID On" mode for booting Windows 10. AmI in a Catch-22 spot? Or can safely ingnore the warning? 

My question is this: If I ignore the warning and proceed to restore the full disk image, will things be OK if, after the restore, I reenter the computer setup to change SATA back from "AHCI" to "RAID On". Will my system be able to boot? Or will it be a brick?

I don't have a 2nd NVMe to swap in to do a test to answer the question myself. And I'd rather not buy a second NVMe because I'd have no use for it after the test since my Aurora only has one slot for a NVMe. 

Fortunately I don't need to do a system restore to the NVMe at the present. But I do want to know that if need be TI will be able to restore to the NVMe and leave it in a bootable state (after I switch the SATA mode back to RAID On so the computer can see the NVMe when booting up). I'd hate to be faithfully making TI system backups and then one day find out restoring an image would make the NVMe unbootable. 

Any insights would be most welcome.

Brian

I think you'll be fine - sounds like you're booting UEFI mode (black screen with white DOS-like menus options for Acronis?).  I believe the message is because you're switching to AHCI as a work-a-round for your RAID enabled NVME drive.

You could instead opt to create WinPE bootable recovery media.  

If you want to use WinPE, you need to add the RAID controller drivers.  To create the WinPE, download the latest Windows 10 ADK and install - you only need the top 3 items checked when prompted which pieces you want to install - roughly 3.4Gb to install.  Once installed, run your ACronis media builder but pick WinPE instead of the default Linux media - it will build the WinPE automatically.  I suggest using a USB flash instead of a CD or DVD since you're going to need to inject the RAID drivers into the PE so it needs to be something you can modify.

Once you have your USB flash drive made with Acronis, grab DISMGUI.  This is a GUI tool that runs Windows ADK commands for you to simplify the driver injection process.  Launch it using right click and "run as administrator".  On the first tab "Mount control" under WIM file, you navigate to the USB flash drive >>> sources >>> boot.wim.

Under "Mount location" You then point it to a temporary location (an empty folder that you should create first) that will be used to "mount" the boot.wim file.  Click on "Mount Wim"... should see success.

Now move to the second tab in dismgui which is "driver management" point it to where your RAID controller drivers are.  You should download and extract them to a folder first (here is the link for them - get the 64-bit version) and then point dismgui to the 64-bit folder that you extracted.

Click the button "add drivers"

When you see succes, go back to the 1st tab again.  

Click on "Dismount Wim"

You'll be prompted if you want to commit the changes or not - say YES to save the changes.  The boot.wim will now be updated with the drivers and you're done.  

Hi Bobbo.

I really appreciate the detail you have given for each step. It gives me confidence to attempt to build the WinPE bootable recovery media which will make backups and restores more straightforward than the workaround I was considering.

Just to be sure I understand, should "not" be "now" in the last sentence: ie "The boot.wim will not [or now?] be updated with the drivers and you're done."

Thanks again.

Brian

Correct, it will now be updated. No spell check , sorry about that.

To Restore Win 10 Image to brand new or "Disk Cleaned" hard drive;

Step 1 - Go to BIOS and make sure your boot mode is in UEFI mode

Step 2 - Boot computer using Acronis boot media

Step 3 - Tools & Utilities - > Add New Disk -> Initialize with MBR option

Step 4 - Restore using image  - Select all partitions

Finished

Worked for me

OK so there was a little trick I have to do to get it to work.  Select all partitions then deselect the MBR partition then reselect the MBR partition. You will now need to go through each partition and assign it to the unallocated space you want to restore the image do. Make sure when you get to the settings of the partition "System" which should be your  boot partition, That you set the partition to active.

 This work for me on a Windows 10 Dell system. 

Joey's post of 6/8/16 did the trick for me: switch to UEFI boot. Thank you!

I believe your answer did not even have the closness of being true, because I amworking from your recovery media and get the same warning, and the sema explanation. (Meaning zero) Thank you very much, including the support you provide. (zero)

Please see KB 59877: Acronis True Image 2017: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media which has screen images showing the differences in these two boot modes.

Within Windows, run the msinfo32 command which will show what BIOS mode your Windows OS uses, then choose the same BIOS mode when booting from Acronis Rescue Media.

Note: If you clone or restore a drive in Legacy BIOS mode it will be partitioned using MBR.  If you do the same in UEFI BIOS mode, it will be partitioned using GPT.  Using the wrong partitioning method will give the error message in the title of this forum topic.