Boot straightly into GRUB instead of pulling out BIOS boot menu

Tomsonas · 2020-01-31 22:09

Note that I use a Wubi installation.

I'd like to boot into GRUB as I turn on my computer, I find it more convenient than repeatedly pressing F12 key. When I installed Q4OS using Wubi installer, it worked pretty much flawlessly and I could get into GRUB as soon as I turned on the computer. Then after few Windows restarts it broke, now I have to use BIOS boot menu to boot into GRUB, then from GRUB boot into Q4OS.

I tried using the solution on askubuntu.com (https://askubuntu.com/a/655279), changing

bcdedit /set {bootmgr} path \EFI\ubuntu\grubx64.efi

with

bcdedit /set {bootmgr} path D:\debian\winboot\EFI\grubx64.efi

but that didn't work.

What would be a possible solution to that?

Dai_trying · 2020-02-01 09:30

You could try moving Q4OS up in the boot order using efibootmgr, if you run the command it should give you some similar output to the below example.

dai@laptop:~$ efibootmgr 
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0001
Boot0000* Debian
Boot0001* Windows Boot Manager

Then you would know the boot order (BootOrder), using this information you can re-order them with the following command (If you are using root account you do not need to use sudo)

sudo efibootmgr -o 1,0

which should give you something like this when entered

dai@laptop:~$ sudo efibootmgr -o 1,0
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001,0000
Boot0000* Debian
Boot0001* Windows Boot Manager

Noting that the line BootOrder has changed from 0000,0001 to 0001,0000

If you have any problems with this please enter your full failed output here and I'm sure it can be easily resolved.

Tomsonas · 2020-02-01 13:13

Dai_trying wrote:

You could try moving Q4OS up in the boot order using efibootmgr, if you run the command it should give you some similar output to the below example.
dai@laptop:~$ efibootmgr 
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0001
Boot0000* Debian
Boot0001* Windows Boot Manager
Then you would know the boot order (BootOrder), using this information you can re-order them with the following command (If you are using root account you do not need to use sudo)
sudo efibootmgr -o 1,0
which should give you something like this when entered
dai@laptop:~$ sudo efibootmgr -o 1,0
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001,0000
Boot0000* Debian
Boot0001* Windows Boot Manager
Noting that the line BootOrder has changed from 0000,0001 to 0001,0000
If you have any problems with this please enter your full failed output here and I'm sure it can be easily resolved.

So I tried using your solution, my output from efibootmgr looks like this before it

tomas@q4os-pc:~$ efibootmgr
BootCurrent: 0000
Timeout: 10 seconds
BootOrder: 0001,0000,2001,2002,2003
Boot0000* Q4OS Centaurus
Boot0001* Windows Boot Manager
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network

After using it, it looks like this

tomas@q4os-pc:~$ efibootmgr
BootCurrent: 0000
Timeout: 10 seconds
BootOrder: 0001,0000
Boot0000* Q4OS Centaurus
Boot0001* Windows Boot Manager
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network

That didn't fix my problem, after restarting the computer it boots into Windows, so I still have to pull out BIOS boot menu with F12 key to enter GRUB for Q4OS. Also it seems to be reverted to the first output right after I boot into Q4OS and enter efibootmgr into terminal.

Last edited by Tomsonas (2020-02-01 13:19)

Dai_trying · 2020-02-01 15:28

You don't show your command and output for what you tried, I could continue guessing but need to know what you actually did in order to offer advice.

q4osteam · 2020-02-01 18:49

We can recommend you to follow advice above by Dai_trying, or you can run command as administrator from within Windows:

bcdedit /set {bootmgr} path \EFI\debian\wubildr\grubx64.efi

q4osteam · 2020-02-01 22:43

You may also make use of "boot-repair-disk" https://sourceforge.net/p/boot-repair-cd/home/Home/

Tomsonas · 2020-02-02 13:27

q4osteam wrote:

We can recommend you to follow advice above by Dai_trying, or you can run command as administrator from within Windows:
bcdedit /set {bootmgr} path \EFI\debian\wubildr\grubx64.efi

Thanks for the help, unfortunately that does not work for me. Not quite sure about boot-repair-disk, but might check it sometime later.

q4osteam · 2020-02-02 14:47

Tomsonas wrote:

... unfortunately that does not work for me.

.. for secure boot enabled systems try this:

bcdedit /set {bootmgr} path \EFI\debian\wubildr\shimx64.efi

Tomsonas · 2020-02-02 15:29

q4osteam wrote:

Tomsonas wrote:
... unfortunately that does not work for me.
.. for secure boot enabled systems try this:
bcdedit /set {bootmgr} path \EFI\debian\wubildr\shimx64.efi

Maybe that's my PC, I don't know, but after I did this it created a new entry in BIOS boot menu. I had 3 entries - 2 "Windows boot managers" and Q4OS Centaurus. The first Windows boot manager entry booted me into Windows, the second Windows boot manager entry booted me into shimx64.efi, so GRUB for Q4OS. Q4OS Centaurus entry booted me into shimx64.efi too. Oddly enough, Windows regenerated its boot entry and set it as first in order as I entered this command into Command Prompt.

q4osteam · 2020-02-02 17:16

Maybe it would be worth using the Linux tool "efibootmgr" to make Q4OS EFI entry the default, as suggested above by "Dai_trying".

Tomsonas · 2020-02-02 17:38

q4osteam wrote:

Maybe it would be worth using the Linux tool "efibootmgr" to make Q4OS EFI entry the default, as suggested above by "Dai_trying".

Tried it as well, didn't work

q4osteam · 2020-02-02 17:45

What command line exactly did you use and what output did you get ?

Tomsonas · 2020-02-02 17:50

q4osteam wrote:

What command line exactly did you use and what output did you get ?

I tried using

sudo efibootmgr -o 1,0

and the output was

tomas@q4os-pc:~$ efibootmgr
BootCurrent: 0000
Timeout: 10 seconds
BootOrder: 0001,0000
Boot0000* Q4OS Centaurus
Boot0001* Windows Boot Manager
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network

meanwhile it didn't work

q4osteam · 2020-02-02 17:56

Well, try to run again:
$ sudo efibootmgr
and paste the output.

Tomsonas · 2020-02-02 18:13

q4osteam wrote:

Well, try to run again:
$ sudo efibootmgr
and paste the output.

tomas@q4os-pc:~$ sudo efibootmgr
[sudo] password for tomas: 
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0000,0001,2001,2002,2003
Boot0000* Windows Boot Manager
Boot0001* Q4OS Centaurus
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
tomas@q4os-pc:~$

q4osteam · 2020-02-02 18:15

Now, run:
$ sudo efibootmgr -o 0001,0000,2001,2002,2003
and paste the result.

Tomsonas · 2020-02-02 18:18

q4osteam wrote:

Now, run:
$ sudo efibootmgr -o 0001,0000,2001,2002,2003
and paste the result.

tomas@q4os-pc:~$ sudo efibootmgr -o 0001,0000,2001,2002,2003
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0000,2001,2002,2003
Boot0000* Windows Boot Manager
Boot0001* Q4OS Centaurus
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
tomas@q4os-pc:~$

Last edited by Tomsonas (2020-02-02 18:21)

q4osteam · 2020-02-02 18:23

Try to reboot now and visually check the boot sequence. EFI bios should load GRUB bootloader now, as shown in the "BootOrder". It's possible Windows will revert the sequence again, unfortunately, we cannot control the process. If the EFI settings will not persist, we could try another way to force Windows to keep the boot order. So, leave a request here, if needed.

Tomsonas · 2020-02-02 18:35

q4osteam wrote:

Try to reboot now and visually check the boot sequence. EFI bios should load GRUB bootloader now, as shown in the "BootOrder". It's possible Windows will revert the sequence again, unfortunately, we cannot control the process. If the EFI settings will not persist, we could try another way to force Windows to keep the boot order. So, leave a request here, if needed.

Sadly it didn't work. I only want it to boot into GRUB for my own convenience, but if nothing else can be done, it's totally fine.

Tomsonas · 2020-02-02 18:39

Also maybe it's because I'm using a Wubi installation? Because as I read about such installations, they don't give entirely full user experience, though my current Q4OS Wubi installation works fine and at the same time way better than Ubuntu Wubi installation. I'm using Secure Boot as well.

q4osteam · 2020-02-02 20:24

Tomsonas wrote:

Also maybe it's because I'm using a Wubi installation?

The bootloader configuration is the same as for regular dual boot systems, so the answer is likely no.

You could try one more attempt to convince Windows of using GRUB bootloader. Try to run in Windows as administrator:
bcdedit /set {fwbootmgr} displayorder {bootmgr} /addlast

Tomsonas · 2020-02-03 18:32

q4osteam wrote:

Tomsonas wrote:
Also maybe it's because I'm using a Wubi installation?
The bootloader configuration is the same as for regular dual boot systems, so the answer is likely no.
You could try one more attempt to convince Windows of using GRUB bootloader. Try to run in Windows as administrator:
bcdedit /set {fwbootmgr} displayorder {bootmgr} /addlast

How do I make it work for BCD configuration I currently have without messing it up? I actually tried doing something like this before and ended up damaging Windows boot manager, having to fix it with installation media.

Firmware Boot Manager
---------------------
identifier              {fwbootmgr}
displayorder            {bootmgr}
                        {541bc494-4549-11ea-af08-9829a64895aa}
                        {885ee8b5-4589-11ea-a897-b62e688b6ee1}
                        {885ee8b6-4589-11ea-a897-b62e688b6ee1}
                        {885ee8b7-4589-11ea-a897-b62e688b6ee1}
timeout                 0

Windows Boot Manager
--------------------
identifier              {541bc494-4549-11ea-af08-9829a64895aa}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\debian\wubildr\shimx64.efi
description             Q4OS Centaurus
locale                  en-US
default                 {current}
displayorder            {current}
timeout                 30

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-US
default                 {current}
displayorder            {current}
timeout                 30

Firmware Application (101fffff)
-------------------------------
identifier              {885ee8b5-4589-11ea-a897-b62e688b6ee1}
description             EFI USB Device

Firmware Application (101fffff)
-------------------------------
identifier              {885ee8b6-4589-11ea-a897-b62e688b6ee1}
description             EFI DVD/CDROM

Firmware Application (101fffff)
-------------------------------
identifier              {885ee8b7-4589-11ea-a897-b62e688b6ee1}
description             EFI Network

Dai_trying · 2020-02-03 18:50

Have you checked the UEFI (BIOS) settings for the machine? Most systems I have used have an option for setting the boot order, although it might not always be obvious it is usually there.

q4osteam · 2020-02-03 18:55

Your Windows bootloader config looks pretty common. The command suggested above shouldn't mess anything, it should only move the {bootmgr} entry, i.e Windows boot manager, to the last position to free bios to use the second entry {541bc494-4549-11ea-af08-9829a64895aa}, i.e shimx64.efi bootloader.

If you want to try something less aggressive, run in Windows command-line:

bcdedit /set {fwbootmgr} displayorder {541bc494-4549-11ea-af08-9829a64895aa} /addfirst

It will move the Q4OS Centaurus entry to the first position.

Tomsonas · 2020-02-03 19:01

q4osteam wrote:

Your Windows bootloader config looks pretty common. The command suggested above shouldn't mess anything, it should only move the {bootmgr} entry, i.e Windows boot manager, to the last position to free bios to use the second entry {541bc494-4549-11ea-af08-9829a64895aa}, i.e shimx64.efi bootloader.
If you want to try something less aggressive, run in Windows command-line:
bcdedit /set {fwbootmgr} displayorder {541bc494-4549-11ea-af08-9829a64895aa} /addfirst
It will move the Q4OS Centaurus entry to the first position.

Still boots into Windows

Q4OS Forum

#1 2020-01-31 22:09

Boot straightly into GRUB instead of pulling out BIOS boot menu

#2 2020-02-01 09:30

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#3 2020-02-01 13:13

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#4 2020-02-01 15:28

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#5 2020-02-01 18:49

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#6 2020-02-01 22:43

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#7 2020-02-02 13:27

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#8 2020-02-02 14:47

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#9 2020-02-02 15:29

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#10 2020-02-02 17:16

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#11 2020-02-02 17:38

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#12 2020-02-02 17:45

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#13 2020-02-02 17:50

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#14 2020-02-02 17:56

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#15 2020-02-02 18:13

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#16 2020-02-02 18:15

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#17 2020-02-02 18:18

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#18 2020-02-02 18:23

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#19 2020-02-02 18:35

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#20 2020-02-02 18:39

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#21 2020-02-02 20:24

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#22 2020-02-03 18:32

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#23 2020-02-03 18:50

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#24 2020-02-03 18:55

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

#25 2020-02-03 19:01

Re: Boot straightly into GRUB instead of pulling out BIOS boot menu

Board footer