Skip to main content

Cloning does not begin upon reboot. Acronis True Image 2016. Then there is an error in normal reboots as well!

Thread needs solution
Beginner
Posts: 1
Comments: 0

Two issues, that are related:

When attempting to clone the C: drive from Windows 7 (64 bit) to a USB-connected HD (same size), the machine reboots but never enters the pre-Windows environment to perform the cloning. It stops and asks for a key-press to boot Windows.

Then, on every reboot of the PC (with the USB disconnected, and the boot sequence verified to point to the bootable HD) the machine stops dead and gives the error message "Non-system disk. Click any key to continue" again. When I hit a key, Windows starts.

To reconfigure the PC to boot normally, I have to boot from the Windows Recovery Disk (after changin the boot order), go to recovery mode and open a termirnal window, enter the commands:

bootrec /fixmbr

bootrec /fixboot

bootrec /rebuildbcd

Then change back the boot order to boot from the Internal HD.

Only then can I boot Windows normally. But cloning is still impossible!!

As you can imagine, this is not ideal!

So what is your solution to this? I paid for this software and I expect support.

0 Users found this helpful
Legend
Posts: 113
Comments: 31105

Hello Pierre,

Welcome to this user forum where other users (like myself) will try to help you.  If you need direct support from Acronis then you should read the following post: 18623: How to get Technical Support: Tips, Tricks and Useful Information which has more details on how to do this.

With regards to cloning, then I would not recommend trying to do this from within Windows, even though the Acronis application allows you to try to do so.

Secondly, I would not recommend cloning from your internal to an external USB drive.

Please see KB Document: 56634: Acronis True Image 2016: Cloning Disks which describes the recommended process for cloning your drive and has a video demonstration for this.

I would recommend having the latest ATIH 2016 build 6569 bootable rescue media which can be created from within the application (assuming you have 6569 installed) on DVD or USB memory stick, or else can be downloaded from your Acronis Account as an ISO file to be burnt on DVD.

You should test that your computer can boot correctly from the rescue media and that all drives can be 'seen' within the standalone ATIH application.

See also KB Document: 45831: Acronis Software: Unbootable System after Cloning Operation which covers some of the situations where cloning can result in an unbootable system.

Lastly, an alternative to cloning is to do an entire disk backup of your current working Windows 7 OS drive to an external backup drive, then restore that full backup to the new Hard Drive, this will give the same result as cloning.

The one warning when doing cloning or duplicating a drive with backup/restore is to ensure that you do not try to boot into Windows with both drives connected, as this can cause other issues due to duplicated disk signatures for the identical drives.

Forum Hero
Posts: 70
Comments: 8346

As Steve mentioned, please use the offline bootable recovery media to start the clone.  When started in Windows, you are telling Acronis to reboot the system, modify the bootloader, instert itself and attempt to boot from a new Acronis partition on the system.  However, if your system bios is not conifgured to allow booting from third party applications (i.e. if you have secure boot enabled, or if the media on the drive doesn't have driver support for your hardware), it will fail  to boot into the new parition and since it can't continue, won't be able to then restore the Windows bootloader.

By booting with your offline recovery media, there will be no need for Acronis to modify the Windows bootloader (bonus #1).  You will then be able to verify if the default bootable media can detect all of your drives (bonus #2).  You can then initiate the clone and hopefully it will complete as intended.  

Keep in mind of the other warnings about cloning:  1) you should move the original disk to the USB and put the new disk exactly where the original was and then clone from the USB to the new one  2) after the clone is complete, do NOT boot the system yet.  Remove the original drive from the USB connection first so that only the new drive is detected by the bios during boot.  This is because the bios will see them both as being the same with the same hardware ID. 

If you are within your 30 days of support, Acronis techinal support will help you free for all issues.  Recovery issues are always supported for free as well.  You are in the user forum though, so to demand support here, really does you no good, although many of us are willing to help where we can. As an example, I'm on vacation in a foreign country, but in my down time drinking beer, I'm still here answering posts becuase I choose/want to, not because there's any obligation to do so as I'm just an Acronis user like you.

Forum Hero
Posts: 70
Comments: 8346

As Steve mentioned, please use the offline bootable recovery media to start the clone.  When started in Windows, you are telling Acronis to reboot the system, modify the bootloader, instert itself and attempt to boot from a new Acronis partition on the system.  However, if your system bios is not conifgured to allow booting from third party applications (i.e. if you have secure boot enabled, or if the media on the drive doesn't have driver support for your hardware), it will fail  to boot into the new parition and since it can't continue, won't be able to then restore the Windows bootloader.

By booting with your offline recovery media, there will be no need for Acronis to modify the Windows bootloader (bonus #1).  You will then be able to verify if the default bootable media can detect all of your drives (bonus #2).  You can then initiate the clone and hopefully it will complete as intended.  

Keep in mind of the other warnings about cloning:  1) you should move the original disk to the USB and put the new disk exactly where the original was and then clone from the USB to the new one  2) after the clone is complete, do NOT boot the system yet.  Remove the original drive from the USB connection first so that only the new drive is detected by the bios during boot.  This is because the bios will see them both as being the same with the same hardware ID. 

If you are within your 30 days of support, Acronis techinal support will help you free for all issues.  Recovery issues are always supported for free as well.  You are in the user forum though, so to demand support here, really does you no good, although many of us are willing to help where we can. As an example, I'm on vacation in a foreign country, but in my down time drinking beer, I'm still here answering posts becuase I choose/want to, not because there's any obligation to do so as I'm just an Acronis user like you.

Beginner
Posts: 0
Comments: 3

Hi Everyone,

                  For the last two days I have been trying to clone a drive without success. Scenarios include;

1. Clone internal to external usb ssd - Failed to boot with 0xC0000007 failure.

2. New drive inside laptop, master is in Apricorn caddy. Clone external to internal, same error.

I had suspected that the bcdedit was trashed because the clone looked good in every way.

From Windows 10, Performed a recovery drive: http://answers.microsoft.com/en-us/windows/wiki/windows_10/how-to-create-a-recovery-drive-for-reinstalling/58df9c7d-84de-4652-9952-8bac34abc6c5 (Took about 30 minutes to create)

Then I booted up with the recovery drive and selected command prompt. Entered Bootrec /rebuildbcd.

That seemed to do the trick. I will add more details.

 

Forum Hero
Posts: 70
Comments: 8346

1. You cannot boot Windows from a USB external drive - this is a restriction imposed by Microsoft prodcuts unless you have Enterprise versions which give you access to Windows 2 go features.  There are other 3rd party products that can help with this, but they go against the Microsoft EULA and would be a violation of the software license agreement so I can't recommend them.  You can Google for Windows 2 go alternatives though...

2. Before the clone, make sure to do a full shutdown (shutdown /s) or restart.  Windows 8.1/10 use fastboot which actually hibernates the drive instead of shutting down and can cause issues.  A cold boot or restart will help ensure that is not part of the issue.

After the clone, did you remove the original drive before booting the OS?  This is important as the bios sees them as the same drive since they are clones of each other.  

After a clone, you should also go back into the bios before booting and make sure the new drive is listed as the first boot priority.

Also, did you start the clone from Windows or with the offline recovery media?  Always use the recovery media!!!!  And when you do, make sure to boot it so that it matches your OS install... boot Legacy if your OS is installed as Legacy/MBR or boot it UEFI if the OS is installed as UEFI/GPT.  How you boot it determines how the disk will be formatted in the process.  

If possible, I would also suggest formatting the new drive in advance and ensure it is already initialized and has the same structure as the OS (MBR or GPT). 

3.  If #2 was done to the T and it's still not bootable, try creating the WinPE recovery media and using that instead.  You just need to have the Windows ADK installed on your system first to use it (it's a big download though - about 3.4GB when installed after selecting the first 3 options).  I would suggest downloading the Windows 10 ADK 1511 (even if you have a Win 7, 8 or 8.1 system - it's compatible) to build your media.  I'd also like to point you in the direction of our MVP tool which creates a much nicer version of the WinPE with Intel Raid drivers, a web browser, file explorer and more.  

  Curious to see if the WinPE works better for you than the default Linux recovery media (assuming you used the recovery media in the first place).

Beginner
Posts: 0
Comments: 3

Bobbo,

          I was posting my experience regarding how I got my clone to operate. I did not expect the external drive to boot. I did expect the several step clone to operate as advertised. Since my experience and others have been similar reagarding the process I thought I would share what I did in order to make everything work. Spending two days trying to understand why the clone did not operate as expected is not what my previous experience was with Acronis. Since Acronis and two other products all yielded the same results I wanted to understand what the issue might be and how I would resolve it. As such I shared that experience so others would have an option should they be in the same boat.

  1. You cannot boot off a USB unless you add drivers accordingly, but that wasn't my expectation.
  2. I thought, and was wrong, that I would be able to make an exact copy of the drive.
  3. Clone process: (External bootable drive --> laptop internal was new drive)
  4. After the clone process I removed the external usb drive so that the internal, default drive, would boot. It didn't.
  5. I used the recovery drive, which I booted off of, in order to execute the Bootrec /rebuildbcd command from the command prompt.

The new internal drive booted fine after the bcd was fixed.

 

Hope that helps clarify the scenario.

 

Forum Hero
Posts: 70
Comments: 8346

Thanks Jay for the clarification - I hope it helps others too.

The clone is an exact copy of the original drive for all intensive purposes to the data that resides on the cloned drive after the process.  

However, the bios is smarter than the OS and also knows that the physcial drive is different as it knows that the physical drive is different based upon vendor information in the hard drive firmware (seral number, make/model, smart reporting information, etc).  I think this may have an impact for some users based upon how their sysetm firmware deals with this.  There is a a lot of varition among bios firmware.  As an example, I've had 2 custom Gigabyte motherboards for the last 5 years.  Both of them have been terrible with detecting new hardware whenever a physical drive is connected or remvoed (even USB if you plug it in or remove it at the wrong time during bootup or after being in the bios).  I thought I killed my previous motherboard because it became unbootable after migrating to a PCIE NVME drive, but now I know it was a firmware issue and I could probably go back and bring it to life if I had another case to throw it in. About 2 weeks ago, Gigabye moved all of the firmware to a single version across their different Z170x boards and I went from F6 to F20c and now, after 5 years, it finally detects drives correctly and doesn't demand a bios reset after I swap drives around (or if I unplug a USB flash drive anytime between boot and the OS booting up).

I will have to do some more testing with cloning on this system to see how it behaves, but just havent' gotten around it.  On other systems (legacy especially), cloning has worked whenever I've used it.  On UEFI systems, there do seem to be more non-boot issues after cloning, but I suspect these to be UEFI and/or bios-specific limitations as to to how the motherboard handles these drives that appear to be the same to it, but that it knows is not exactly the same based on what's reported to the bios firmware. 

Beginner
Posts: 0
Comments: 3

Followup - What made this even more interesting is that I had the same Kingston 240Gb SSD for the source and new destination. The beauty in this is that the drive is non-uefi and that minimizes the opportunity for issues as you mentioned. Somehow the clone should be identical right down to the BCD boot order but is in a funky state with the boot drive being set to unknown. After the Bootrec /rebuildbcd command it understood that the OS directory structure was there and allowed the BCD boot order to get fixed. You have to admit, that falls short of an identical clone. I work with disk magnetics and I will try to do some work to understand where the clone goes wrong. The disk structure is 100%, the MBR is 100%. After the MBR it tries to recognize which disk to boot from per the bcd, no go.

Moral of the story, if your suspected boot drive looks like all of the directory structure is in order and you get subsequent errors like:

0xC0000007
0xC000000E

Chances are your MBR is good and the BCD is damaged.

I found this link which will save me some typing.

https://neosmart.net/wiki/0xc000000e_selected_entry_could_not_be_loaded/

Thanks for your comments, I appreciate it.

 

Jay

 

 

 

Frequent Poster
Posts: 4
Comments: 566

Hello Jay,

Thank you for the simple explanation of your steps, the outcome and how to address it.

Just in case you will require any further investigation of the issue - you can always submit a support ticket and we would be glad to troubleshoot the problem, nail down the root cause of the possible BCD corruption.

Regards,

Slava

Beginner
Posts: 0
Comments: 1

I read very quickly through these, watched the video and am still confused.  I have an internal SSD, and wish to replace with a new larger SSD. I am trying to clone internal to the replacement SSD, which is connected via USB.  Part way through I get a message about rebooting.  I do this and nothing gets completed.  Can anybody just give me some simple steps to complete this? I bought the new drive, I bought the adapter to read the new SSD, I bought the cloning software and yet I still can't use the new SSD.

Forum Hero
Posts: 213
Comments: 5435

With ATI 2017 (and 2015, 2016) you get better results if you clone using the recovery media. I strongly recommend that you read the thread: [IMPORTANT] CLONING - How NOT to do this!!! Thing can go very wrong when you clone from within Windows due to the need to reboot to the Linux recovery media.

This may change with ATI 2018; the beta that we tested allowed cloning of system drive without the need to boot into the Linux recovery. Hopefully it will be retained in the release version.

Ian