Dual Boot - Fedora listed in Grub, Windows 10 not listed

I want to be prepared for the future. From what little I know, the partition for Fedora 42 is too small for updates and I will need to install 44 when it becomes stable. I will need to continue with the dual boot set up as I need the printer drivers and games on the WIN 10 side. If I need to reconfigure grub after a fresh install of 44 ,this will be my walk through on how to get the WIN 10 drive to be seen by grub as it is on a separate ssd. Only other thing I can surmise is if there actually will be indeed enough room on the smaller partition for the 44 kernal and previous. 43 & 44 have 2 gigs correct? While 42 has 1 gb.
Thanks again.

I avoid the symbolic links as they may be there for backwards compatibility with older tools that look in etc for configuration details and might disappear with some future update.

This means the content is not the default for fedora.

The common fix to restore the default content is

  1. sudo rm /boot/grub2/grub.cfg /boot/efi/EFI/fedora/grub.cfg to remove both those old files.
  2. sudo dnf reinstall grub2-common which should properly rebuild both the removed files.

Once that is done then a reboot should now use the actual grub.cfg file from /boot/grub2/grub.cfg. It then should show the windows entry

The file you posted should show the windows boot menu as shown in that posting.

###BEGIN /etc/grub.d/30_os-prober
menuentry ‘Windows Boot Manager (on /dev/sdb1)’ --class windows --class os $menuentry_id_option ‘osprober-efi-6C7D-51DF’ {
insmod part_gpt
insmod fat
set root=‘hd1,gpt1’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt1 --hint-efi=hd1,gpt1 --hint-baremetal=ahci1,gpt1 6C7D-51DF
else
search --no-floppy --fs-uuid --set=root 6C7D-51DF
fi
chainloader /efi/Microsoft/Boot/bootmgfw.efi
}
###Other OS found, undo autohiding of menu unless menu_auto_hide=2
if [ “${orig_timeout_style}” -a “${menu_auto_hide}” != “2” ]; then
set timeout_style=${orig_timeout_style}
set timeout=${orig_timeout}
fi

###END /etc/grub.d/30_os-prober

You may try sudo grep -A 15 os-prober /boot/grub2/grub.cfg for the current file located there and see what it shows about a windows boot menu. It may show something like above or it may show this if no windows boot manager was configured.

$ sudo grep -A15 os-prober /boot/grub2/grub.cfg
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

Games maybe, printer drivers probably already in linux.

We may be able to assist with that if we have more info.
Please provide the output of lsblk -f and df -h which will give info about drives / partitions / and free space.

A clean new install of f43 will create a 2GB /boot partition while f42 and earlier only created a 1GB /boot. However, it is worthwhile to note that an upgrade usually works and it is seldom required to expand a previously existing /boot. I have done so on 3 different systems with the 1GB /boot and had no problems.