Skip to main content

Cloning process stuck

Thread needs solution

Hello.

I bought WD SN850 1TB drive that came with Acronis software.

Now I'm trying to clone my old SSD, which is only 500MB to the new one, using the Acronis for WD version. But the problem is that it always gets stuck. After a brief message saying "locking drive c:" it's stuck in preparing for ever.

I left it the all the night and it didn't move an inch.

I tried contacting WD support, but they sent me here, and I don't seem to find a license number in that version of the app, so what can I do.

I attach a photo of the state of the process.

For reference, the old one is also an M2 drive, which I plugged in the second M2 slot, PCIE 3x only, and that I'm using as the current boot drive. The idea was to be replaced by the new one.

Anyone can help?

Attachment Size
Screenshot 2021-03-05 123812.png 21.15 KB
0 Users found this helpful

Joao, welcome to these public User Forums.

See KB 2201: Support for OEM Versions of Acronis Products which applies to all OEM versions of ATI supplied with hardware purchases.

I have never tried cloning any NVMe M.2 SSD drives and have no PC's with 2 x M.2 slots to even try doing so.

Personally, I would not recommend using cloning for this scenario but would recommend using Backup & Recovery, which has worked successfully for the times that I have wanted to upgrade or change my own NVMe M.2 drive.

To do this, it is best to create the Windows PE version of the Acronis Rescue Media and boot the PC from this to do the Recovery, ensuring that you use UEFI boot mode as required for NVMe M.2 drives when used to boot the Windows OS.

See KB 65508: Acronis True Image 2021: how to create bootable media and KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media

KB 65539: Acronis True Image 2021: How to restore your computer with WinPE-based or WinRE-based media

See forum topic here Steve migrate NVMe SSD where I documented upgrading my own NVMe SSD using ATI 2020 with screen images. 

Hello Steve.

Thanks for the tips.

I actually was able to sort out my issues. By creating a Recovery Disk and starting the cloning process from there, it went without an itch. Could be better labeled though. It was a bit of guess work to determine that the clone process could be started from there.

As for that KB 2201, it's funny. Because I tried contacting Western Digital first and they were the one that sent me here.

Anyways, problem is solved now. Thanks a lot