Salta al contenuto principale

Cloned SS 970 EVO Plus M.2 SSD won’t boot after being swapped into a MS Surface Studio Gen 1

Thread needs solution

Aloha - I used Acronis True Image to clone a relatively newly installed 2TB WD Blue 3D SATA that is my boot drive.  The target drive is a Samsung 970 EVO Plus NVMe M.2 2TB drive.  Acronis indicated that the clone had completed successfully.  I then swapped the 2 drives, but am getting error msg. 0xc000000e.  I have gotten to the command prompt using a Win 10 recovery USB drive and checked to ensure that the 2 drives in the MS SS are both online.  That didn’t work....so then attempt to let Win 10 repair itself....that took awhile, but also didn’t work....so, now I’m at a loss.  Also, I have the “old” WD Blue M.2 in a 3.0 USB case and it isn’t being recognized on my other computer (MS Surface Book 2).  Both the original and the target drives were originally formatted using GPT and I used the Automatic mode in Acronis True Image 2019.  Any assistance you can lend would be very much appreciated.  I’d rather not have to repeat what I did last time (I.e., when I installed the WD M.2 I had to rebuild windows and then load all of my programs from scratch....a very time-consuming process to say the least).  Mahalo! 

0 Users found this helpful

I got a bit confused. Somehow the post ended up in the ATI 2015 forum rather than ATI 2019, as you were using ATI 2019. I have successfully cloned from SATA to M.2 NVMe, so it can be done.

The first thing we need to know is how you did the clone: did you do it from within Windows or using the recovery media?

While I have successfully cloned both from within Windows and with recovery media, if I am dealing with a mission critical PC abundant caution dictates the slightly more complicated creating full backup and then recovering to the new drive (both using the recovery media).

If you used recovery media, why type did you create: Linux, WinRE or WinPE? The latest build of the Linux media seems to fully support NVMe M.2 devices; this support is relatively recent.

When something goes pear shaped with a clone, I would either try to do the clone again or do a recovery rather than spending time trying to repair the non-working windows installation.

If memory serves me correctly, to clone to M.2 you need to run recovery media in UEFI rather than legacy (bios) mode. I assume you did this if you used recovery media.

Ian

Probably need some more info. However, in my experience, surface pros come bitlocker encrypted and have secure boot enabled by default. And if bitlocker is not actually encrypted, it may be flagging the disk is locked anyway. 

First, turn off secure boot in the bios. Then make sure bitlocker is fully disabled and not flagged as locked on the drive while booted back into it in the original system location.

Then, when you shutdown, do a full shutdown (cmd prompt and shutdown /f /p)

Then boot the rescue media and make sure it is booted in UEFI mode and not Legacy!! Then attempt the clone again.