Windows 10 not shown after dual boot

Back in business with old PC. It is still showing to altenatives, when starting up PC.
Other (first) one EndeavourOS, on linux and second is EndeavourOS, on linux (fallback initramfs).

Here You have mine grub:

# GRUB boot loader configuration

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="EndeavourOS"
GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3 nowatchdog"
GRUB_CMDLINE_LINUX=""

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Set to 'countdown' or 'hidden' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT_STYLE=menu

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
GRUB_THEME=/boot/grub/themes/EndeavourOS/theme.txt

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

# Uncomment to make GRUB remember the last selection. This requires
# setting 'GRUB_DEFAULT=saved' above.
#GRUB_SAVEDEFAULT=true

# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y
GRUB_DISABLE_SUBMENU=y

# To enable usage of os-prober, set GRUB_DISABLE_OS_PROBER to 'false'.
# Note: enabling os-prober creates a potential security risk!
# More info: https://www.gnu.org/software/grub/manual/grub/grub.html
GRUB_DISABLE_OS_PROBER=false

Can you run this command and show the returned address:

sudo cat /boot/grub/grub.cfg | eos-sendlog

It will send file /boot/grub/grub.cfg to a pastebin service. Then we can look at it.

I’m just wondering if there are too many partitions on first SATA hard disk. Because it is MBR.
If I don’t remeber wrong sda1 is for “System Reserved”.
Sda2 for “C”:- partition and sda3 for “D:”- partition. sda4 is perhabs for “Recovery”.
Difficalt to say, cause cannot use Disk Management right now.

In anyway there must be some unallocated 2 GB partition as well.

[boomer@boomer ~]$ sudo cat /boot/grub/grub.cfg | eos-sendlog
[sudo] password for boomer:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 5105 0 24 100 5081 30 6386 --:–:-- --:–:-- --:–:-- 6413
https://clbin.com/wXU3R

and

Used wonderfull program called Disks and took screenshots of situation here.

Seems that it doesn’t recognize the Windows disk properly…

Maybe this helps: write the following contents (as root) to file
/boot/grub/custom.cfg:

menuentry 'Windows 10' {
  savedefault
  search --set --fs-uuid 1846D85046D8306C
  chainloader +1
}

and reboot.

String 1846D85046D8306C is the UUID of a partition on your Windows disk.
If that string doesn’t work, try 7A82E64082E6008D instead.

there is on sda3 an extented partition MBR , so after this one you can have more

Okay, I will try.

Used nano:

[boomer@boomer ~]$ sudo su
[sudo] password for boomer:
[root@boomer boomer]# nano /boot/grub/custom.cfg
[root@boomer boomer]# exit
exit

Tried the first one, 1846D85046D8306C.
Same situation. Only to alternatives for Endeavour OS when starting up.
Now going to try with that other serial of numbers.

Now I could see 3rd alternative at the first time, but the timeout is so short that I couldn’t take a picture.
But from the next window I managed to get picture.

I used the second serial 7A82E64082E6008D latest.

Link to picture: https://1drv.ms/u/s!AkXsvqgcSrMCjSH-Z_27sp0dw62c

Are you sure the Windows disk is working?
You can try shutting down, unplugging the Linux disk and boot.

I tried install Endeavour OS with enabled UEFI, but it didn’t work.
I just disabled it and then I managed to install with alternative "KingstonDT101 II 8.20 found under “Legacy Boot Sources”.
Here is one picture from BIOS - Boot Order:

Second picture is from hectical saturday evening.
Trying to install Endeavour OS again. I don’t remeber how many times I tried.
Maybe this (next) picture can clear situation best. Frustration was apparent.

Yes, I can here it that both are running.

I will probably not get the bronze Endeavour OS pin :roll_eyes:

I’m gonna check BIOS again and take a photo of BIOS.

I used SuperGlue - Extra Strong for connecting data cable to that broken connector. Ofcourse not on the pins, but anyway.

Here is photo of situation before booting up again PC.

Okay I will try that as well.

Here is situation with SATA hard disk where Microsoft Windows 10 is installed.

I have not learned about Disk Part but Disk Party :grinning:

Preparations

First, make sure you have a backup of any personal data from both or your disks. They can be a life saver.

Then, make sure you have a Windows boot repair disk (or similar, I’m not really familiar with the Windows terms). This may be needed if the Windows boot system (MBR) fails after boot changes.

Note that the EndeavourOS installer USB stick is also important to have available.

And make sure your system is set to use BIOS legacy boot instead of UEFI boot.

Fixing the boot menu

Next, after the above, make sure both disks are plugged in and boot to EndeavourOS. Then run commands:

sudo grub-mkconfig -o /boot/grub/grub.cfg
sudo grub-install /dev/sda  # overwrites MBR

and reboot.
If you can see both EndeavourOS and Windows menu entries, then it works.
If not, try running the first of the commands above again and reboot.

Thank You , I will now first take care of needed data by copying those to extra hard disks. Let us see how things start to work.
It is nice that I’m getting hughe help

3 Likes