Skip to main content

Cannot get past "select destination drive" when trying to clone

Thread needs solution

Cannot get past "select destination drive" when trying to clone

If I try to clone my OS drive on my Windows 10 system, I can select the clone method amd the source drive but when I select destination drive the acronis spinning clock spins for 10 mins before a list of disks is presented. Sometimes it just seems to hang and however long I wait no destination (internal or USB) disk list is presented?

What is worng here please? Any suggestions. I do not have any disconnected network drives.

(have jujst updated to latest version, 3/12/2015)

Thanks, Mel

0 Users found this helpful

Are you attempting this while booted into Windows and using the installed application?  If you are you shouldn't be.  The clone procedure and/or a recovery procedure of a system OS drive if run from the Windows installed program requires that the computer reboot into a Linux based environment to perform either procedure.  Therefore, it is recommended that the user create Recovery Media using the Media Builder tool which will create this Linux environment on a CD/DVD or USB stick which can be used to boot the machine and run the TI application to perform a clone or a recovery of an OS system disk.

I am using the "clone" procedure built into Acronis 2016, starting from within Windows. This doesn't specifiy the procedure you suggest. I don't see any other way using Acronis - once one has selected the source and destination Acronis does indeed re-boot into its own OS (I presume Linux) and then creates the clone outside of windows. This used to work perfectly OK with little delay in allowing a destination to be selected. Recently (after Win 10 upgrade I THINK) this prevaracation in selecting a destination has begun.

 

Attachment Size
313107-124156.jpg 23.91 KB
313107-124159.jpg 22.52 KB

You are correct in that the computer does reboot into a Linux environment to perform an OS system disk clone.  That reboot however can be problematic and I agree that Win 10 has made that even more so.  So to avoid this problem it is simpler, easier, and a bit safer to just create a Recovery Media Disk, boot to it, and perform the clone.

Enchantech wrote:

You are correct in that the computer does reboot into a Linux environment to perform an OS system disk clone.  That reboot however can be problematic and I agree that Win 10 has made that even more so.  So to avoid this problem it is simpler, easier, and a bit safer to just create a Recovery Media Disk, boot to it, and perform the clone.

Ok - will try this at weekend. Thanks