Changing the boot order

Pentagon said:

@kitpzyxmsir
The problem is the {current} entry! When you select Windows 2 and make it to default it becomes current and therefore Windows 2 jumps to the first place. When I select the Windows Recovery Environment for the next boot, the recovery becomes current and appears in the bootorder list on the first place!
bcdedit /v gives you the guid insteadt of current!

I need some interpretation. I'm not sure what you want me to do. Run bcdedit /v? I did so. Then what? Replace "current" with the actual identifier from the cmd result?, i.e.

bcdedit /displayorder {c317a689-b95e-11ee-bb05-d050998538f1} {ca77566d-b712-11ee-9d25-d050998538f1} {ca77566f-b712-11ee-9d25-d050998538f1}

The replacement from bcdedit /v is slightly different then what I got from bceditall:

c317a688-b95e-11ee-bb05-d050998538f1 (bceditall)
c317a689-b95e-11ee-bb05-d050998538f1 (bcdedit /v)

Just to check, I again ran bcdedit /enum all >>%userprofile%\Desktop\BCDEditALL.txt again, and got the same difference. Please straighten me out

It seems the op has ( at least) 3 disks and not surprisingly 3 windows boot managers all of which have the same description "windows boot manager" and at least one of the windows boot managers references a bcd store with three entries.

all the bcd entries have the same os description "Windows 10" yet the op seems to think volume 3 volume 16 etc makes sense to anybody else.

But this is the actual current boot priority order? How do I identify which ones are Volumes 3, 9, and 16

.

Change the description, as I suggested before.

In case you dont know how:









there is nothing difficult about it

Pentagon said:

once more !!!
from where did you get these numbers?
{ca77566d-b712-11ee-9d25-d050998538f1}
{ca77566f-b712-11ee-9d25-d050998538f1}

bcdedit /displayorder {c317a689-b95e-11ee-bb05-d050998538f1} {ca77566d-b712-11ee-9d25-d050998538f1} {ca77566f-b712-11ee-9d25-d050998538f1}


look at this:

You don't understand the procedure!

Do you understand what I write?
bcdedit /enum all >> %userprofile%\Desktop\BCDEditALL.txt
and upload the textfile from your desktop

I just did. Sorry, I made a mistake in transcribing from an earlier source.

From BCDEditALL.txt
----------------------------------------------------------------------

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 1
locale en-us
inherit {bootloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {c317a688-b95e-11ee-bb05-d050998538f1}
nx OptIn
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {c317a68b-b95e-11ee-bb05-d050998538f1}
device partition=D:
path \WINDOWS\system32\winload.efi
description Windows 2
locale en-us
inherit {bootloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=D:
systemroot \WINDOWS
resumeobject {c317a68a-b95e-11ee-bb05-d050998538f1}
nx OptIn
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {c317a68d-b95e-11ee-bb05-d050998538f1}
device partition=L:
path \WINDOWS\system32\winload.efi
description Windows 3
locale en-us
inherit {bootloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=L:
systemroot \WINDOWS
resumeobject {c317a68c-b95e-11ee-bb05-d050998538f1}
nx OptIn
bootmenupolicy Standard

-------------------------------------------------------------------------

According to current BCDEditALL.txt, should have been

bcdedit /displayorder {c317a689-b95e-11ee-bb05-d050998538f1} {c317a68b-b95e-11ee-bb05-d050998538f1} {c317a68d-b95e-11ee-bb05-d050998538f1}

Successful!





But I'd like to know where you got the identifier for C;\. My version of BCDEditALL.txt contains

c317a688-b95e-11ee-bb05-d050998538f1 (see above)(

yours has

c317a689-b95e-11ee-bb05-d050998538f1

Your identifier worked when running bcdedit /displayorder. Mine did not.

- - - Updated - - -

SIW2 said:

It seems the op has ( at least) 3 disks and not surprisingly 3 windows boot managers all of which have the same description "windows boot manager" and at least one of the windows boot managers references a bcd store with three entries.

all the bcd entries have the same os description "Windows 10" yet the op seems to think volume 3 volume 16 etc makes sense to anybody else.

.

Change the description, as I suggested before.

In case you dont know how:









there is nothing difficult about it

You need to re-examine that post you're referring to, which contains "none" of the suggestions your offering up now.

Secondly. the "3 windows boot managers all of which have the same description "windows boot manager" and at least one of the windows boot managers references a bcd store with three entries", please explain in detail, I have no clue what your talking about. The three volumes on the boot recovery page were created and 'peculiarly" named by the system when I first connected the other boot disks. Aside from that, I had nothing to do with their creation, long, long, ago.

BTW, apologies to the rest following this thread. Sometimes the tech terms/concepts are beyond me. I'm jumping back and forth between source material, trying to figure it out on the fly. That's why I ask so many "dumb", perhaps redundant questions. Occasionally I make mistakes.

Changing the boot order



full shutdown and restart might be needed for bios to reflect the changes



Those are two different bootmanagers (bootmgfw.efi ) on two different disks. Each references a different bcd store.

SIW2 said:

Changing the boot order



full shutdown and restart might be needed for bios to reflect the changes



Those are two different bootmanagers (bootmgfw.efi ) on two different disks. Each references a different bcd store.

I appreciate you're input. I need more info please. What are you trying to tell me?

Yes, there is a Seagate hard drive, formerly known as Volume 16. Are you saying that last image illustrates it has a bios of it's own? That it can be accessed, with settings that can be manipulated? Just a wild guess. I have no clue..

SIW2 said:

No. It looks like each of the 3 disks has an esp partition with a boot manager and a bcd store.

Bcd commands, examples of which I posted in the screenshot, can be used to change the description of each boot manager that bios displays.

Please tell me more about this Bcd command you posted. Since I mentioned I was unsure, and having difficulty having difficulty precisely identifying each boot manager in the bios list, are you saying we can change those descriptions to make them easily distinguishable and identifiable?

If so, please offer details.