hello, i have the MS boot manager configured to boot either win7, win10 or grub4dos even though BCD is set to "bootmenupolicy Legacy", it still sometimes starts in graphical mode and then as you know it takes an annoying extra restart whenever i want to launch something else than win10 is anyone else seeing this, and is a fix/work-around known ? i am ready to install grub2 to MBR if i have to, but that would introduce a small delay whenever booting to win10 (which i pick most of the time)
hi rpo, thanks for your reply. I do not remember typing that explicitly but it seems to be active (see below the full output of bcdedit) Windows Boot Manager -------------------- identifier {bootmgr} device partition=C: description Windows Boot Manager locale en-GB inherit {globalsettings} default {current} resumeobject {903a8a3e-9c0e-11e6-b229-00190f26c9e4} displayorder {903a8a39-9c0e-11e6-b229-00190f26c9e4} {current} {903a8a3d-9c0e-11e6-b229-00190f26c9e4} toolsdisplayorder {memdiag} timeout 3 displaybootmenu Yes Windows Boot Loader ------------------- identifier {903a8a39-9c0e-11e6-b229-00190f26c9e4} device partition=C: path \Windows\system32\winload.exe description Windows 7 locale en-US inherit {bootloadersettings} recoverysequence {903a8a3a-9c0e-11e6-b229-00190f26c9e4} recoveryenabled Yes osdevice partition=C: systemroot \Windows resumeobject {903a8a38-9c0e-11e6-b229-00190f26c9e4} nx OptIn bootmenupolicy Legacy Windows Boot Loader ------------------- identifier {current} device partition=D: path \Windows\system32\winload.exe description Windows 10 locale en-GB inherit {bootloadersettings} recoverysequence {903a8a40-9c0e-11e6-b229-00190f26c9e4} recoveryenabled Yes allowedinmemorysettings 0x15000075 osdevice partition=D: systemroot \Windows resumeobject {903a8a3e-9c0e-11e6-b229-00190f26c9e4} nx OptIn bootmenupolicy Legacy bootstatuspolicy IgnoreShutdownFailures Real-mode Boot Sector --------------------- identifier {903a8a3d-9c0e-11e6-b229-00190f26c9e4} device partition=C: path \NST\NeoGrub.mbr description NeoGrub