Windows 10: 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:





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!

:)

 

Windows 10 system files

I have resolved the issue by removing non system drives, ensuring both system and backup drives would boot either via Metro bootloader or independently. I reconnected the non system drives and was able to format as required.

Regards,

Steve

 

Bootloader for Thumbdrive ?

Hi, I want to put multiple boot discs for multiple computers on one thumb drive. I assume I need to create a multiple bootloader on the thumbdrive so I can select which boot loader I want for each computer when the computer boots into the thumbdrive, correct
?

 

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:





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!

 

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

 

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:

 

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.

 

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.

 

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

 

Thanks for the continued patience. I have managed to assign a drive letter to the EFI partition, however when I try to access it, I am presented with a permission denied request (seems reasonable):





It turns out the EFI partition was volume 4, not volume 2 as I assumed. Anyways, I was able to assign the partition.

I tried to get to the security tab, but because this is a special partition, it isn't present in the drive properties window:





What should I do now? Also, how would I use the BCDedit delete commands as you mentioned?

EDIT: See below, following up on previous advice.

 

Upon your 1st point (navigating to EFI\Microsoft\Boot folder): the big boot menu with extra items doesn't show up here.

I am going through your second piece of advice now (running bcdedit /delete commands on the unneeded entries).

Thank you

 

Looks like it worked! Came across this nasty message upon reboot, but it fixed itself and displayed the only 2 boot entries that I was interested in seeing:





Why did this happen when I used EasyBCD? If you know, I would love to know the answer.