Seems this post is missing some information. OPs description is kind of confusing so I ask you to reply to the below question accordingly to get a better idea of the problem. Otherwise, we’ll be throwing at walls until it sticks.
When does this error appear? When you try to boot your computer after you install and restart the system or when you try to boot the system using your install media?
You want to dual-boot with and Windows. Which one did you install first?
How old is your PC?
Does it have a BIOS or EFI?
What install media (USB/DVD) do you use to install the distro or OS?
If USB how did you create the bootable USB (What method/software you used)?
How did you do the partitioning (Manually through the installer or Automatically)?
Are sure you didn’t select the wrong hard drive when partitioning?
1 - when trying to boot my western digital hd which i used to install eos
2 - no, just keep the old eos install on my samsung hd while installing the new one on the WD hd
3 - i bought it recently but that doesnt means the hardware is recent, i use an i5 cpu and ddr3 ram, gpu 1650 gtx
4 - i am not quite sure but it seems to be legacy bios from what i’ve checked with the blue background, it doesnt have a mouse cursor
5 - i normally use a dvd driver but decided to use usb flash this time.
6 - using mintstick
7 - Manual partitioning, i normally create first one for / and then another one for /home, been doing that for years
8 - yes i am sure, i chose the WD hd while keeping my old eos install on the samsung hd
That means your Samsung drive is the primary drive or being technical it must be connected to SATA0 port. And your boot details might have been written on to that drive.
Try this just unplug your Samsung drive and install onto your WD drive. Then check if that solves the issue.
No an i5 has a EFI Bios… you should check the boot load order inside the bios… the first entry must named “Linux bootloader” or so, after saving and reboot you should see entries for other OS you have installed
If you want to dual boot install Windows first to whatever drive you want that to be in. Then install Endeavour on the 2nd drive. GRUB should detect the Windows install and write the bootloader correctly.
EDIT: You’re getting that message because your connected drive doesn’t have the details pointing to the bootloader.
i dont want w10, i just had it because when i bought my new pc case i took it to a ti shop to install the components on the new case, and they decided to install w10 on the WD hd, that’s why i had it
you have to change the boot load order of youre drives inside the bios… and i mean not to only change the drives that should be first drive… there must be another entry inside youre bios that handle the bootloaders… most times there are still named *like" linux boot loader/windows bootloader etc.
The Problem i think is youre Bios loadorder isn´t correct… or you have still change the to much settings with the order from what harddrive the OS should boot
The Entry must be “Linux-Boot-Loader” from there you can boot to windows, another EOS or OS you have installed
would resolve the lag of needed information for me.
In case it can happen that if system software is set to be able to boot USB in legacy mode, and harddrive is set to allow EFI mode so you install in MBR mode, but system tries to boot hard drive in EFI mode… And do not find the bootloader.
As long as @ramon395 is not providing proper info i can not help.
The recommendation is to disable all CSM legacy boot options… but in case windows is installed in legacy mode you can not do that, as with it you will ot be able to boot windows anymore… only if you go to reinstall with efi-boot-mode enabled.
at walls until it sticks
.
and Windows. Which one did you install first?
