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
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

41 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-04-03T06:28:32+00:00

    Unfortunately, the ReagentC is disabled. Here's the copy,
    DISKPART> Select Disk 1

    Disk 1 is now the selected disk.

    DISKPART> Select Part 4

    Partition 4 is now the selected partition.

    DISKPART> Assign Letter=R

    DiskPart successfully assigned the drive letter or mount point.

    DISKPART> Exit

    Leaving DiskPart...

    C:\Windows\system32>ReagentC /SetREImage /Path R:\Recovery\WindowsRE /Target C:\Windows
    Directory set to: \?\GLOBALROOT\device\harddisk1\partition4\Recovery\WindowsRE

    REAGENTC.EXE: Operation Successful.

    C:\Windows\system32>ReagentC /EnableREAGENTC.EXE: Unable to update Boot Configuration Data.

    C:\Windows\system32>ReagentC /Info
    Windows Recovery Environment (Windows RE) and system reset configuration
    Information: 

    Windows RE status:         Disabled  
Windows RE location:  
Boot Configuration Data (BCD) identifier: 4d163c56-d6af-11eb-a988-93a3341b5547  
Recovery image location:  
Recovery image index:      0  
Custom image location:  
Custom image index:        0

    REAGENTC.EXE: Operation Successful.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-04-03T06:00:41+00:00

    You are welcome. I'm glad to hear it. Yep, EFI is HardDiskVolume6 which is on the SSD. It can't be told from that BCD which Windows partition was booted, but I'm sure you've seen elsewhere that its size is 118 GB which is the one on the SSD. But there is more work to do.

    As I suspected, BCDBoot did not set up the Recovery Environment. That means Shift+Restart will either just reboot back to Windows, or maybe it will give a stunted environment. So, let's first try to set it right with ReagentC. If that fails, we'll have to do it manually.

    DiskPart

    Select Disk 1 <<<Focus on the SSD

    Select Part 4 <<<Focus on the Recovery partition of the SSD

    Assign Letter=R <<<Give it letter R:

    Exit

    ReagentC /SetREImage /Path R:\Recovery\WindowsRE /Target C:\Windows

    ReagentC /Enable

    ReagentC /Info

    DiskPart

    Select Vol=R <<<Focus on Recovery partition

    Remove Letter=R <<<Remove the letter

    Exit

    Use Ctrl-A & Ctrl-C to copy, then paste it to us. Let's have a look.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-04-03T04:52:59+00:00

    Thank you so much! Finally. It works!

    this is the BCD:C:\Windows\system32>BCDEdit /Enum AllFirmware Boot Manager---------------------identifier {fwbootmgr}displayorder {bootmgr} {b45af706-b308-11ec-8c54-806e6f6e6963}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 ManagerWindows Boot Loader-------------------identifier {current}device partition=C:path \Windows\system32\winload.efidescription Windows 10locale en-usinherit {bootloadersettings}isolatedcontext 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}isolatedcontext 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
  4. Anonymous
    2022-04-03T04:19:39+00:00

    Yes, no problem in redoing, probably the software will erase the SSD and clone again.

    Was this answer helpful?

    0 comments