So I have attempted to install a new M.2 drive (Adata 8200 Pro) into my Gigabyte Z390 AORUS PRO motherboard. When I first installed it I was able to open up my BIOS and see the SSD and also could install Windows onto it via the usual USB method. However after installing Windows and attempting to reboot the PC, my PC seemingly refuses to go to BIOS.
I've attempted to reset the mobo by taking out the battery but still not. When I was first able to get on the BIOS after first installing Windows I saw the two boot options. When I tried to open Windows from #2 it doesn't go to the OS but if I select the 'Windows Boot Manager' option it goes to the Windows I installed. I'm a bit confused as to why I see this and whether I've installed it wrong?
My main issue now is that whenever I turn on my PC with the M.2 SSD installed it now never goes to BIOS. I have 2 smaller SATA SSDs and 1 HDD. This issue happens whether or not they are also installed in the PC, however if I install these drives but take out the new M.2 SSD my PC boots perfectly normal and always goes to BIOS. This happens whether I use the M2A or M2M slot.
Anyone got an idea of what my issue may be and if it's at all linked to having 2 different boot options for the M.2 drive?
I've attempted to reset the mobo by taking out the battery but still not. When I was first able to get on the BIOS after first installing Windows I saw the two boot options. When I tried to open Windows from #2 it doesn't go to the OS but if I select the 'Windows Boot Manager' option it goes to the Windows I installed. I'm a bit confused as to why I see this and whether I've installed it wrong?
My main issue now is that whenever I turn on my PC with the M.2 SSD installed it now never goes to BIOS. I have 2 smaller SATA SSDs and 1 HDD. This issue happens whether or not they are also installed in the PC, however if I install these drives but take out the new M.2 SSD my PC boots perfectly normal and always goes to BIOS. This happens whether I use the M2A or M2M slot.
Anyone got an idea of what my issue may be and if it's at all linked to having 2 different boot options for the M.2 drive?