You are not logged in.
I began experiencing a new issue with my GRUB Boot Manager whenever I use The Windows Boot Manager to boot into a live USB, which takes me back to the GRUB Boot Manager. I was wondering, is there a way to make the GRUB Boot Manager auto-detect live USBs without having to manually add them in, instead of still having to use the Windows Boot Manager?((because as everytime I need to enter it, I need to enter the UEFI settings via GRUB, then restart my PC from there, then hit F12 on my keyboard to access the Windows Boot Manager, as I have Grub set to default). If not, how do I fix the Windows Boot Manager taking me back to GRUB? And how can I add it to the GRUB configuration properly? As it is there, but it doesn't work and it boots me straight into Windows.
Offline
Very hard to follow.
It sounds like you have boot managers all over the place.
Your motherboard is loading the windows boot manager, which you then use to boot off the usb, which has a grub boot manager on it.
I am not sure what the 'Windows Boot Manager' looks like.
You say you hit F12 to access it.
Which makes it sound like it's just a standard bios boot selection.
Please confirm what you're talking about.
Your motherboard supports UEFI.
That means it can act as your boot loader.
See my thread https://bbs.archlinux.org/viewtopic.php?id=238803 for what that entails.
That way, each drive has only what it needs on it.
Windows has its own drive with everything it needs to boot.
Linux has its own drive with no boot loader, because it doesn't need one besides UEFI.
If any drives are plugged in, they are auto detected by UEFI and available in the motherboard's UEFI boot loader.
Selecting a live usb will always yield another bootloader, since the point of a livecd is to be bootable by itself.
So it will always come with a boot loader.
If you still wish to use GRUB, grub has to live on one of the disks.
It is not built in to your motherboard.
So the motherboard has to boot until it can access that disk, then run the grub on that disk.
Then you would use grub to boot off whatever disks it is configured for.
Offline
Very hard to follow.
It sounds like you have boot managers all over the place.
Your motherboard is loading the windows boot manager, which you then use to boot off the usb, which has a grub boot manager on it.I am not sure what the 'Windows Boot Manager' looks like.
You say you hit F12 to access it.
Which makes it sound like it's just a standard bios boot selection.
Please confirm what you're talking about.Your motherboard supports UEFI.
That means it can act as your boot loader.
See my thread https://bbs.archlinux.org/viewtopic.php?id=238803 for what that entails.
That way, each drive has only what it needs on it.
Windows has its own drive with everything it needs to boot.
Linux has its own drive with no boot loader, because it doesn't need one besides UEFI.
If any drives are plugged in, they are auto detected by UEFI and available in the motherboard's UEFI boot loader.Selecting a live usb will always yield another bootloader, since the point of a livecd is to be bootable by itself.
So it will always come with a boot loader.If you still wish to use GRUB, grub has to live on one of the disks.
It is not built in to your motherboard.
So the motherboard has to boot until it can access that disk, then run the grub on that disk.
Then you would use grub to boot off whatever disks it is configured for.
"The Windows Boot Manager is a Microsoft-provided UEFI application that sets up the boot environment."
Sorry for not clarifying, and yes it is just like a standard bios boot selection. I have the Windows Boot Manager along with GRUB, on the same harddrive, not separate, as GRUB is highly customizable in terms of setting the order of the selectable drives (Windows, Linux, fallback, etc...), but I still need to use the Windows Boot Manager to be able to boot into live media such as USB Drives, which are auto-detected by it, unlike GRUB. So I really have to use both of them, but I have GRUB as default. I understood what you mean, but I began encountering a new problem with booting into USBs from the Windows Boot Manager, as it kicks me back into GRUB, which I never had, and it's almost been a year since I had this setup. So now I can't boot into USB's unless if I use the GRUB command line to boot into it manually, or by adding each and every live USB I have into my GRUB boot lost manually too.
Offline
If you wish to boot various liveUSBs, why not use your motherboard's normal boot selection process instead of Windows Boot Manager?
Then you won't have to troubleshoot any configuration issue with Windows Boot Manager.
I hear:
You can select Windows Boot Manager from grub.
It starts Windows.
You want it to only load the Windows Boot Manager and not start Windows.
Windows Boot Manager is an EFI application.
GRUB2 can load EFI applications using the `chainloader` command.
Perhaps there are some configurable options relating to that.
Offline
If you wish to boot various liveUSBs, why not use your motherboard's normal boot selection process instead of Windows Boot Manager?
Then you won't have to troubleshoot any configuration issue with Windows Boot Manager.I hear:
You can select Windows Boot Manager from grub.
It starts Windows.
You want it to only load the Windows Boot Manager and not start Windows.Windows Boot Manager is an EFI application.
GRUB2 can load EFI applications using the `chainloader` command.
Perhaps there are some configurable options relating to that.
I think the Windows Boot Manager is a boot manager just to boot into Windows which can be accessed via either my motherboard's normal boot manager (which I mistakenly thought WAS the windows boot manager), or from GRUB, sorry for mixing things up and causing confusion. So that means I have been using my motherboard's boot manager this entire time alonside GRUB. Well now there is a few options, either I delete GRUB/set my motherboard's boot manager as default, or I could make GRUB automatically detect liveUSB's, as I still don't know what is best.
Offline