PC with dual boot Manjaro/Windows opens directly Windows

Hi, I have an Acer Aspire 5. I’m having problems with dual booting Windows 11/Manjaro. I successfully installed Manjaro. However, every time I start the computer, the PC boots directly Windows without the choice between Manjaro and Windows Boot Manager doesn’t appear, and it directly opens Windows 11. The only way I found to enter the menu is to go into advanced restart, use a device, select Manjaro, and successfully enter the menu with the option to choose between Manjaro and Windows Boot Manager. Obviously, this process is long and inconvenient, and I would like the menu to appear at every startup. Going into the BIOS settings and the Boot section, the Boot Priority Order is empty, and I have no way to change anything. Previously I installed Arch Linux and there was the same problem. So, I uninstalled Arch and then in the Boot Priority Order there was Windows Boot Manager.

You might find something useful it the following article:

You will likely need to provide more information for others to do more than guess.


Hi @Kastor and welcome to the Manjaro community

As a new user, please take some time to familiarise yourself with Forum requirements; in particular, the many ways to use the forum to your benefit:

And last, but not least, the Stable Update Announcements, which you should check frequently for important update related information.

Cheers.

2 Likes

Since I have Manjaro and Windows 11 installed on the same disk, that article is not useful to me. What information should I add? I think I have already described the situation and I add that I cannot change the Boot Priority Order because no operating system is listed there.

Maybe your problem is with Windows How to Fix Missing GRUB Boot Menu after a Windows Update – TechBlog.dev

This sounds to me like you’ve got one system installed in legacy BIOS mode (CSM) and the other one in native UEFI mode. It is possible to run a setup like this, but only if both systems are installed on separate drives. It does not work when they’re on the same drive.

So, you’re going to have to convert one of your systems to boot in the same manner as the other one, but doing so is not easy — especially not for a beginner — and in the end, you might be better off reinstalling. And in that case, I would recommend disabling CSM in your UEFI firmware and installing both systems in native UEFI mode.

1 Like

There is useful information in the article, whether or not you read past the title; the specific caveats mentioned, for example.

You have now revealed that you’re multibooting on a single disk – that would have been helpful to know, for a start. System information would be useful, also, though I concede at this point it’s not easy to provide much. The information (links) provided lead you to a wealth of possibilities.

For now, you might benefit from recreating (reinstalling) Grub; please see:

Follow the directions carefully. You will need to boot from a Manjaro Installer DVD/ISO/USB, and enter a chroot environment.

Good luck.

I apologize for stopping at the title without reading the article, now I’ve read all the article. I’ve Secure Boot, Fast Startup, Fast Boot disabled and OS prober is set up correctly. But the problem is that the Boot Priority Order is empty and I can’t set GRUB first because it’s not there. So, I can access GRUB only from Advanced Restart → Use a device → Manjaro If GRUB is set up correctly, as I think it is, I don’t know if I should install rEFInd.

How do I know if one of the OS is in Legacy BIOS mode?

In Windows:
System Information” in Start panel and under BIOS Mode, you can find the boot mode. If it says Legacy, your system has BIOS. If it says UEFI, well it’s UEFI.

In Linux:

ls /sys/firmware/efi

… if not found, it’s in Legacy mode.

1 Like

In Manjaro, issue the following command in a terminal window… :point_down:

mount | grep efivarfs

If it produces output, then your Manjaro system is installed in UEFI mode. If it does not produce any output, then it is installed in legacy BIOS (CSM) mode.

I cannot tell you how to do it in Microsoft Windows, however — I do not use that… um… “operating system”. :stuck_out_tongue:

Likewise. Only in VMs just to see what M$'s latest shenanigans are …

The Windows instructions were the result of a search. :wink:

1 Like

Not even that. I’d get nightmares just thinking about it. :stuck_out_tongue:

3 Likes

They are both UEFI.

1 Like

I do like the “horror” genre. But I promise their OSes will never touch any bare metal.

2 Likes

In that case, I suspect that you’ve recently had a Wintendo update, and that it wiped your EFI variables. Wintendo does like to claim the computer for itself.

If you can boot up into Manjaro, you must reinstall the boot loader. The easiest way to do it is to download install-grub from the repository and run it. It’ll take care of everything.

sudo pacman -S install-grub
sudo install-grub

If you cannot get into Manjaro, then you must chroot in from the Manjaro live USB and then run those two commands in the chroot environment.

The installation has been done but I found some sentences that gave me some doubts.

Grub will be installed on: EFI
Installazione per la piattaforma x86_64-efi.
Installazione completata, nessun errore segnalato.
Update UEFI Fallback file: /boot/efi/EFI/Manjaro/grubx64.efi
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.9-x86_64
Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-6.9-x86_64.img
Found initrd fallback image: /boot/initramfs-6.9-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: avviso: tipo di device nvme0n1 sconosciuto.
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
/usr/bin/grub-probe: avviso: tipo di device nvme0n1 sconosciuto.
done

I believe this is just talking about another partition that you don’t care about. It did find your kernel and initramfs (on your root partition).

Does it boot?

No, it’s because OP once (or still) had(/has) grub-btrfs installed instead of the regular grub. :wink:

2 Likes

My bad. My root FSs are buttered.

2 Likes

Nothing changed. PC still boots directly Windows and the boot priority order is still empty.