Salta al contenuto principale

Clone Disk Not Working

Thread needs solution

I have been trying to run Clone Disk operation for over an hour.  I keep getting an error:  Unable to clone a disk while task is running.  Please wait for all tasks to complete and try again.

My system is not currently running a Backup.  What's up with that?

0 Users found this helpful

Fred, welcome to the Acronis user forums.

The messages given by ATI when things go wrong frequently are unhelpful. For the user community to be able to offer assistance, more information would be helpful.

  1. please confirm that you are attempting to do the clone within Windows (i.e. not using recovery media) -   alive clone;
  2. please advise the version and build of Windows being used, for Example Window 10 x64 Pro, 20H2 build 19042.928.
  3. The version and build of ATI you are using - the latest build of ATI 2021 is 39216 24-March-2021; just remembered you appear to be using ATI 2020, in which case the latest build is 38530 (13-February-21)
  4. Information on the disk being cloned - for example is it the disk containing the operating system - also, does the computer have multiple operating systems installed. What type of drive is it, an M.2 SSD drive (is it NVMe or SATA), a SATA SSD, or SATA HDD.
  5. Information on the target disk - type and how it is connected; to SATA port on the motherboard, to an M.2 connector on the mother board, or to USB port.

While I have successfully cloned drives from within windows, I prefer to use recovery media for that process. However, because I am risk averse when "cloning" a system disk, I usually create a backup and then recover it to the new drive as, in the past nasty things have happened when doing a clone. If you are going to clone, please make a full backup first. 

Ian

Ian, I was able to clone this morning.  For some reason "Clone Disk" would not run last night due to some unknown process running.  I could not identify/stop that process.  It resolved overnight. 

BTW, I'm running Acronis True Image 2021, Build 39216 on a 2.90 gigahertz Intel Core i5-9400 using Windows 10 Professional (x64) Version 2009 (build 19042.928).

 

Thanks for your help.

Fred, good news that it is now sorted. Sometime shutting down and restarting a PC can solve problems, and this may have happened here.