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: Newest
  1. Anonymous
    2022-04-04T11:18:43+00:00

    OK, that's the stunted one, alright. Something (probably the ReagentC we ran) seems to have added a few essential lines to your Windows Boot Loader & Resume from Hibernate objects...

    recoverysequence {4d163c56-d6af-11eb-a988-93a3341b5547}
    recoveryenabled Yes

    That was apparently enough to get you the stunted environment. Now, we've got to get the rest of it into there, which are these...

    I know I can get the first into there (with the proper HarddiskVolume number), but I need to research the second. I'll get back to it tomorrow.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-04-04T07:09:32+00:00

    there's advanced menu after i clicked the troubleshoot button. but it doesn't have those features you mentioned. but each of this menu has restart button. do i need to click it, so it shows the features you mentioned?

    these are the pictures:

    Image

    startup settings:

    Image

    UEFI settings:

    Image

    BCDEdit:

    C:\Windows\system32>BCDEdit /Enum AllFirmware Boot Manager---------------------identifier {fwbootmgr}displayorder {bootmgr} {b45af706-b308-11ec-8c54-806e6f6e6963} {b45afde7-b308-11ec-8c54-409f38eae6ee} {b45afde8-b308-11ec-8c54-409f38eae6ee} {b45afde9-b308-11ec-8c54-409f38eae6ee}timeout 1Windows Boot Manager--------------------identifier {bootmgr}device partition=\Device\HarddiskVolume6path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFIdescription Windows Boot Managerlocale en-usinherit {globalsettings}default {current}resumeobject {3d220f61-b386-11ec-80bf-f633f337b071}displayorder {current}toolsdisplayorder {memdiag}timeout 30Firmware Application (101fffff)-------------------------------identifier {b45af706-b308-11ec-8c54-806e6f6e6963}device partition=\Device\HarddiskVolume1path \EFI\Microsoft\Boot\bootmgfw.efidescription Windows Boot ManagerFirmware Application (101fffff)-------------------------------identifier {b45afde7-b308-11ec-8c54-409f38eae6ee}description UEFI:CD/DVD DriveFirmware Application (101fffff)-------------------------------identifier {b45afde8-b308-11ec-8c54-409f38eae6ee}description UEFI:Removable DeviceFirmware Application (101fffff)-------------------------------identifier {b45afde9-b308-11ec-8c54-409f38eae6ee}description UEFI:Network DeviceWindows Boot Loader-------------------identifier {current}device partition=C:path \Windows\system32\winload.efidescription Windows 10locale en-usinherit {bootloadersettings}recoverysequence {4d163c56-d6af-11eb-a988-93a3341b5547}recoveryenabled Yesisolatedcontext Yesallowedinmemorysettings 0x15000075osdevice partition=C:systemroot \Windowsresumeobject {3d220f61-b386-11ec-80bf-f633f337b071}nx OptInbootmenupolicy StandardResume from Hibernate---------------------identifier {3d220f61-b386-11ec-80bf-f633f337b071}device partition=C:path \Windows\system32\winresume.efidescription Windows Resume Applicationlocale en-usinherit {resumeloadersettings}recoverysequence {4d163c56-d6af-11eb-a988-93a3341b5547}recoveryenabled Yesisolatedcontext Yesallowedinmemorysettings 0x15000075filedevice partition=C:filepath \hiberfil.sysbootmenupolicy Standarddebugoptionenabled NoWindows Memory Tester---------------------identifier {memdiag}device partition=\Device\HarddiskVolume6path \EFI\Microsoft\Boot\memtest.efidescription Windows Memory Diagnosticlocale en-usinherit {globalsettings}badmemoryaccess YesEMS Settings------------identifier {emssettings}bootems NoDebugger Settings-----------------identifier {dbgsettings}debugtype LocalRAM Defects-----------identifier {badmemory}Global Settings---------------identifier {globalsettings}inherit {dbgsettings} {emssettings} {badmemory}Boot Loader Settings--------------------identifier {bootloadersettings}inherit {globalsettings} {hypervisorsettings}Hypervisor Settings-------------------identifier {hypervisorsettings}hypervisordebugtype Serialhypervisordebugport 1hypervisorbaudrate 115200Resume Loader Settings----------------------identifier {resumeloadersettings}inherit {globalsettings}C:\Windows\system32>

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-04-04T06:35:03+00:00

    (1) Hmm -- you do have the Troubleshoot button. What did you see after you clicked the Troubleshoot button? That's where Reset this PC & Advanced Options should show up. Also, Recover from a Drive may be there. If Advanced Options is there, these should show up after clicking it: Uninstall Updates, System Restore, System Image Recovery, Startup Repair, Command Prompt, UEFI Firmware Settings, Startup Settings, & there may be a See More Recovery Options button. Do you have any of that?

    (2) You still had the recovery environment set up in your BCD after the clone was made, but it was loading the Recovery partition of the HDD. When we ran BCDBoot to generate a new BCD, it wiped out the code that handled the recovery environment. We have to get that code into the new BCD. The gist of it are these from your earlier pictures...

    We'll get that back in there one line at a time, if necessary. But, instead of HarddiskVolume5, we'll want ...9 (for the Recovery partition of the SSD).

    (3) Show me a new "BCDEdit /Enum All" to see whether anything has changed from the stuff we did since the last.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-04-04T05:38:40+00:00

    it doesn't reboot to a full featured recovery environment. it doesn't have the Advanced Options button. Here's the picture I took for the recovery menu.

    why doesn't it load to the full featured recovery environment? is there any problem with the cloning process?

    Was this answer helpful?

    0 comments No comments