Boot Menu messy after last update - please advise

Support
,
1

Hi all, after the last update, I had a boot error that I managed to fix, but I would some inputs on the result / good practices

Before update, my bios boot setup was like that:

  • Option 1: UEFI partition (this is my Manjaro)
  • Option 2: Windows (on another disk)

System:

❯ uname -a
Linux  7.2.9-1-MANJARO #1 SMP PREEMPT_DYNAMIC Sat, 03 Oct 2026 15:02:22 +0000 x86_64 GNU/Linux

Explanations

  • Updated to latest release, reboot, when straight to GRUB_RESCUE, Error: grub_user_error not found
  • Booted into BIOS, and I saw that another boot entry was set at option 3: Manjaro
  • Booted on option 3, messy boot menu (see below), but it worked
  • I then applied the proposed fix proposed by volker62
  • (
  • it works but I have the following issues (I guess they are related)

Messy Boot Menu

I have now few entries:

  • Manjaro Linux
  • Advanced options
  • Windows boot manager
  • UEFI Firmware Settings
  • Windows boot manager (EFI BootNext)
  • Manjaro (EFI BootNext)
  • (linux logo) EUFI OS (EFI BootNext)
  • Memory tester

efibootmanager

Boot0000* Windows Boot Manager  HD(1,GPT) 
Boot0001* Manjaro       HD(3,GPT,64ce30ef-xxx)/\EFI\Manjaro\grubx64.efi 
Boot0002* UEFI OS       HD(3,GPT,64ce30ef-xxx)/\EFI\BOOT\BOOTX64.EFI0000424f

Grub version

I did run a new grub-install as recommended

grub-install (GRUB) 2:2.16-3.1

boot/efi/EFI

But I found out that I have old boot installations (I used to test on other disks)

Jun  4  2024 Manjaro2
Jun  4  2024 ManjaroM

Questions:

Did i do the right things ? What else should i if not ?

Can I remove manually the old folder in EFI ?

Thanks in advance

2

[Stable Update] 2026-10-28 - Plasma 6.75, GNOME 50.5, COSMIC 1.9.0 - #51 by Yochanan

Review your /etc/default/grub.pacnew. A new default sets GRUB_DISABLE_BOOTNEXT to true which will disable creating those entries.

[Unstable Update] October 2026 - #125 by Yochanan

# Disable generating menu entries for other EFI boot manager entries detected
GRUB_DISABLE_BOOTNEXT=true

# Skip EFI boot manager entries that are marked inactive
# when when generating bootnext entries
GRUB_BOOTNEXT_OMIT_INACTIVE=true

See:

3

Translation: the messy is the new normal, but one can toggle it off.

To me what you posted looks normal, but i cannot know how many other remnants of os boot entries do you have. Post
sudo tree /boot/efi

4

linux72 is now end of life. I would suggest switching to a supported kernel before the next update.

5

SHORT: add a line to /etc/default/grub
GRUB_DISABLE_BOOTNEXT=true

and do in terminal: sudo update-grub.

9 
sudo tree /boot/efi
sudo: tree: command not found

@Teo is that normal ?

@nikgnomic adding these 2 lines to grub did the trick. thanks !

@GaVenga That worked, thanks a lot !

@ben75 the only option I have (above 72) is 7.3.0rc6-1 which is marked as experimental.

Should I downgrade to 6.18 ?

Moderator edit: Merged consecutive replies. Please quote or tag other users in one reply instead of replying to each one separately.

10

7.2 is not yet eol, in the manjaro stable. Will be next month. So yeah, your choice - now 7.3rc, or after a month 7.3 final, or 6.18 lts.

About tree: Then tree is not installed

sudo pacman -S tree
11

@Teo

Noted for the kernel

here is the tree result

/boot/efi
├── EFI
│   ├── boot
│   │   ├── boot64.efi
│   │   └── bootx64.efi
│   ├── Manjaro
│   │   └── grubx64.efi
│   ├── Manjaro2
│   │   └── grubx64.efi
│   └── ManjaroM
│       └── grubx64.efi

I do not use Manjaro2 and ManjaroM anymore

12

Then you can delete those.
If they still appear in the firmware menu, to delete from there too use efibootmgr

13

If only one instance of Manjaro is installed, and EFI/Manjaro/ is the active loader, this should clean it up:

sudo rm -rf /boot/efi/efi/Manjaro2/
sudo rm -rf /boot/efi/efi/ManjaroM/

As we don’t know which efi stub is current in /boot/efi/EFI/boot/:

sudo rm /boot/efi/efi/boot/boot64.efi
sudo rm /boot/efi/efi/boot/bootx64.efi
sudo install-grub
sudo update-grub

If everything worked as expected, reboot:
sudo shutdown -r now or sudo reboot now