I have Ubuntu (18.04) and Windows 10 (May 2019 Update) installed on separate hard drives. This works, in a manner. Without entering the grub menu my system boots into Ubuntu. I can use Grub2 to boot into Windows 10. However, to do so, I have to:
- Enter the grub menu
- Try booting into Windows 10
- Receive an error: "invalid EFI file path"
- Press "escape" to enter a grub terminal
- Type "exit" to leave the terminal (and grub)
After this, the system boots into Windows 10 successfully. My custom grub entry (/etc/grub.d/40_custom) is:
menuentry "Windows 10" --class windows --class os {
insmod part_msdos
insmod ntsf
search --no-floppy --fs-uuid --set=root MY_UUID
chainloader +1
}
The UUID I am using points to the larger partition of the following:
Device Boot Size Type
/dev/sdb1 * ... 238G HPFS/NTFS/exFAT
/dev/sdb2 ... 474M Hidden NTFS WinRE
No additional information is given about these partitions when I run lsblk or blkid.
My question is, why does this still work, and can I modify my custom grub entry so that it works when I select it, rather than after doing what I do above?
exit
in the Grub-command-line is that the boot failed and the firmware switches to the next entry in the boot-order list which is Windows in your case. – mook765 Sep 15 '19 at 04:29