I want to use the Windows bootloader on dual boot, not GRUB. I already have a Windows 10 on my notebook. I tried EasyBCD, but it works only on non-UEFI devices.

I think it seems like this:

Windows boot menu

boot settings on Windows 10

  • 1
    Windows bootloader doesn't have support for Ubuntu. If you know how to add such support, then you are welcome to use it. – mikewhatever Sep 16 '16 at 12:48

Ordinarily, you'll use both GRUB2 and the Windows boot loader, because GRUB2 cannot launch a Windows kernel directly and the Windows boot loader cannot launch a Linux kernel directly. To boot Windows from GRUB2, GRUB2 launches the Windows boot loader; and to boot Ubuntu (or any Linux distribution) from the Windows boot loader, it launches GRUB2.

What you're asking for, then, is how to make the Windows boot loader the primary boot loader -- that is, the one whose menu you see when the computer starts up. This can be done (or so I hear), but you should ask about it on a Windows forum, since that's fundamentally a Windows question, not an Ubuntu question. Most Ubuntu users run GRUB2 as their primary boot loader, and have little knowledge of how to configure the Windows boot loader.

That said, there are alternatives to both GRUB2 and the Windows boot loader. See this page of mine for details. Technically, what you're interested in is a boot manager, not a boot loader. (A boot manager presents a menu with a list of OS boot options; a boot loader loads a kernel into memory and executes it. Both GRUB2 and the Windows boot loader perform both tasks, but some programs perform just one task or the other.) You don't say why you prefer the Windows boot manager to GRUB2, so I can only guess at what you might like; however, my suspicion is that you be interested in gummiboot (now called systemd-boot) or my own rEFInd. If you install either of these tools, it will become your primary boot manager, and it will then hand off control to either the Windows boot loader or a Linux boot loader. A final twist on this is that the Linux kernel can function as its own EFI boot loader, so if you use a pure boot manager, you can omit GRUB2 entirely when booting Ubuntu. This is easier with rEFInd than with systemd-boot because the latter can only launch programs from the partition on which it resides, and Linux kernels don't ordinarily reside on that partition under Ubuntu. rEFInd includes EFI filesystem drivers and can launch boot loaders from any partition the EFI can read, so rEFInd can live on the EFI System Partition (ESP) and launch a Linux kernel that's stored on a separate Ubuntu partition.

  • You may be able to edit BCD in Windows: see post by Rod Smith: askubuntu.com/questions/371559/… – oldfred Sep 16 '16 at 15:52
  • 1
    Actually, that bcdedit command doesn't edit the BCD; it adjusts the EFI boot variables, much like efibootmgr does in Ubuntu. Microsoft seems to have expanded bcdedit's capabilities beyond what the command's name implies. – Rod Smith Sep 16 '16 at 15:57
  • GRUB2 launches the Windows boot loader wrong! GRUB2 launches the Windows Boot Manager, then Windows Boot Manager launches Windows Bootloader. – Yousha Aleayoub Mar 2 at 17:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.