Skip to main content

Attempt to clone from bootable media creates a boot "error message"

Thread needs solution

I attempted to clone my D-drive to a similar (Samsung 1TB 2,5") in an external USB3 dock (from True Image 2013 Plus Pack Tools and utilities).
Upon reboot the loader did not load. I got the screen attached. After I hit Enter Windows 7x64 SP1 loaded normally.

I then attempted to run clone from bootable media. I got the same screen. Hit Enter and Windows loaded.

Now everytime when I restart my computer, even if I don't have the bootable disk, this screen loads. But Enter and I am back in Windows.

I use a Toshiba Qoosmio X870 i7, 16 gb, C-drive 200 GB SSD (Intel), D-drive 1TB Samsung.

I have had some "curious" behaviour lately. When I right-click on a folder (on the D-drive) in Windows Explorer the little "time-wheel" starts to rotate, but nothing more happens. The Explorer instant seems to freeze. When I open a 2nd Explorer Window I can only see the libraries - not my computer and drives.

The exact same thing happens if I right-click on a file (e.g. to copy it).

If I go into Outlook and attach a file to a mail this works fine. I can open files in Photoshop and Lightroom.

In order to close the frozen Explorer windows I have to start the Activity Manager (ctrl+shift+esc).

If I restart my computer all works fine until the same thing happens again. Not always, but sometimes. I thought this had to do with my D-drive. Thus the attempt to clone and replace.

Any suggestions?

Attachment Size
img_3181-2.jpg 37.62 KB
0 Users found this helpful

You should go to Tools and Utilities, select Acronis Startup Recovery Manager and toggle "activate" and "deactivate" until you have enabled and then disabled the ASRM. This should take care of your startup issues noted in your attachment. It appears that the ARSM may not be compatible with your system.

Are you running build 6514?

The right-click behavior was an issue in the earlier build (5551) and there is a patch http://forum.acronis.com/forum/38423#comment-122173 for build 5551 that corrects it. The 6514 build should not need this patch, but another user has also reported this issue. http://forum.acronis.com/forum/41376.

I would first try and run a "Repair" install from the 6514 installation file to see if this helps. One user said after upgrading from 5551 to 6514 that this problem occurred, but a repair install corrected it.

Hello everyone!

Thanks for taking your time!

James, thanks for you support, we're very appreciated for your help!
Goranwk could you please tell us solution James gave you helped or not, and yes, build number is 6514?

Kind regards,

Sergey