Boot EasyBCD on D:\ ???

D

darth2602

Member
Hello

I have a problem with EasyBCD....

I had a pc with a hard disk on which windows 7 was installed.

I installed an SSD, which I set up as bootable disk 1, then I installed windwows 10 pro on it.
I created a multiboot with easy bcd;




There are 2 entries in the Windows boot loader

Default input: Win 10
Countdown: 5 second(s)
EasyBCD boot disk: D:\

Input #1
Name : Win 10
BCD identifier: {current}
Disc : C:\
Path to boot loader : \Windows\system32\winload.exe

Input #2
Name : Win 7
BCD identifier: {8be6587d-323f-11ee-af3c-0021910b7cca}
Record : D:\
Path to boot loader : \Windows\system32\winload.exe




what I'm having trouble with is this line: "EasyBCD boot disk: D:\"
this means that the menu is on my D: hard drive and not on my C: SSD ????
if I remove the hard disk I won't be able to boot on my SSD, windows 10 ????

If that's the case, how can I correct it?

For now my solution would be to boot on the windows 10 insatllation key
and choose "repair".....

(ou Easy Recovery Essentials for windows 10 pro ?)
 
EasyBCD boot disk shows in overview mode if you've previously used something like XP or Linux which EasyBCD had to chain. That tells you where those EasyBCD files were created.
View settings in detailed (debug mode) will tell you the boot partition.
Or simply look at the Disk Management flags

"boot" = "this is the system you're running"
"system" = "this is where I found the boot files for the currently running system"
"active" (on the first HDD in the BIOS boot sequence) = "this is where I started the search for the boot files"
"active" (on subsequent HDDs in the BIOS boot sequence) ="this is where I will look if I don't find something in the MBR on the first HDD"
 
I think just found the solution .... (I moved the BCD from D: to C:smile:

on Save/Repair BCD ..... > Administration options > change Boot Disk, > C

Correct ?
 
now i have ;


There are a total of 2 entries listed in the bootloader.

Default: Window 10 64bits Pro
Timeout: 5 seconds
EasyBCD Boot Device: C:\

Entry #1
Name: Window 10 64bits Pro
BCD ID: {current}
Drive: C:\
Bootloader Path: \Windows\system32\winload.exe

Entry #2
Name: Windows 7 32bits Int
BCD ID: {8be6587d-323f-11ee-af3c-0021910b7cca}
Drive: D:\
Bootloader Path: \Windows\system32\winload.exe
 
Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device boot
description Windows Boot Manager
locale fr-FR
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {6fe69f26-31f3-11ee-b498-afdde181c176}
resumeobject {6fe69f25-31f3-11ee-b498-afdde181c176}
displayorder {6fe69f26-31f3-11ee-b498-afdde181c176}
{8be6587d-323f-11ee-af3c-0021910b7cca}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 5

Windows Boot Loader
-------------------
identifier {6fe69f26-31f3-11ee-b498-afdde181c176}
device partition=C:
path \Windows\system32\winload.exe
description Window 10 64bits Pro
locale fr-FR
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {6fe69f27-31f3-11ee-b498-afdde181c176}
displaymessageoverride Recovery
recoveryenabled Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {6fe69f25-31f3-11ee-b498-afdde181c176}
nx OptIn
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {8be6587d-323f-11ee-af3c-0021910b7cca}
device partition=D:
path \Windows\system32\winload.exe
description Windows 7 32bits Int
locale fr-FR
osdevice partition=D:
systemroot \Windows
resumeobject {046e8685-3240-11ee-bef0-806e6f6e6963}
 
Now I think that if I delete :


Entry #2
Name: Windows 7 32bits Int
BCD ID: {8be6587d-323f-11ee-af3c-0021910b7cca}
Drive: D:\
Bootloader Path: \Windows\system32\winload.exe


and set the delay to 0 I could remove the D . disc;
 
Delete the W7 entry and leave a positive numer in the timeout. It won't matter because bootmgr won't present a menu when there's no choice to be made.
Setting timeout to zero is not a good idea. At some point in the future it might bite you in the ass. Always as well to leave yourself an opportunity to stop the clock during boot in the future. As I said, there won't be any delay even if that number is set to 1000 as long as bootmgr defaults to a single choice of OS without the need for a menu.
 
Back
Top