Solved Restoring the Windows GUI boot menu again if legacy text one appears. (fixed)

jimbo45 · Jan 14, 2024

Hi folks
After creating a winpe.vhdx and a windows 22 server vhdx I lost the blue boot windows GUI and just got the old legacy black text one.

The easiest way to fix this is via (as admin) bcdedit.

Simply run bcdedit /set {default} bootmenupolicy standard where {default} is the system you want as default (or in whatever id it is -- you can see that by just running bcdedit without any parameters - just lists them all if you have serveral systems.

Of course if you already have the newer blue boot menu and don't like it you can revert by typing

bcdedit /set {default} bootmenupolicy legacy - but not sure why you'd want to do that -- people's choice I suppose.

Cheers
jimbo

cereberus · Jan 14, 2024

jimbo45 said:
Hi folks
After creating a winpe.vhdx and a windows 22 server vhdx I lost the blue boot windows GUI and just got the old legacy black text one.

The easiest way to fix this is via (as admin) bcdedit.

Simply run bcdedit /set {default} bootmenupolicy standard where {default} is the system you want as default (or in whatever id it is -- you can see that by just running bcdedit without any parameters - just lists them all if you have serveral systems.

Of course if you already have the newer blue boot menu and don't like it you can revert by typing

bcdedit /set {default} bootmenupolicy legacy - but not sure why you'd want to do that -- people's choice I suppose.

Cheers
jimbo

I recommend you use Code tags when suggesting such commands (</> icon in menu)

Code:

bcdedit /set {default} bootmenupolicy standard

Code:

bcdedit /set {default} bootmenupolicy legacy

Main reason some prefer the legacy menu is it can be quite a bit faster.

trumpy81 · Jan 14, 2024

I use the legacy boot menu since my BIOS enter screen is mostly black, except for the ROG logo and it blends in nicely. It is also a little faster, but not by much.

If I need to get to the recovery menu I just need to press F8 at the boot menu.

GammaP · Jan 14, 2024

Good info. I will give legacy option a try. Thanks!

-Gamma

cereberus · Jan 14, 2024

GammaP said:
Good info. I will give legacy option a try. Thanks!
-Gamma

It is much easier to select option using graphical interface - it is too easy to select wrong option on legacy bios, particularly for people with reduce dexterity or "fat fingers". Also can take several clicks.

Also, some bioses have a bug where legacy bios only shows in low resolution if secure boot is enabled.

jimbo45 · Jan 14, 2024

Hi folks

especially if you have a load of different OS'es -- the description which you can set (also doable with legacy boot) is much clearer IMO with white / blue GUI tham with black / grey text in the legacy menu.

I don't think boot time length makes any even noticeable difference on decent (and even quite old) equipment either. Also you can get longer descriptions visible on the screen.

But it's people's choice and at least both menu types are still available.

(And yes I still use Win 10 from time to time).

cheers
jimbo

GammaP · Jan 14, 2024

jimbo45 said:
Hi folks

especially if you have a load of different OS'es -- the description which you can set (also doable with legacy boot) is much clearer IMO with white / blue GUI tham with black / grey text in the legacy menu.

I don't think boot time length makes any even noticeable difference on decent (and even quite old) equipment either. Also you can get longer descriptions visible on the screen.

But it's people's choice and at least both menu types are still available.
View attachment 84061
(And yes I still use Win 10 from time to time).

cheers
jimbo

Wow! You are a VHD rider. That's me too!

-Gamma

zamar21 · May 24, 2024

jimbo45 said:
Simply run bcdedit /set {default} bootmenupolicy standard where {default} is the system you want as default (or in whatever id it is -- you can see that by just running bcdedit without any parameters - just lists them all if you have serveral systems.

As detailed in this thread, the above command may be remotely relevant to the task stated, but in many scenarios will not produce desired change from Legacy to Modern Boot Menu on a multiboot system with Windows 11 as primary OS. It remains a mystery, how to accomplish that on a multiboot system with several partitions per drive upon OS upgrade or reinstall. Most likely, certain Bootloader parameters set by bcdedit can switch the menu.

I wonder if someone researched the issue deep enough, and whether there is some Tutorial written to do that?

Winuser · May 26, 2024

I find that EasyBCD 2.4 works the best for me.

zamar21 · May 26, 2024

I tried EasyBCD 2.4 to revert to Modern Boot Menu or rebuild boot records, but no change in appearance. Adding new OS installs to Boot Menu in EasyBCD resulted in switch to Legacy Boot Menu no matter what options or BCDEdit commands & parameters I tried. The only reliable way I found to switch from Legacy to Modern Boot Menu on a Multiboot system with several disks & partitions and Windows 11 Boot Manager as primary:

1. Launch Windows version, which Boot Manager you want to use as primary, observe Legacy Boot Menu at boot
2. Reboot to Windows Recovery - Advanced Options - Command Prompt, or launch & reboot from Windows Install Disk choosing its Repair Windows - Command Prompt option
3. Run Diskpart - List Volume to get a feel of accessible partitions and their drive letters, then Exit
4. Run bootrec /RebuildBcd to erase existing boot records and auto add available Windows installations to a new boot menu
5. Run BCDEdit to see updated BCD OS records, or BCDEdit /v /enum all to see all boot records, including hidden in Menu
6. Reboot, make sure your motherboard BIOS or UEFI settings are configured to start from the same drive as before, if several are connected.

Winuser · May 26, 2024

zamar21 said:
I tried EasyBCD 2.4 to revert to Modern Boot Menu or rebuild boot records, but no change. Adding new OS installs to Boot Menu in EasyBCD resulted in switch to Legacy Boot Menu no matter what options or BCDEdit commands & parameters I tried. The only reliable way I found to switch from Legacy to Modern Boot Menu on a Multiboot system with several disks & partitions and Windows 11 Boot Manager as primary:

1. Reboot to Windows Recovery - Advanced Options - Command Prompt, or launch Windows Install Disk choosing Repair Windows - Command Prompt
2. Run Diskpart - List Volume to get a feel of accessible partitions and their drive letters
3. Run bootrec /RebuildBcd to erase existing records and auto add available Windows installations to boot menu
4. Run BCDEdit to see updated BCD store, or BCDEdit /v /enum all to see all records, including hidden
5. Reboot, make sure your motherboard BIOS or UEFI settings are configured to start from the same drive as before, if several are connected.

When you made the changes did you save them and wait until EasyBCD said the changes were saved? I've never had a problem using EasyBCD to make any needed changes to my boot menu.

zamar21 · May 26, 2024

Winuser said:
When you made the changes did you save them and wait

I took part in the debate with the dev, when EasyBCD update to V2.4 was developed years ago, and familiar with the issue. I suspect that inherited OS globalsettings and certain hidden bootloadersettings affect the outcome. EasyBCD 2.4 is somewhat obsolete to cover all grounds. If it fails for some to switch from Legacy to Modern Boot Menu, run bootrec from Windows Recovery or Install Disk. There might be alternative ways to achieve that with BCDEdit requiring in-depth knowledge of various boot affecting factors. Bootmenupolicy alone doesn't cut it.

Winuser · May 26, 2024

zamar21 said:
I took part in the debate with the dev, when EasyBCD update to V2.4 was developed years ago, and familiar with the issue. I suspect that inherited OS globalsettings and certain hidden bootloadersettings affect the outcome. EasyBCD 2.4 is somewhat obsolete to cover all grounds. If it fails for some to switch from Legacy to Modern Boot Menu, run bootrec from Windows Recovery or Install Disk. There might be alternative ways to achieve that with BCDEdit requiring in-depth knowledge of various boot affecting factors. Bootmenupolicy alone doesn't cut it.

I don't know what changes you have made that would make EasyBCD not work. I've been using EayBCD for years on just about every computer I have owned and it has always worked for me. I'm at that point in my life that I'm going to do things the easy way whenever possible. I no longer want to learn or remember things such as command lines.