Hi everyone
My friend had a wierd issue, where after moving to a new SSD + fresh Windows install, he always needed to select the new SSD (M.2 NVME) in the bios selection menu. Even after formatting the old ssd, it would still show up as a boot drive (Probably because we haven't removed all partitions).
Now when trying to change the boot order in the bios, it would never save, making him use the boot selection menu every time.
We decided to update the bios... And that's where the magic begins:
His new SSD isn't showing up in the bios anymore. Even after unpluggin every other drive and only using the m.2, it's not showing up.
But it does show up in the F12 boot selection menu. It can also boot normally into Windows. As soon as we plug in the old SSD (SATA) it would try to boot into that one. So again, he needs to use f12 to select the correct drive.
His Hardware:
R5 2600
Gigabyte B450 Aorus Pro
M.2 SSD: (Kingston) Gen. 3, NVMe
Bios Version: newest one, downloaded over the APP center (16th of April, 2022)
Windows 11
Any ideas to fix that?
My friend had a wierd issue, where after moving to a new SSD + fresh Windows install, he always needed to select the new SSD (M.2 NVME) in the bios selection menu. Even after formatting the old ssd, it would still show up as a boot drive (Probably because we haven't removed all partitions).
Now when trying to change the boot order in the bios, it would never save, making him use the boot selection menu every time.
We decided to update the bios... And that's where the magic begins:
His new SSD isn't showing up in the bios anymore. Even after unpluggin every other drive and only using the m.2, it's not showing up.
But it does show up in the F12 boot selection menu. It can also boot normally into Windows. As soon as we plug in the old SSD (SATA) it would try to boot into that one. So again, he needs to use f12 to select the correct drive.
His Hardware:
R5 2600
Gigabyte B450 Aorus Pro
M.2 SSD: (Kingston) Gen. 3, NVMe
Bios Version: newest one, downloaded over the APP center (16th of April, 2022)
Windows 11
Any ideas to fix that?