Thanks man! That is interesting. Sounds like you might be right (considering it does not work, and the comment about 300-500mb efi size.
I can mention that my windows install memory stick (rufus gpt from windows ISO) does show in bios both as Kingston AND UEFI Kingston (I of course allways choose to boot from the UEFI version. But considering the «ordinary / legacy version «shows» maybe it overrides and boots from that instead...

Is there a way that I can check (if i boot from my other windows sata disk) if it innstalled as UEFI or legacy? If so where?

Various ways, but regarding disk, just go to disk management in windows and u will see a 100Mb partition as Fernando already showed to u.

Regarding the boot from USB, there is no mistakes or failure, why?
Because this all due to the configuration in BIOS as PURE UEFI (CSM Disable) boot and this is mandatory, the USB will always boot UEFI, ignoring legacy boot... as long as the USB installer is well prep.
So the need for boot selection is irrelevant in this scenario (A USB UEFI installer and an empty disk as destination)
So again... CSM disable, Secure boot Other OS (Not always necessary and can be set to Windows UEFI after 2nd boot), USB installer will be the only available UEFI boot and the rest u already know, thats it no more secrets here.
Upon reboot with USB disconnected if no available boot, its simple...ur NVMe mod is not correct and once again the OS was installed as legacy, no boot available.
More clarified than this sorry, but its not possible, agree?

Hello, i need boot from pcie NVMe crucial m2 motherboard GA-990FXA-UD3 (rev. 4.0)... i need help to do!!! please.

@HSerg:

Zitat von HSerg im Beitrag #3203

---

Patched ASUS H87M-PRO 2102 BIOS (7MB)

---

Hi guys,

I think I found the problem. I think the problem is the Samsung 980 (not Pro version / standard version). One of the reasons is:
No matter what I do, I can not get it to work, even though I get it to appear as PATA. I have tried on two systems now with the same result.

Also i tried cloning my current SATA SSD, and it is not possible to clone due to this "fault":
"Incompatible disk selected
The target disk has an incompatible sector size for this operation. Please choose a different disk."

The Samsung 980 is 4096 byte/sector (while my Kingston SSD is 512 byte/sector).
I think that might be the reason to why my EFI boot partion always partitions as 300mb+ (compared to the regular 100mb). on the Samsung 980. (The Kingston SATA SSD partitions as 100mb EFI boot partition).

So yeah... I think the Samsung 980 might be unsuitable.

980 (PCIe 3.0, 1.4) or Pro (PCIe4.0, 1.3c) r both NVMe
https://www.samsung.com/semiconductor/mi...t/consumer/980/
https://www.samsung.com/semiconductor/mi...onsumer/980pro/

Now if u do see a PATA device/entry in bios the NVMe module DXE is presente, done correctly by mod.
So bizarre...but still u can perform an OS install and finish the whole setup? And as u said before, on the next reboot, nothing to boot, correct?
U've tried in 2 different systems...the same PCIe/M.2 adaptor, correct...

Thx a lot. Your method of adding the module to the BIOS worked perfectly on a GA-f2a78m-d3h rev3.

Hi,
Yeah. I am getting to the part where windows restarts in 10 seconds (after innstalling) and when it reboots automatically and I enter bios then there is no "windows boot manager" to be found.
I am using this one:
ICY BOX PCIe card with M.2 M-Key socket for one M.2 NVMe SSD (IB-PCI214M2-HSL) https://www.komplettbedrift.no/product/1...2-m-key-socket#
I can also mention that the drive is tested and working as a storage drive also. I just can`t boot from it. Only get it to appear as "PATA"
"U've tried in 2 different systems...the same PCIe/M.2 adaptor, correct..." Yes :)
I am going to try to use rufus to create a win10 installer partition on a SATA SSD and try to install from that to see if that makes a difference (if i disable USB LEGACY, then the UEFI win10 installer does not appear in bios, have a 5% theory that it might be something with that) hehe.

Hi Fernando,

I am not trying to boot from the PATA (honestly), I just try to make a point that the SSD980 "appears" as PATA in the BIOS, indicating that the biosflash is working. I am following your guide to the point. The EFI boot partition is allways like 295/300mb (and yes it gets created).

Hey, I have Gigabyte GA-F2A88XM-hd3 v 3.2 main board, and I successfully modded bios, ver FC.
The problem is that when I power on the PC it turns off immediately.
Tried confs:
Case 1.
PCIE x16 - graphics card (R7 360), PCIE x4 - PCIE adapter with SSD m.2 and 2 SATA disks > won't turn on.
Case2.
PCIE x16 - graphics card (R7 360), PCIE x4 - PCIE adapter without! SSD and with 2 SATA disks > turning on.
Case 3.
No external graphics card, PCIE x4 - PCIE adapter with SSD m.2 and 2 SATA disks > turning on , ssd readable/writable
Case 4
PCIE x16 - PCIE adapter with SSD m.2 and 2 SATA disks > turns on.
Case 5
PCIE x16 - graphics card (R7 360), 2 SATA disks booting up and then inserting gently adapter with ssd works and is readable even restart, but when poweroff it's same as case 1.

What's wrong?


SSD is Team Group MP33 256GB M.2 2280 PCI-e Gen. 3.0 x4 with NVM Express
Adapter is cheap one (PCI-e x4 M.2 NGFF M Key SSD NVMe) as seller mention it was tested with Samsung: 950pro, 960evo, xp941, pm951, pm961, sm951, sm961; Toshiba: BG1, XG3, XG4; OCZ: RD400; LITEON: T10; PLEXTOR M6e, 8PeG, M8PeG-N
And is compatible with PCI-e 3.0, 2.0, x4, x8, x16 slot.