Need Help Changing Boot Manager Screen

Hi All,
I recently rebuilt my PC and installed Windows 10. I then decided I wanted to have Windows 7 available just in case. I partitioned my primary HD and installed Windows 7. In other words, I installed Windows 7 AFTER Windows 10 for a dual-boot system. I was surprised to see the Windows 7 Boot Manager screen appear instead of the Windows 10 Boot Manager. I guess I did this backwards as it appears installing Windows 10 AFTER Windows 7 is more common.

Is there a way to edit/change/modify the boot manager to use the Windows 10 screen instead of the Windows 7 screen?

Thanks for any help!
John

alphanumeric said:

I do believe if you boot into Windows 10, and then set it as the default, you will get the Windows 10 dual boot menu.

Hi alphanumeric,
Thanks for the reply! I tried that last night and nothing changed.

John

I thought it was either one of these in a CP Admin and a reboot:

To enable the graphical boot menu:

bcdedit /set {default} bootmenupolicy standard

To disable the graphical boot menu:

bcdedit /set “{current}” bootmenupolicy legacy

cereberus said:

I think either works

Edwin said:

I thought it was either one of these in a CP Admin and a reboot:

To enable the graphical boot menu:

bcdedit /set {default} bootmenupolicy standard

To disable the graphical boot menu:

bcdedit /set “{current}” bootmenupolicy legacy

Hi cereberus, Edwin,
Thanks for the suggestions. Unfortunately, the command processed successfully but the boot manager screen did not change.

I ran it first in Windows 10 and nothing changed. I switched over to Windows 7 and ran it there but the command wouldn't process. The error was something to do with it not being recognized properly.

Oh, well; I'll keep looking for a remedy.

John

JohninNH said:

Hi cereberus, Edwin,
Thanks for the suggestions. Unfortunately, the command processed successfully but the boot manager screen did not change.

I ran it first in Windows 10 and nothing changed. I switched over to Windows 7 and ran it there but the command wouldn't process. The error was something to do with it not being recognized properly.

Oh, well; I'll keep looking for a remedy.

John

Make sure you do it from within Windows 10 and Windows 10 is your default.