Skip to main content

clone disk issues

Thread needs solution

I have been utilizing Clone disk with ATIH for a long time. On upgrade to version 2014 (purchased last night), I am unable to use. The dialog box for Source disk comes up, I click on my C: drive as the source. The "Clock" comes up as it analyzes the drives... and never returns. The disk drive activity light is lit solid so something is happening... but no joy.
I ran CHKDSK /f on the C: Drive, but there were no errors to fix. This is a clean install of Windows 7 SP1 and a new purchase of ATIH 2014. I am lost. No issues with any other installed applications.
Open to suggestions...

0 Users found this helpful

More info: the clone disk issue arises when trying to run clone disk within Windows. If I boot the ATIH recovery disk, I am then able to successfully utilize clone disk. Which also adds a whole new problem. Running clone disk outside of windows, there is a warning that ATIH puts on the screen indicating the drive letters may be different than windows. That's cool, but there has to be a way to differentiate between the source and the destination... when both drives are the same manufacture, model, and size (which I have). Otherwise you could run clone disk in the wrong direction!!

In summary, there is a problem with clone disk under Windows, and there is a potential problem with clone disk under the recovery environment. Neither of which I ever experienced with ATIH 2012 or ATIH 2013.

Do the clone when booted from the TI Recovery CD.

When selecting the source and the target be very observant of what is displayed at the bottom of the screen.

When clicking on a target such as disk A, the bottom picture will show the partitions of disk A such as would show in Windows Disk Management. Or, it disk A is new, the bottom picture will show as all unallocated space.
Do NOT use drive letters as any type reference.

Don't forget, you have 30 days from date of purchase to get help direct from Acronis or live chat .

Trying to run Clone from within the Windows environment is risky if attempting to clone the active disk which is the case in your scenario. Doing so can often result in data corruption on the source disk leading to unbootable system. Always use a live instance (boootable media) when performing such an operation.