Multiple and unneeded boot devices on Metro Bootloader

Page 1 of 2 12 LastLast

  1. Posts : 357
    Release (17134.471) + Insider Preview Fast Ring (18298.1)
       #1

    Multiple and unneeded boot devices on Metro Bootloader


    I didn't know which thread to post this topic in, thought this was the right one. Mods, if you think there is a more relevant thread to post this in, please make the necessary changes. Thank you. Onwards to my issue:

    I just recently decided to dual boot my UEFI-based system between Windows 10 and Windows 8.1. Upon using EasyBCD to create a bootloader that only includes Windows 10 and Windows 8.1, I get this mess:

    Multiple and unneeded boot devices on Metro Bootloader-nsl2e6w.jpg

    Can anyone help me figure out how I can get back a Metro-styled Bootloader that only includes Windows 10 and Windows 8.1? Thanks!
      My Computer


  2. Posts : 7,128
    Windows 10 Pro Insider
       #2

    Go back into EasyBCD and delete the entries you don't want.
      My Computers


  3. Posts : 357
    Release (17134.471) + Insider Preview Fast Ring (18298.1)
    Thread Starter
       #3

    Winuser said:
    Go back into EasyBCD and delete the entries you don't want.
    I tried that, sorry for not mentioning it. When I go into EasyBCD, I only see my Windows 10 and Windows 8.1 entries:

    Multiple and unneeded boot devices on Metro Bootloader-adfadsf.png

    Even with just two entries here in EasyBCD, I still get the unneeded boot entries in the Metro Bootloader seen in the OP picture. Weird!
      My Computer


  4. Posts : 18,424
    Windows 11 Pro
       #4

    Run msconfig - what does the boot tab on msconfig show?
      My Computer


  5. Posts : 357
    Release (17134.471) + Insider Preview Fast Ring (18298.1)
    Thread Starter
       #5

    NavyLCDR said:
    Run msconfig - what does the boot tab on msconfig show?
    Did that as well....it also shows shows just 2 boot entries: Windows 10 and Windows 8.1

    Multiple and unneeded boot devices on Metro Bootloader-lkjl.png
      My Computer


  6. Posts : 18,424
    Windows 11 Pro
       #6

    K. What are the results of just the bcdedit command run from an elevated ("run as administrator") command prompt? No options, just bcdedit by itself.
      My Computer


  7. Posts : 357
    Release (17134.471) + Insider Preview Fast Ring (18298.1)
    Thread Starter
       #7

    NavyLCDR said:
    K. What are the results of just the bcdedit command run from an elevated ("run as administrator") command prompt? No options, just bcdedit by itself.
    Yeah, here in bcdedit, the other unneeded entries rear their ugly heads. Looks like I gotta reformat the BCD. Please advice on this process.

    Here are the results from the simple bcdedit command:


    Windows Boot Manager
    --------------------
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\bootmgfw.efi
    description Windows Boot Manager
    locale en-US
    inherit {globalsettings}
    integrityservices Enable
    badmemoryaccess Yes
    default {current}
    resumeobject {eefdfbaf-d950-11e5-b85e-806e6f6e6963}
    displayorder {d42218bb-c58f-11e5-a5a4-86dc896b6dce}
    {d42218ae-c58f-11e5-a5a4-86dc896b6dce}
    {d42218af-c58f-11e5-a5a4-86dc896b6dce}
    {d42218b0-c58f-11e5-a5a4-86dc896b6dce}
    {d42218b1-c58f-11e5-a5a4-86dc896b6dce}
    {d42218b2-c58f-11e5-a5a4-86dc896b6dce}
    {d42218b3-c58f-11e5-a5a4-86dc896b6dce}
    {d42218b4-c58f-11e5-a5a4-86dc896b6dce}
    {d42218b5-c58f-11e5-a5a4-86dc896b6dce}
    {current}
    {d42218cc-c58f-11e5-a5a4-86dc896b6dce}
    toolsdisplayorder {memdiag}
    timeout 30


    Firmware Application (101fffff)
    -------------------------------
    identifier {d42218ae-c58f-11e5-a5a4-86dc896b6dce}
    description USB CD
    badmemoryaccess Yes
    custom:250000c2 1


    Firmware Application (101fffff)
    -------------------------------
    identifier {d42218af-c58f-11e5-a5a4-86dc896b6dce}
    description USB FDD
    badmemoryaccess Yes
    custom:250000c2 1


    Firmware Application (101fffff)
    -------------------------------
    identifier {d42218b0-c58f-11e5-a5a4-86dc896b6dce}
    description ATAPI CD0
    badmemoryaccess Yes
    custom:250000c2 1


    Firmware Application (101fffff)
    -------------------------------
    identifier {d42218b1-c58f-11e5-a5a4-86dc896b6dce}
    description ATA HDD0
    badmemoryaccess Yes
    custom:250000c2 1


    Firmware Application (101fffff)
    -------------------------------
    identifier {d42218b2-c58f-11e5-a5a4-86dc896b6dce}
    description ATA HDD1
    badmemoryaccess Yes
    custom:250000c2 1


    Firmware Application (101fffff)
    -------------------------------
    identifier {d42218b3-c58f-11e5-a5a4-86dc896b6dce}
    description ATA HDD2
    badmemoryaccess Yes
    custom:250000c2 1


    Firmware Application (101fffff)
    -------------------------------
    identifier {d42218b4-c58f-11e5-a5a4-86dc896b6dce}
    description USB HDD
    badmemoryaccess Yes
    custom:250000c2 1


    Firmware Application (101fffff)
    -------------------------------
    identifier {d42218b5-c58f-11e5-a5a4-86dc896b6dce}
    description PCI LAN
    badmemoryaccess Yes
    custom:250000c2 1


    Windows Boot Loader
    -------------------
    identifier {current}
    device partition=C:
    path \Windows\system32\winload.efi
    description Windows 10
    locale en-US
    osdevice partition=C:
    systemroot \Windows
    resumeobject {eab05afb-d9a5-11e5-b861-806e6f6e6963}
    nx OptIn
    bootmenupolicy Standard


    Windows Boot Loader
    -------------------
    identifier {d42218cc-c58f-11e5-a5a4-86dc896b6dce}
    device partition=D:
    path \Windows\system32\winload.efi
    description Windows 8.1
    locale en-US
    osdevice partition=D:
    systemroot \Windows
    resumeobject {7ecddf80-d9a5-11e5-8257-806e6f6e6963}
    nx OptIn
    bootmenupolicy Standard
      My Computer


  8. Posts : 18,424
    Windows 11 Pro
       #8

    First, do you have a drive letter assigned to the partition containing the BCD? From BCDEdit, it is volume 2 on what looks like probably the first hard drive. You'll have to have a drive letter assigned to it. Then when you run EasyBCD - go to the file menu, Select BCD, browse to the BCD store contained in the EFI\Microsoft\Boot folder. See if the big boot menu with the extra items shows up in EasyBCD there. Then edit that boot menu and save.

    Or you can run a series of BCDEdit delete commands like:

    bcdedit /delete {d42218b5-c58f-11e5-a5a4-86dc896b6dce} /cleanup

    should remove the PCI LAN entry from the menu.
      My Computer


  9. Posts : 357
    Release (17134.471) + Insider Preview Fast Ring (18298.1)
    Thread Starter
       #9

    NavyLCDR said:
    First, do you have a drive letter assigned to the partition containing the BCD? From BCDEdit, it is volume 2 on what looks like probably the first hard drive. You'll have to have a drive letter assigned to it. Then when you run EasyBCD - go to the file menu, Select BCD, browse to the BCD store contained in the EFI\Microsoft\Boot folder. See if the big boot menu with the extra items shows up in EasyBCD there. Then edit that boot menu and save.
    Firstly, how do I assign a drive letter to the partition containing the BCD? How do I locate the partition that contains the BCD. Is it the partition that contains the EFI System Partition? I am trying to assign a drive letter to the EFI system partition from the Windows 10 OS, but the option is greyed out when I right click the EFI System Partition.

    Multiple and unneeded boot devices on Metro Bootloader-screenshot-20-.png
      My Computer


  10. Posts : 18,424
    Windows 11 Pro
       #10

    It might be easier just to use the BCDEdit delete commands - you won't need a drive letter assigned for that.

    I'm not sure if diskpart commands will assign a drive letter to the EFI system partition or not:

    Diskpart
    Select Disk 0
    Select Volume 2
    Assign
    Exit
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 12:24.
Find Us




Windows 10 Forums