[SOLVED] Help! So many glitchy Windows Boot Managers in ASUS BIOS that will freeze and crash BIOS if I move them. Screenshot attached.

[tgimagine]

Thank you for reading! I have a ASUS SABERTOOTH Z97 MARK1 LGA 1150 Intel Z97 and in the "Boot Order" section of the BIOS, there are listed I believe 14 (fourteen) items that say "Windosw Boot Manager". This is very glitchy, and if I touch one, the whole system freezes and I have to hard restart my PC.

Here is a screenshot of my issue:

https://imgur.com/a/NyAu5Jd

View: https://imgur.com/a/NyAu5Jd


I am trying to touch/move them, because currently my #1 boot drive in BIOS is NOT the drive that I want to boot to. So I literally will have to go into bios and custom boot every single time to get into my OS.

I have 4 Logical drives on my computer:

Volume 1: A raid 0 array with 2 SDDs (This is what I want to boot from, it contains Windows OS)

Volume 2: A raid 5 array with 3 HDDs (Just storage, nothing bootable)

Volume 3: HDD with Linux Distro installed to it (This is #1 in the boot order, but I want Windows to boot, but I cannot move anything around)

Volume 4: External HDD (no bootable partitions)

I would rather not reset BIOS to factory settings, as I believe that this would not be the solution. I will do this eventually, but I would rather it be a last resort. The BIOS cannot be making up these boot managers. It is seeing them and bringing them in from somewhere. Again, if you try to boot, or change their order, or click on them at all the system will freeze/crash. Any help is so much appreciated!

 

[Colif]

with UEFI if you've installed say some Linux versions and you don't want them any more you might still see these at boot if you go into your BIOS boot menu.

Easy way to fix these i.e remove them

1. Go into command mode (run as administrator)
2. type bcdedit /enum firmware (space between enum and firmware

3)Now you'll see a list

4) To delete entries you don't want
type bcdedit delete identifier where the identifier is shown in your list. Include the sigiddly braces { }

Easy -- job done

If you are worried about this just simply backup the EFI partition with Macrium - you don't need to back up the rest of the system. If boot fails because you deleted wrong entry simply restore the EFI partition (it's only 100MB or so - takes seconds with macrium and works -- I deliberately hosed up an entry to test this --restored partition and system booted fine).

https://www.tenforums.com/installat...unwanted-boot-entries-bios-solved-easily.html

 

[tgimagine]

https://www.tenforums.com/installat...unwanted-boot-entries-bios-solved-easily.html

Would you happen to have any insights on which ones I would need to remove? Or better yet, which ones that I do not need to remove? I am a little out of my element here. I understand the Windows Boot Manager, but not the "Firmware Application (101fffff)". These seem to not have any descriptive information, though a handful do. These do not have the DESCRIPTION of "Windows Boot Manager", So I am wondering if they are something different entirely? I also only have one CD/DVD drive, so that is a bit of a head scratcher. Any further assistance would be very helpful!

Microsoft Windows [Version 10.0.18363.1198]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>bcdedit /enum firmware

Firmware Boot Manager
---------------------
identifier              {fwbootmgr}
displayorder            {579b1da1-d655-11e8-82dd-806e6f6e6963}
                        {b066cadb-b67e-11e5-8273-806e6f6e6963}
                        {bootmgr}
                        {bootmgr}
                        {bootmgr}
                        {bootmgr}
                        {bootmgr}
                        {bootmgr}
                        {bootmgr}
                        {bootmgr}
                        {bootmgr}
                        {bootmgr}
                        {bootmgr}
                        {bootmgr}
                        {bootmgr}
                        {bootmgr}
                        {bootmgr}
                        {bootmgr}
                        {bcdd8a91-06fa-11eb-8310-806e6f6e6963}
                        {58d79d57-25a9-11eb-8312-806e6f6e6963}
timeout                 1

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume5
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {de3404ee-e732-11e9-88d2-a548651d699f}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Firmware Application (101fffff)
-------------------------------
identifier              {22c4809e-b1f2-11e5-8270-806e6f6e6963}
description             Hard Drive

Firmware Application (101fffff)
-------------------------------
identifier              {22c480a0-b1f2-11e5-8270-806e6f6e6963}
description             Hard Drive

Firmware Application (101fffff)
-------------------------------
identifier              {2c00238a-b240-11e5-8271-806e6f6e6963}
description             CD/DVD Drive

Firmware Application (101fffff)
-------------------------------
identifier              {579b1da1-d655-11e8-82dd-806e6f6e6963}
description             CD/DVD Drive

Firmware Application (101fffff)
-------------------------------
identifier              {58d79d57-25a9-11eb-8312-806e6f6e6963}
device                  partition=H:
description             UEFI: (NTFS) TOSHIBA External USB 3.0

Firmware Application (101fffff)
-------------------------------
identifier              {738930b0-b240-11e5-8271-10c37b964e74}
description             CD/DVD Drive

Firmware Application (101fffff)
-------------------------------
identifier              {738930b3-b240-11e5-8271-10c37b964e74}
description             CD/DVD Drive

Firmware Application (101fffff)
-------------------------------
identifier              {738930b5-b240-11e5-8271-10c37b964e74}
description             Hard Drive

Firmware Application (101fffff)
-------------------------------
identifier              {a6d75e2d-49f0-11e5-a4a2-c2b1d51d35c7}
description             CD/DVD Drive

Firmware Application (101fffff)
-------------------------------
identifier              {a6d75e2f-49f0-11e5-a4a2-c2b1d51d35c7}
description             Hard Drive

Firmware Application (101fffff)
-------------------------------
identifier              {b066cad5-b67e-11e5-8273-806e6f6e6963}
description             CD/DVD Drive

Firmware Application (101fffff)
-------------------------------
identifier              {b066cad6-b67e-11e5-8273-806e6f6e6963}
description             Hard Drive

Firmware Application (101fffff)
-------------------------------
identifier              {b066cad7-b67e-11e5-8273-806e6f6e6963}
description             CD/DVD Drive

Firmware Application (101fffff)
-------------------------------
identifier              {b066cad8-b67e-11e5-8273-806e6f6e6963}
description             Hard Drive

Firmware Application (101fffff)
-------------------------------
identifier              {b066cad9-b67e-11e5-8273-806e6f6e6963}
description             Hard Drive

Firmware Application (101fffff)
-------------------------------
identifier              {b066cadb-b67e-11e5-8273-806e6f6e6963}
description             Hard Drive

Firmware Application (101fffff)
-------------------------------
identifier              {bcdd8a91-06fa-11eb-8310-806e6f6e6963}
device                  partition=Z:
description             UEFI: (NTFS) WD My Book 111A

Firmware Application (101fffff)
-------------------------------
identifier              {ce23bb99-b1d4-11e5-826f-10c37b964e74}
description             CD/DVD Drive

Firmware Application (101fffff)
-------------------------------
identifier              {ce23bb9a-b1d4-11e5-826f-10c37b964e74}
description             Hard Drive

C:\WINDOWS\system32>

 

[Colif]

I think @SkyNetRising might be able to help

I think the identifier is the GUID of the drive the entry is on
22c4809e-b1f2-11e5-8270-806e6f6e6963
738930b0-b240-11e5-8271-10c37b964e74
a6d75e2d-49f0-11e5-a4a2-c2b1d51d35c7

Every GPT drive on earth has its own number.

to identify the GUID of the hdd that has windows on it,
open command prompt (admin)
type diskpart and press enter
type list disk and press enter
note the disk number of C drive
choose select disk X (X being number of drive you want)
type uniqueid Disk and press enter - this should show one of the 3 numbers. Can you tell us which?


You have at least 3 Boot drives in here, I just can't tell which is which. 4 including one for a WD My Book

Can you show us a screenshot of Disk management showing all drives and columns?

these are boot entries, for different partitions, so the wbm is going to show all bootable devices linked to that install at any time, that includes the dvd drive it seems. One entry seems to list it twice, I don't know why really


I will see what others suggest about rest.

most mods are suggesting you just reset bios and start again. might be faster and less messy and can probably run BCD afterwards to fix the boot info for windows, not so sure about the Linux install.

 

[tgimagine]

Can you show us a screenshot of Disk management showing all drives and columns?

Here it is:

https://imgur.com/a/1OS5NVF

View: https://imgur.com/a/1OS5NVF

 

[Colif]

{bcdd8a91-06fa-11eb-8310-806e6f6e6963
is an external HDD not currently plugged in, it could be removed

Actual unique numbers
22c4809e-b1f2-11e5-8270-806e6f6e6963 – HDD
2c00238a-b240-11e5-8271-806e6f6e6963 – CD
579b1da1-d655-11e8-82dd-806e6f6e6963 – CD
58d79d57-25a9-11eb-8312-806e6f6e6963 – Toshiba USB
738930b0-b240-11e5-8271-10c37b964e74 – CD
a6d75e2d-49f0-11e5-a4a2-c2b1d51d35c7 – CD
b066cad6-b67e-11e5-8273-806e6f6e6963 – HDD - there are 6 entries listed for this identifier
ce23bb99-b1d4-11e5-826f-10c37b964e74 - HDD

need to know which of the hdd is which.
I don't know linux, need to find out what the GUID of that drive is too if you don't want to lose it.

Some of them are just for a CD drive, you could probably remove those identifiers and it will shrink list

 

[Colif]

i think 8270-806e6f6e6963 is likely linked to windows, as its most prevalent number above. it lists 2 hdd so not sure about it all.
this is probably the linux install - 10c37b964e74 as its only got 1 link to a hdd and cd drive

I am learning this as I go along too. I was curious why it showed so many.

I have to go soon as its 5am here.

 

[tgimagine]

i think 8270-806e6f6e6963 is likely linked to windows, as its most prevalent number above. it lists 2 hdd so not sure about it all.
this is probably the linux install - 10c37b964e74 as its only got 1 link to a hdd and cd drive

I am learning this as I go along too. I was curious why it showed so many.

I have to go soon as its 5am here.

I have just removed everything that was listed under firmware, and this resolved this issue. There was still an option for Windows Boot Manager in BIOS and that started OS right up. I was able to move it to #1 without freezing, and all is well. Thank you so much for all of your help. You really helped me out today!! Thank you!

 

[Colif]

glad it was that easy