Distinguishing Two Windows Installs?

[saintpatr]

Great concept, but I don't think the program is effective at distinguishing two Windows instalations. I've tried all options with no changes to the boot order. I am using the built in boot manager for Windows 10. Any idea of where I could be going wrong?

[pgaskin]

I'm not sure how Windows manages multiple installations (I rarely use my Windows dual-boot). Having the same name shouldn't be an issue since bootnext uses the ID, so I guess it might not be a proper EFI boot entry. Can I see the output of bcdedit /enum all?

[saintpatr]

Suure, here it is;

C:\Windows\system32>bcdedit /enum

Windows Boot Manager

identifier {bootmgr} device partition=\Device\HarddiskVolume3 path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI description Windows Boot Manager locale en-GB inherit {globalsettings} default {current} resumeobject {cb6e5a41-7461-11eb-a963-aa8011311bee} displayorder {current} {cb6e5a42-7461-11eb-a963-aa8011311bee} toolsdisplayorder {memdiag} timeout 1

Windows Boot Loader

identifier {current} device partition=C: path \Windows\system32\winload.efi description Windows Production locale en-GB inherit {bootloadersettings} recoverysequence {cb6e5a47-7461-11eb-a963-aa8011311bee} displaymessageoverride Recovery recoveryenabled Yes isolatedcontext Yes allowedinmemorysettings 0x15000075 osdevice partition=C: systemroot \Windows resumeobject {cb6e5a45-7461-11eb-a963-aa8011311bee} nx OptIn bootmenupolicy Standard

Windows Boot Loader

identifier {cb6e5a42-7461-11eb-a963-aa8011311bee} device partition=E: path \Windows\system32\winload.efi description Windows Play locale en-GB inherit {bootloadersettings} recoverysequence {cb6e5a43-7461-11eb-a963-aa8011311bee} displaymessageoverride Recovery recoveryenabled Yes isolatedcontext Yes allowedinmemorysettings 0x15000075 osdevice partition=E: systemroot \Windows resumeobject {cb6e5a41-7461-11eb-a963-aa8011311bee} nx OptIn bootmenupolicy Standard

[pgaskin]

Do both show up separately in the hard disk boot order options in the firmware settings?

[saintpatr]

There are certainly two options in windows boot manager but I'll check in Firmware when I get home.

[saintpatr]

There is only one option in the Bios- I assume there's only one version of windows bootloader that manages both systems.

[pgaskin]

Go to the advanced tab, then find the options for each individual hard drive. You should see the additional entries there if they exist.

[saintpatr]

There were no additional entries.

[pgaskin]

In that case, bootnext won't be able to choose between the options unless I implement the ability to manipulate the BCD (similar to #2, but for Windows).

[NP-chaonay]

pgaskin

at least you could put ID with it so power user can get to know what ID should use, however I think it should only display 1, as Windows Boot Loader is not meant to install as EFI boot entry, but only for Windows Boot Manager (bcdboot/bootmgfw.efi) internal usage.

Does this program is directly get data from EFI bootmgr? if get through Windows API, then maybe it is technical problem on that API usage. If I not wrong, using Linux binary 'efibootmgr' will list only 1 Windows Boot Manager.