[SOLVED] "No Windows Bootloader Found" In Dual Boot - How To Fix It?
antiX / MX LinuxThis forum is for the discussion of antiX and MX Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
"No Windows Bootloader Found" In Dual Boot - How To Fix It?
I try to install MX Linux on an existing partition for Linux (ext4) in a dual boot box. The installation stops around 95% when installing GRUB. A message says "can't get GRUB installed" and to reboot and go to the grub rescue menu. After reboot the live MX, I select bootloader and find the menu. Under the menu, I select "find window bootloader" and get a message, "no windows bootloader found".
At the moment, Windows couldn't get booted from the HD. The Windows repairing process didn't help. After I reinstalled the Windows, it can get booted from HD.
Now, I go back to MX Linux live from USB. I still get the error message. How to fix it?
Can you re-install MX and run those same commands again ?. From the installed system rather than the liveCD.
I get the same error after reinstalling MX. I can't see how to get to the hard drive to find out that Linux information from the MX live.
The error message is "GRUB installation failed. You can reboot to the live medium and use the GRUB Rescue menu to repair the installation". After playing the "switch to GRUB bootloader", I can't see how to fix the problem. Any advice?
For EFI install you may need to use GPT partition table, some firmawares are choosy and may not want to boot in EFI mode from MSDOS partitioned drive.
OTOH, for legacy boot you need a small 2 MB empty non-formatted so-called Grub-BIOS partition, Grub needs it for its stage 1.5 files, methinks. If this partition is missing Grub will fail, like it does on you. If you want to use current partition table use some other bootloader, SysLinux, Lilo, whatnot.
For EFI install you may need to use GPT partition table, some firmawares are choosy and may not want to boot in EFI mode from MSDOS partitioned drive.
OTOH, for legacy boot you need a small 2 MB empty non-formatted so-called Grub-BIOS partition, Grub needs it for its stage 1.5 files, methinks. If this partition is missing Grub will fail, like it does on you. If you want to use current partition table use some other bootloader, SysLinux, Lilo, whatnot.
During the installation procedure, there isn't a requirement on grub-bios partition if my memory is correct.
So I guess we can assume BIOS rather than [U]EFI complications. I'd be looking in the BIOS menus for a "anti-virus" type setting that may be stopping grub updating. colorpurple21859' suggestion should test that tho'.
So I guess we can assume BIOS rather than [U]EFI complications.
The drive is msdos and the first partition is diag not esp, and no /sys/firmware/efi. With the usb plugged in, grub has the usb as the first drive. See post 3 and 9.
Quote:
Under the /sys/firmware, there are three directories: acpi dmi memap, but not any files.
I was checking for the existence or not of a /sys/firmware/efi directory. If this had been a uefi system the partition table would have been gpt. The cat command would have returned "/sys/firmware/efi is a directory" if booted in uefi mode, versus legacy/csm mode.
Last edited by colorpurple21859; 03-23-2021 at 09:32 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.