Legacy Boot Menu

gnulab

Member
Hi,

I've searched, not exhaustively, and all posts involve dual booting Windows 7 and Windows 10, thus the appearance of Legacy Boot Menu instead of the Metro Style boot menu.

My setup is a little bit different. I dual boot Windows 10, both windows 10. 1 for normal use and 1 for gaming purpose.

So, it is a new DELL laptop shipped with 1 installation of Windows.
I downloaded a new copy of Windows 10 from microsoft website, installed it and boom. Legacy boot menu.

Then this is what I did.
A
Secure Boot = on
install EasyBCD
tick Metro style
reboot
blank screen
did boot to default OS
turns out the blank screen is the boot menu step.

B
Secure Boot = off
edit timeout from 5 sec to 6 sec
sort of causing EasyBCD to write something to BCD store
reboot
still blank screen

C
Secure Boot = off
untick Metro style from EasyBCD
Legacy boot menu appears

D
Secure Boot = on
Metro Style = unticked
system boots still Legacy type

Oh well...
 
Can you post a screenshot of your Device Management and the contents of EasyBCD's "view settings" (detailed mode)
 
Can you post a screenshot of your Device Management and the contents of EasyBCD's "view settings" (detailed mode)

Hi Terry,


Ok, I'm lost about the DEVICE MANAGEMENT part. Where can I access it?

However, here is the contents of EasyBCD's view settings.

Code:
Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-US
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default                 {b736ae8d-1ddc-11eb-8aaf-9cebe8de92e8}
resumeobject            {b736ae8c-1ddc-11eb-8aaf-9cebe8de92e8}
displayorder            {743f52d7-1de0-11eb-a8ba-806e6f6e6963}
                        {b736ae8d-1ddc-11eb-8aaf-9cebe8de92e8}
                        {803afa74-4955-11eb-b440-c9a48acc6be8}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 5
displaybootmenu         Yes

Firmware Application (101fffff)
-------------------------------
identifier              {743f52d7-1de0-11eb-a8ba-806e6f6e6963}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Boot\BootX64.efi
description             UEFI RST PC SN530 NVMe WDC 512GB 2036C7808823
custom:250000c2         0

Windows Boot Loader
-------------------
identifier              {b736ae8d-1ddc-11eb-8aaf-9cebe8de92e8}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 10N
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence        {da49fe4c-1de5-11eb-833c-9cebe8de92e8}
displaymessageoverride  Recovery
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {b736ae8c-1ddc-11eb-8aaf-9cebe8de92e8}
nx                      OptIn
bootmenupolicy          Standard

Windows Boot Loader
-------------------
identifier              {803afa74-4955-11eb-b440-c9a48acc6be8}
device                  partition=E:
path                    \Windows\system32\winload.efi
description             Windows 10G
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence        {803afa75-4955-11eb-b440-c9a48acc6be8}
displaymessageoverride  Recovery
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=E:
systemroot              \Windows
resumeobject            {803afa73-4955-11eb-b440-c9a48acc6be8}
nx                      OptIn
bootmenupolicy          Standard
 
Sorry, my finger trouble - should have said Disk Management.
Just type it into the W10 search box and you'll find it (Create and Format..)
It's the Disk snap-in of the Computer Management Program.
(Or type diskmgmt.msc into powershell or search (or ask Cortana if you've got that turned on))
Make sure you expand the status column so that all the flags are visible.
 
Hi,

Here's the request. I installed MiniTools Partition Wizard too and took a screenshot which seems to be in more detail.2021-01-19_180239.png2021-01-19_180302.png
 
You edited out the bit I was actually looking for
Capture.JPG
but from what you did post, the only major difference I can see which might have an influence is the fact that your second OS and your virtual storage (Page) are both encrypted.
On my PC I can flip between Metro and legacy menus with that simple tick (or lack of). (I actually prefer and use legacy)
The only situation I know of which forces legacy boot regardless is having W7 designated "default".
Many, many years ago, the author remarked that the menu choice is not just a simple binary fork in the bootmgr code, but actually involves several different modules in the boot process.
It seems that having an older OS version as default disrupts that internal decision, so maybe having an encrypted OS does likewise.
I'm just speculating,
If the author looks in, he might be able to give a definitive reason.
 
Ok, just decrypted all my volumes. Here is the updated status.
2021-01-20_190648.png

MiniTools PM also shown the volumes are no longer BitLock-ed. But it still shows black screen, same as before. Oh well, as long as I can boot up. I can live with it.

Thanks for the reply Terry.

Cheers.

2021-01-20_190716.png
 
That's me finished then. Everything looks like it should be as simple to switch for you as it is for me.
Forgive me for stating the bleedin' obvious, but after 13 years of answering questions here, nothing surprises me any more, and it's impossible to know the expertise of each new stranger who turns up, so... you did click "save" after altering the Metro status ?
 
Back
Top