

There are two ways to do this that are relatively safe and easy.
Refind boot manager fail install#
It could be you've also got an EFI-mode GRUB and had been booting that way or maybe you had been switching between OSes by using the computer's built-in boot manager (typically accessed by hitting Esc, Enter, or a function key at start time).Īt this point, your best bet is to install an EFI-mode boot loader for Linux.

Refind boot manager fail windows#
Such a mish-mash means that you'd not be able to boot Windows from a BIOS-mode GRUB on this computer. Your disk uses the GUID Partition Table (GPT), which means that Windows will install to and boot from this disk only in EFI mode but there's evidence of a BIOS-mode installation of GRUB, the standard Ubuntu boot loader.The same may be true of Ubuntu, too but see below.

(I've seen this happen from time to time.) OTOH, if those files are missing, then it means that Windows has failed to install its boot loader. My suspicion is that they do exist, but the script has omitted these entries.
