HP 17-G153US Laptop
Windows 10
EaseUS Partition master 14 used to clone
Here is a shot from EaseUs and my device manager. My cloned SSD wont boot when installed but will from usb connection. I have cloned hard drives without this much trouble in the past. Any help or guidance you can provide is greatly appreciated.
Thanks,
Todd
Streak27
For starters, what happens if you disconnect the HD (disk 0), and connect the SSD to the same SATA connection that was connected to?
NOTE: If you cannot connect it to the same connector, you may possibly need to go into the BIOS to tell it which device to boot from.
If that still doesn't work, you may need to boot from your Windows install media, choose repair Windows, and tell it to fix problems preventing Windows from starting.
Thanks for the reply
I booted from the usb externally and it started up fine, got to the desktop without issue. When I installed directly to sata and attempted to boot, it was unable to boot and advised me to use windows repair module to assist.
I don’t have a Windows 10 disc to use to repair. Was researching using a flash drive to assist with boot and repair.
Is the anything in need to do to the disc prior to installing it in the computer? I notice disk 0 and disk 1 don’t look identical or have the same info in the partitions.
Samuria, The only difference is the size off the SSD is smaller but I see the obvious differences in labeling, format, etc.
The partitions are going to look different because your source was 900+ GB in size whereas the SSD is only 400 some odd GB. Disk cloning software will typically take care of those differences for you and everything should be good so long as there is not more data than can fit on the destination.
I've noticed that a lot of people on this forum suggest creating an image backup from the original drive and then restoring the image to the new drive rather than an actual clone. That has been known to work when clones were problematic and that is the method that I typically use as well.
When you clone a Windows disk, the EFI System partitions on both disks will contain the same info such as BCD required to boot Windows. The BCD is correct in the source disk but on the destination disk still contains the same info from the source disk.
You'd need to rebuild the BCD on the cloned disk so that the correct info will point to it.
Use partition master, assign an available drive letter, for example: "S" to the EFI partition on disk 1 (your SSD) then open the Admin command prompt then type:
bcdboot F:\windows /s S: /f UEFI
This will rebuild the BCD in disk 1 with correct info to boot Windows from F.
Once done, remove the letter.
Reboot.
topgundcp, thanks for your reply, tried what you suggested and got the attached result.
When startup repair is ran now does it produce a srttrail.txt with error message or code?
Open administrative command prompt and post images of these commands and results:
Code:bcdedit /enum all bcdedit | find "osdevice" diskpart lis dis lis vol sel dis 0 det dis lis par sel par 1 det par sel par 2 det par sel par 3 det par sel par 4 det par sel par 5 det par sel par 6 det par sel dis 1 det dis lis par sel par 1 det par sel par 2 det par sel par 3 det par sel par 4 det par sel par 5 det par sel par 6 det par exit bootrec /fixboot bootrec /scanos bootrec /nt60 sys bootrec /nt60 all
zbook, Here is a full screen shot once i ran it.
Quote
