Quantcast
Channel: Active questions tagged windows - Super User
Viewing all articles
Browse latest Browse all 9663

Two Windows Boot Manager entries in BIOS boot section

$
0
0

I have in dual boot Arch Linux and Windows 11.

In my BIOS or when, at boot, I press key for boot selection, I have two Windows Boot Manager despite I have only one Windows installation.

If I run in Windows CMD the command bcdedit /enum firmware, I get:

Firmware Boot Manager---------------------identifier              {fwbootmgr}displayorder            {ddb06b1f-6133-11ee-a5c3-806e6f6e6963}                        {bootmgr}                        {db70feaf-6179-11ee-a5c8-806e6f6e6963}timeout                 1Windows Boot Manager--------------------identifier              {bootmgr}device                  partition=\Device\HarddiskVolume4path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFIdescription             Windows Boot Managerlocale                  en-USdefault                 {current}resumeobject            {3d596ea5-6131-11ee-a5c2-806e6f6e6963}displayorder            {current}timeout                 30Firmware Application (101fffff)-------------------------------identifier              {db70feaf-6179-11ee-a5c8-806e6f6e6963}device                  partition=C:path                    \EFI\Microsoft\Boot\bootmgfw.efidescription             Windows Boot ManagerFirmware Application (101fffff)-------------------------------identifier              {ddb06b1f-6133-11ee-a5c3-806e6f6e6963}device                  partition=\Device\HarddiskVolume4path                    \EFI\GRUB\GRUBX64.EFIdescription             GRUB

and, on System Configuration of Windows, under Boot tab, I have only one entry:screen

When I run efibootmgr on Linux, I get:

BootCurrent: 0001Timeout: 1 secondsBootOrder: 0000,0001,0002Boot0000* Windows Boot Manager  HD(1,GPT,71e827d6-2276-46f2-816b-881e51c53d30,0x800,0x96000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d0000000c000100000010000000040000007fff0400Boot0001* GRUB  HD(1,GPT,71e827d6-2276-46f2-816b-881e51c53d30,0x800,0x96000)/File(\EFI\GRUB\GRUBX64.EFI)Boot0002* Windows Boot Manager  HD(2,GPT,4ae5c801-ebf3-be4c-a9b3-cab7a69f40a8,0xd6800,0x1da5a7f9)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)0000424f

The bad one is Boot0002 (that is not working when boot to it). If I remove it by sudo efibootmgr -b 2 --delete-bootnum, and I re-run efibootmgr, it actually disappears, but when I reboot, it appears again, and indeed that entry is still in BIOS. It is like it is generated at reboot when I delete it.

How can this issue be solved?


Viewing all articles
Browse latest Browse all 9663

Trending Articles