Can't boot windows after installing Fedora on a separate disk

Hello! So, when installing Fedora KDE, I removed both my SSD with Windows 11 and my 10tb HD, leaving only the disk where I wanted it to be installed. After seeing that the installation was successful, I put the other disks on and tried to boot windows. However, the windows disk’s name is “WDC WDS480G2G0C-00AJM0” and when i select it to boot, the message “Reboot and Select proper Boot device or Insert Boot Media in selected boot device and press a key” appears. Also, when I try to open the disks on the Fedora file manager, it asks for a password and I can’t access them.

lsblk -f:

NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1
└─sda2 BitLocker 2
sdb
├─sdb1 vfat FAT32 8036-B5B2 579.5M 3% /boot/efi
├─sdb2 ext4 1.0 2cef00ac-10bf-49bb-910c-b8fa41f92f83 620.8M 29% /boot
└─sdb3 btrfs fedora b4b7c221-9caa-428f-b825-fb33024c1f56 225.1G 2% /home
/
sdc
└─sdc1 vfat FAT32 DEBIAN TRIX 3E4B-9F0C
zram0 swap 1 zram0 375030a0-7083-4206-ac57-3bf631dec14e [SWAP]
nvme0n1
├─nvme0n1p1
├─nvme0n1p2 BitLocker 2
└─nvme0n1p3 ntfs F260A42260A3EB93

Found the solution:
I first downloaded and booted windows 11 on a pendrive and went to the repair option, then to the command prompt. I had to type in two recovery keys, because I have two encrypted disks (the third disk was formatted when I installed Fedora so it lost the encryption), that’s my guess. Then, I just followed a simple guide with the right commands to repair the bootloader and it started working again. Now, the windows’ boot option appears to be on my Samsung SSD when I look into BIOS, but I think that’s no problem.

The guide I used: How to Repair EFI/GPT Bootloader on Windows 10 or 11 | Windows OS Hub

Thanks everyone for the help!

By installing fedora in that way, with the windows drive disconnected, grub was not able to see the windows drive and did not add the windows boot loader to the menu.
When dual booting with windows it is simpler to just leave the windows drives connected and perform the installation while selecting only the desired disk for the installation.

Try running sudo grub2-mkconfig -o /boot/grub2/grub.cfg then reboot to see if it now appears in the grub menu for booting.

The reason you cannot open the disks in nautilus is that they are using bitlocker and you would need the bitlocker key to unlock the device.

1 Like

sudo fdisk -l would also be interesting to see a bit more detail about the partitions.

1 Like

The command didn’t work.

Disk /dev/sda: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors
Disk model: ST10000VN0008-2P
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: A709DCA7-D6E8-4934-8D48-57EB6C8C0D71

Device Start End Sectors Size Type
/dev/sda1 2048 32767 30720 15M Microsoft basic data
/dev/sda2 32768 19532869631 19532836864 9.1T Microsoft basic data

Disk /dev/sdb: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 860
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 0EC68C7B-6EB2-4BF4-91A8-233F20BFD9ED

Device Start End Sectors Size Type
/dev/sdb1 2048 1230847 1228800 600M EFI System
/dev/sdb2 1230848 3327999 2097152 1G Linux extended boot
/dev/sdb3 3328000 488396799 485068800 231.3G Linux filesystem

Disk /dev/nvme0n1: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: WDC WDS480G2G0C-00AJM0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 25D39563-1627-4C8E-85EA-A28C9C2615A0

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 34815 32768 16M Microsoft reserved
/dev/nvme0n1p2 34816 936105983 936071168 446.4G Microsoft basic data
/dev/nvme0n1p3 936105984 937697279 1591296 777M Windows recovery environment

Disk /dev/zram0: 8 GiB, 8589934592 bytes, 2097152 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

That was not a very good idea (although very understandable), as the removed disk had primary UEFI partition with bootloaders. But bootloader entries have relative paths, and when you added extra disk, they could have changed, so UEFI cannot find the specified bootloader now. In addition to that, your disk is encrypted with Bitlocker.

The easiest thing is probable booting into the UEFI bios and making sure your windows disk (the one with the original UEFI partition which is normally around 100MB, probably nvme0n1p1) is Number 1 in disk boot selection chain, then it should boot.

However in this case you will have to add an extra entry with bcdedit for linux.

Alternatively, you could edit uefi boot menu from linux, editing windows entry so it has the right path (efibootmgr or GUI apps like bootice or grub-customizer).

If this sounds too complicated, the easiest thing would be leaving 2 original disks as they were initially, making sure Windows boots again, then re-format the fedora disk completely, plug it in, and reinstall fedora (in this case the setup will be able to make correct boot menu entries considering your configuration).

1 Like

So I should keep all three disks in and simply reinstall Fedora on the same disk I installed it before? This process would fix the windows disk’s boot?

the fedora disk probably has its own uefi partition now (and there should only be one), that’s why in this situation i re-format the disk. I would have done the following:

  1. take the fedora disk out;
  2. make sure Windows boots fine (most important - as your drives are encrypted)
  3. re-format (or delete all the partitions) from fedora disk from under windows, connecting it via usb if you have usb enclosure
  4. connect clean disk (if windows won’t boot, check disk boot order in UEFI) and then install fedora.

this seems the easiest and safest way, but maybe others will give better advice.

1 Like

Unfortunately, I don’t know how to do what you recommended before and I only want to get to boot windows at this point. But how am I going to make sure Windows boots fine after removing the fedora disk if it doesn’t boot now?

I’ll boot windows on a pendrive so that I can try to run a reparation. Would this work?

If you take the Fedora disk out, the original disks should go back to their original names and UEFI should be able to find windows bootloader and start it. (Windows will boot again)

1 Like

Ok, thank you! I’ll try that

So, i removed the fedora disk and it still has the weird name and the same error message.

try booting into Fedora, install a GUI boot menu editor like EFIboots GitHub - Elinvention/efiboots: Manage EFI boot loader entries with this simple GUI
it will show what’s going on with your boot menu items.

efibootmgr -v will show the same, but it’s more difficult to control and easy to make a mistake.

also have a look at this thread: Windows boot not starting after Fedora installation - #14 by ajsiegel

1 Like

This is surprising - there is no EFI partition on the Windows drive (the partition isn’t shown as “EFI System”, and 16MB is much too small for Windows EFI).

So there’s nothing to initiate the boot into Windows.

Before you installed Fedora, how was this set up? Did you have only your NVMe and the 10 TB drive? Or was your Samsung SSD (now containing Fedora) in use as part of your install?

1 Like

I had removed both the SSD with windows and the 9TB drive. Only the Samsung SSD was left when I formatted it and installed Fedora. Then, after testing it, I put the other drives back on and I couldn’t boot Windows anymore.
However, I just fixed it. Here’s the solution:

I first downloaded and booted windows 11 on a pendrive and went to the repair option, then to the command prompt. I had to type in two recovery keys, because I have two encrypted disks (the third disk was formatted when I installed Fedora so it lost the encryption), that’s my guess. Then, I just followed a simple guide with the right commands to repair the bootloader and it started working again. Now, the windows’ boot option appears to be on my Samsung SSD when I look into BIOS, but I think that’s no problem.

The guide I used: How to Repair EFI/GPT Bootloader on Windows 10 or 11 | Windows OS Hub

1 Like

And you were using that Samsung SSD on your Windows-only setup before you installed Fedora?

I think your Windows EFI partition would have been on that Samsung SSD previously. So the Fedora install wiped it, and your repair procedure recreated it.

Glad it’s all working now, anyway! :tada:

1 Like

Yes, but Windows wasn’t installed on the Samsung SSD though, which is strange. But that’s probably it. I ran cd /d K:\efi\microsoft\boot\ on the command prompt and it couldn’t find the path.