Grub-2.04-18 Unstable update not detect Windows 10 boot on NVME

Hi Grub not detect windows 10 boot manager after update grub

#os-prober
/dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
#sudo update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Adding boot menu entry for UEFI Firmware Settings ...
Adding reboot option.
Adding poweroff option.
done

When grub downgrade from testing repo(Grub-2.04-17) grub detect windows boot manager.:

sudo update-grub 
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Warning: os-prober was executed to detect other bootable partitions.
It's 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 ...
Adding reboot option.
Adding poweroff option.
done

In /etc/default/grub try adding/uncommenting the line:

GRUB_DISABLE_OS_PROBER=false

Then update grub with: sudo update-grub.

1 Like

Thanks ā€“ I can confirm that GRUB was not detecting other systems on any of my machines after a recent update. This workaround has done the trick perfectly.

It seems that @philm patched the latest version of Grub to, by default, disable OS-Prober.

My grub configuration was missing the os-prober line completely. And without a .pacnew file showing the change, this issue was a bit of a hassle to identify. Iā€™m guessing this change will require manual intervention on a lot of systems.

Just updated to 2.04-18 via the stable branch. Windows10 option disappeared from bootloader.
@rev 's solution fixed it!

It is wanted by upstream to do so for security reasons: broken patch; fixed patch.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.