I used AOMEI Backupper to clone my original drive to a new SSD. When I try to boot I get a blue screen that says:
Recovery Your PC/Device needs to be repaired A required device isn't
connected or can't be accessed. Error code 0xc000000e
I tried to run Startup Repair but it fails and says:
Automatic Repair couldn't repair your PC.
I tried going into the command line repair tool and I ran bootrec /FixMBR
and it apparently runs successfully and it says:
The operation completed successfully
When I run bootrec /fixboot
I get an error that says
Access is denied
and when I try to run bootrec /rebuildbcd
it sees my installation and asks if I want to add the installation to the boot list. When I select Yes(Y)
I get an error that says:
The system cannot find the path specified.
I tried doing an upgrade installation of Windows and it says it can't upgrade without having an existing installation.
How can I repair this installation? The source disk is GPT and the SSD is a Samsung 850 EVO. The original hard drive boots fine.
Did you do a bootrec /scanos before doing the repair tasks? That often fixed it for me.
Also this might help you, I believe fixmbr is for mbr disks only not for gpt disks. Basically you have to assing a drive letter to the efi system partition using diskpart and then start the bootrec /fixboot operation from inside the partition. http://www.dell.com/support/article/us/en/19/sln300987/how-to-repair-the-efi-bootloader-on-a-gpt-hdd-for-windows-7-8-81-and-10-on-your-dell-pc?lang=en
What might also be the problem is the automatic resizing those backup tools often do, which makes necessary system partitions unusable sometimes.
Best bet is to clone it again using another tool and chose a manual layout, the ssd manufacturers often provide one that is optimized for their hardware if it's not a walmart product.
My SSD was labeled as H instead of C so I received a winload.efi error. The solution I found was to use the cmd on a repair install off a usb and then type, type bcdboot H:\windows (if H is your windows partition)
I had the same problem. It was caused by one of two things.
I started again, using diskpart clean, diskmanagement MBR, and making sure not to boot to the USB connected disk and all went well. I was using Clonezilla in beginner mode and in both attempts I selected to copy the main boot record.
User contributions licensed under CC BY-SA 3.0