After clone to SSD....will not boot.

[Shinobiwan]

yes. Within bios setup the SSD is listed as a bootable device.

UEFI boot list refers to it as  "windows boot manager" on sata 0.

And legacy boot list will refer to it as the manufacturer name of the SSD.

There is not a one time option. It will offer that only if i have a bootable dvd in the optical drive, but only for cd/dvd. 

It basically just bypasses the ssd and goes to the end of the bootable options and trys to do an ipv6 network login. I leave these options in the list as a check to make sure its still doing some sort of boot priority.

I did another clone  over night with  EaseUS todo backup free. This time choosing the "sector by sector" and "optimize for ssd", in an attempt to check the last remaining variables of the cloning software that i have used. And again, same situation, the bios setup will see the SSD, windows 10 pro disk sees it, my windows PRE disk sees it. but the hp will not boot the dang thing.. "Boot device not found, please install operating system on your HD"

[Shinobiwan]

Actually now that i think about it, there is a boot menu, before the bios menu. But again, it lists the SSD as a bootable option for both uefi and legacy. I tried both options and nothing works. Litteraly the only thing that will boot is this WD Blue 1.0 TB that came with the computer...

list of bootable devicesInitial boot menu before bios menu

every single thing i try to get this ssd to work leads to this infuriating screen...

Could this possibly be a funcionality of the "smart" detection, maybe its detecting that there isnt a "spinning" drive at all and just completely ignoring the ssd?

[mdklassen]

> Have used the Aomei Backupper software to perform a disk clone whilst the SSD was temp installed in a USB chassis.

Did your computer boot from the SSD while it still was mounted within that USB adapter (and while the old disk-drive was detached) ?

Can you physically take both the old disk-drive and the "bare" SSD, with a bootable copy of Acronis (CD or USB) to another computer, and connect both devices to SATA ports on the motherboard -- THUS OMITTING THE USB ADAPTER -- and boot Acronis, and redo the "disk-cloning" ?  Will the SSD then boot after reconnecting to your computer?

Hint: if you have the WD (Western Digital) version of Acronis, you'll need to have a WD disk-drive attached when doing the disk-cloning, but the WD need *NOT* be either the "source" nor the "target" of the disk-cloning.

Ditto if you have the SEAGATE version of Acronis.

[Shinobiwan]

I cant use aomei or acronis, there arent free options to clone/migrate from these pieces of software and i have currently expended my budget in this project, so i cant afford to purchase or unlock the cloning options for additional pieces of software. Cant risk using any sort of non-legit software at work either.

No the computer did not boot from the usb drive,  it works in the same way. For whatever reason the mobo/bios will not boot from the ssd no matter how its plugged in via usb bay or sata. But i still can get into bios and boot menus and see the harddrive as a bootable option in its various boot menus and other windows. Macrium PE Dvd will boot, Windows 10 PRO dvd will boot, Usb recovery stick will boot......

I have tried the dual sata on another computer aproach, eliminating the usb drive but I recieved the same results as every other attempt...

At this point i think im going to just bite the bullet and do fresh windows 10 installs on all our HP's. Its really dissapointing to not be able to figure this out but i feel like i have spent so much time trying to solve a problem that is normally a simple procedure.  There is no reason it should be this unforgiving. 

If you guys have any other info on to what the problem could be let me know, 

[LeftStep]

I have no answers (a year later) but I deeply feel your pain, as I am in an identical predicament.

Did you end up just throwing it through a window?  I think that's where I'm headed...

UPDATE:  As I was heading toward the window, I tripped over the answer:

• With Windows 10 installation/recovery media open the command prompt in advanced tools

• Diskpart

• list volume (take note of boot partition volume and windows partition letter)

• select volume X (X partition responsible for booting the system, the hidden partition in fat32)

• assign letter w (to be able to recover the boot files)

• exit (exit diskpart)

• bcdboot X:\Windows /s w: /f UEFI (X = partition letter that contains the Windows folder)

• reboot system (select the new boot option if more than one)

• msconfig (Boot - delete the \Windows options and leave only the c:\Windows option)

[SailsElan]

Can you make this solution easy for a non tech person to understand? I have the exact issue and have tried the exact solutions to no avail. I’m hoping your solution can work for me but I need more step by step directions about the command prompt steps. 

[SailsElan]

I just wanted you to know that after three days of trying every idea, and tip and three types of cloning software, I tried you above "tripped over" solution and it worked!!!!!! I thought I was seeing things. I just cannot thank you enough for posting this and I hope many others find it as magical as I did!

[Grzwacz]

Greetings,

Welcome back to the forum.

I am not a HP employee.

 Are you connecting the cloned SSD (assuming the drive is a 2.5 inch SATA SSD) to the SATA port previously occupied by the existing HDD? An M.2 NVME PCIe SSD should also work in this scenario.

I don't think you need to mess with Secure boot and Legacy support because Windows 10 should boot using Secure boot mode. The boot sector on the cloned disk is identical to the HDD .

I have done this many times with zero failures.

Did not realize this thread was stale.

Regards

[SailsElan]

Just barely .... (stale). I appreciate your reply. The SSD I was replacing was not a SATA drive. I was replacing a P1 NVMe M.2 drive with the same, just larger capacity. I had the drive to be cloned in an external USB enclosure. This was so painful that I hope to never do this again. LOL.