I have a PCIe adapter card supports PCIe v5.0 installed in the 2nd PCIe x16 slot which is actually a (PCIex4) with a Intel Optane M.2 NVMe (32GB) 500GB SSD installed in the adapter.
I am running 2 other sata hard drives one is a 2.5 SSD the other a western digital both connected through sata wires. I had attempted to just install Windows 10 professional x64 onto the NVMe just by booting to it even though it didn’t recognize it in the BIOS. But when the Windows installer from the USB flash drive booted into the situation and came to the point where I had to pick a hard drive to install windows on on, low and behold there was the NVMe listed.
It copied all the windows installation files onto the NVMe no problem without any extra driver to inject or clover bootloader bullshit. But the problem was when it rebooted to actually install the files it lost the NVMe again so I couldn’t finish the installation. When I booted back into my original Western Digital HD with windows already installed I checked the NVMe and windows recognized the NVMe and when I checked the contents of the drive windows had installed itself during the rebooting process without any help from me.
Then it creates a second problem which is after all that being accomplished and all that needs to happen is to boot into that hard drive to use it and it refuses, even using clover bootloader. So I don’t have any idea how the FXXX to get this GOD DXXX thing to boot so I can use it the way I want. Any suggestions on what the FXXX is going on here or how to fix it? Secure boot and tpm are disabled. Holla.
Afaik the optane dual drives (with a small amount of optane and a large amount of flash) are special and can be used to boot only if the motherboard has Intel Rapid Storage Technology feature in the bios ( an intel only raid mode) see
This mobo doesn’t have an NVMe slot and most likely its bios does not support this protocol to identify NVMe drives as part of the boot process (before any OS code is loaded).
Modern Windows (and other OSs) will see and allow using NVMe drives, which is why the Windows installer was able to detect the drive and install Windows onto it.
On the next reboot, the motherboard needs to be able to communicate with the drive to get at least the first Windows files loaded so that the OS can take over - this part is missing in your mobo.
board bios does not support nvme so it cannot boot from that.
As the other guy said, an operating system can see nvme fine regardless of bios support. So your OS on sata or the windows installer that is started from USB can see it, but then when the board has to boot from nvme it fails.
There is a modded bios here that claims to have added nvme support and other stuff. (as a confirmation stock bios cannot boot from nvme)
Read the whole thread to learn about potential issues and use it at your own risk.
also this article claims that gigabyte has made an updated bios that supports nvme for that board or similar ones, so if you don’t want to use the modded bios you can also check gigabyte’s bios downloads for that board and update bios
The F16f firmware primarily addresses the PKfail issue. However, WhiteCamellia identified an additional functionality. An analysis of the F16f firmware using UEFITool reveals the inclusion of the NVMe DXE trifecta (Nvme, NvmeSmm, NVMEINT13), which is essential for booting from NVMe drives, like M.2.