ATI 2015 clone keeps repeating
I have an HP Envy 700-147C that's a year old. I'm using Win 8.1. I am having a persistent problem with terminating the clone program after it is complete. I set up the clone process to automatic, source & target are each 1Tb & are connected to SATA. When the clone is finished, it automatically shuts down the PC. If I then restart it to see if the clone is successful it boots with the Acronis logo & goes right into what seems to be a repeat of the clone operation. It will not respond to the cancel button & the only way to stop it is to pull the plug. Fortunately, the clone was successful & I am writing this on it now. However, if I put the original source disk in the pc, it will start with the Acronis clone again.
Several questions:
1. How can I stop Acronis from booting up & beginning the clone on the source disk? I want the source disk in the pc, not the clone.
2. Is this normal for the Acronis clone operation?


- Log in to post comments

Hi Enchantech
For some reason the source disk is now booting normally. I don't know why. However, I followed your advice to see what Acronis tasks are running & I did not see Trueimagetools. I assume this is because it only runs when a clone is being done. I would have thought that the startup programs are disk dependent, I.E. they reside on the boot disk. Your advice gave me a possible idea for future cloning. I will not shut down the pc automatically after cloning. I will start taskmanager, find trueimagetools, disable it & then restart. Does that make sense?
- Log in to post comments

Yes it does make sense. In the future in Task Manager under the Processes tab you should find the trueimagetools as well. You have the ability to select the process and choose End Task from that view.
We MVPs recommend that clones be made from the Recovery Media instead of from within Windows. That practice would eliminate your issue as well.
Had the trueimagetools executable still been running on your machine you would have found it in the startup tab in Task Manager. I suspect a restart of the machine killed it and fixed your issue. At any rate glad you got it sorted out.
- Log in to post comments

Thanks for the speedy response.
Advice well taken.
Cheers.
- Log in to post comments