Skip to main content

THe resulting "cloned" disc is invalid; Windows will not boot properly

Thread needs solution

1) I am running Acronis True Home 2017 from a DVD; ie not inside Windows.

2) The source drive is a Sandisk 500GB Solidstate drive running a perfectly running good version of Win 10 (64 bit ) which is my C drive that boots Windows.

3) The Destination drive is a formatted Western Digital 500GB hard drive which is my D drive.

4) I ran a Clone operation from the DVD; from C to D.  It took about 45 minutes and says Completed Successfully at the end.

5) I ran the clone in the "As Is" mode.

6) After all of that, I changed the boot drive priority in the BIOS and restarted the PC.  It gets into Windows with the small blue 4 segment graphic with the spinning dots and remains there forever.  Clearly that Windows image is bad.

I tried all of the above twice carefully. 

What am I doing wrong? Thanks.

 

0 Users found this helpful

Without further information it is difficult to be certain what the problem is. I suggest you do two things:

  1. Check out the thread in the ATI 2017 forum [IMPORTANT] CLONING - How NOT to do this
  2. once you have reviewed that thread, please repost in the ATI 2017 forum with full details on how you did the clone.

One common problem is leaving the original disk in place. It must be disconnect before you reboot.

Ian

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Jim Calvert wrote:

If I DO leave the original / source disk in place , what goes wrong?? 

 Hi! Having two drives with the same Disk Dignature can confuse Windows, here our MVP Steve Smith posted a good explanation of why it happens https://forum.acronis.com/comment/428574#comment-428574

[Moved the thread to Acronis True Image 2017 forum]

 

I did physically detach the C drive and the D drive did in fact boot. But it took 20 minutes of furious disk activity to do so.

Thanks everyone for your help.

Very odd, but at least you are now up and running.

I wonder if universal restore was applied after the clone - this was uncovered recently in 2018 and 2019 if the clone process detected the new drive to be on a different storage controller.  That would explain Windows loading new drivers at startup which could have delayed the boot.