Skip to main content

When a clone isn't quite the same

Thread needs solution

I purchased a new Asus Windows 8.1 laptop, and I usually make an Acronis Disk image backup before the first boot up, I didn't get that done this time. I did make a whole disk image backup shortly after however.
In order to play safely I put in a new hard drive and restored the backup. The system booted and appeared to work ok, until I tried to invoke the recovery with F9 during boot. Then I get a blue screen error which happens every boot thereafter until I restore the image backup again. The screen reads as follows:
Recovery
Your PC needs to be repaired
a requested device isn't connected or can't be accessed.
Error Code: 0xc0000225
You'll need to use the recovery tools on your installation media. If you don't have any installation media (like a disc or USB device.), contact your system administrator or PC manufacturer.

So, my question is - why is a clone not a clone?

I did this with backup/ restore of the whole drive, when I tried the actual clone process it crashed with a blue ( or maybe black ) screen after quite a while, Segmentation fault I think it was.

0 Users found this helpful

With laptops the manufacturers often have non standard partitioning or sector sizes of the disk.

As far as cloning is concerned, try reverse cloning, put the new drive in the laptop/PC and the original drive in an external caddy, clone from external to internal.

If you have a Secure Zone or Try and Decide setup disable it for the clone.

That is exactly how I did it many times. I tried once going the other way, with the same results.

It happened to me as well that restoring a whole disk backup will screw up the OEM recovery partition location or records, although it was with the 2014 version, and the 2015 is supposed to be better at not messing with the original partitions order and placement.
Put your original disk in a USB adapter, then boot on the Acronis recovery USB and do a clone (not an image) of the original disk to the new disk in the system. Disconnect the Old disk before booting. That might fix your issue.

Pat L wrote:

It happened to me as well that restoring a whole disk backup will screw up the OEM recovery partition location or records, although it was with the 2014 version, and the 2015 is supposed to be better at not messing with the original partitions order and placement.
Put your original disk in a USB adapter, then boot on the Acronis recovery USB and do a clone (not an image) of the original disk to the new disk in the system. Disconnect the Old disk before booting. That might fix your issue.

Sadly I did do it this way, I had started this using 2014, and when that didn't work I upgraded to 2015 hoping that would fix it. No luck though. Using 2015 the actual "clone" process actually crashes with a segmentation fault. At least 2014 did not do that. In Backup/Restore whole disk - they both do the operations, the result is bootable but the F9 keypress during boot trashes the BCD