Switching Windows Boot Manager from HDD to SSD

Anonymous
2022-03-31T00:10:33+00:00

Hey all, I am Dizah.

I recently upgraded my computer with a V-GEN SSD, I installed it properly and it works. I cloned my HDD to my SSD. I changed the boot priority 1 as my SSD and disable the boot priority 2. The restart process happened, I successfully signed in to my computer. But then I checked the disk management, I found that the booting process still happens from the HDD, as this image shows.

I am unsure that I have successfully switched the booting process from HDD to SSD. If anyone could get back to me that would be great.

Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2022-04-03T03:27:26+00:00

That indicates BIOS did indeed direct the boot to EFI of the SSD. Its BCD is in use & can't be renamed. So, let's do it from the Recovery Environment (RE). But drive letters may be different there. So...

(a) Click any Power icon, then hold Shift as you click Restart.

 That should reboot to the RE at the "**Choose an Option**" screen.

(b) Click "Troubleshoot > Advanced Options > Command Prompt"

 That reboots again to a Command Prompt.

(c) Enter the following commands...

DiskPart <<<Enter DiskPart

List Vol <<<List the volumes & their letters

=== Examine the listing to see what letter is on the partition of size 118 GB. That will ===

=== be the SSD's Windows partition. Use that letter instead of E: (if different) in the ===

===BCDBoot command below. And if Volume 5 has a letter, use it instead of S:. ===

Image

List Disk <<<See that Disk 1 is the SSD by its size

Select Disk 1 <<<Focus on the SSD

Select Partition 1 <<< EFI System partition of the SSD

Assign Letter=S <<<Give it letter S (if it doesn't already have a letter)

Exit <<<Exit DiskPart

DEL S:\EFI\Microsoft\Boot\BCD.old <<<In case BCD.old exists, delete it

REN S:\EFI\Microsoft\Boot\BCD BCD.old <<<Rename current BCD to BCD.old (not necessarily S:)

BCDBoot E:\Windows /s S: /f UEFI <<<Not necessarily letters E: or S:

DiskPart

Select Vol=S <<<Focus on EFI (not necessarily letter S:)

Remove Letter=S <<<Remove the letter S

Exit

(d) Close the Command Prompt with its "X" or type Exit.

(e) Click "Continue" to reboot to Windows

That should do it. Good luck. After booting, show me the BCD. You won't be able to copy/paste in the RE, so print this out first.

Was this answer helpful?

6 people found this answer helpful.
0 comments No comments

41 additional answers

Sort by: Most helpful
  1. Anonymous
    2022-04-03T04:15:54+00:00

    I used Macrium Reflect.

    It took more than 5 hours to clone, I fell asleep while waiting the clone to finish. But I had set the computer to be shut down after the clone process finished. When I woke up, the computer shut and there was no following message that said the cloning process had fully done or not. So then I checked the size of the OS file in SSD, compared it to the size of the original one in HDD. It's the same size.

    But still, I'm not sure enough if the cloning process had been fully done.

    Is it safe to reclone the HDD again and let the clone process overwrites the data on the SSD?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-04-03T03:56:15+00:00

    Probably the problem is with the clone, maybe the boot partitions were not copied correctly, so it is not respecting the BIOS configuration to boot from the SSD.

    What program did you use?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-04-03T03:52:03+00:00

    never, the booting process always from the hdd.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-04-03T03:45:27+00:00

    Right, after clone HDD to SSD, did it ever boot from SSD at any time or never work until now?

    Was this answer helpful?

    0 comments No comments