@100PIER

What version of Uefitool were you using?

@davidm71
I used a obsolete UEFItool version not working with MSI BIOS. I reported the problem to Fernando, and he has now fixed with the proper link into the start up post Guide LIne to offer now UEFItool v0.25.1.
v0.25.1 does fix the MSI BIOS compatibility problem when usin v0.22.4.

Good to know. Going to replace every version I have to 0.25.1. Thanks.

I doesnt really know what settings I have to change in the BIOS, after flashing the mobo with the modded BIOS.
( P8Z77-V Pro/thunderbolt)ä I have set everything as before, but I guess I need to di some boot settings for pcie or uefi ?

The ones that I can see possibly affecting this issue:

( fast boot= enable/disable)

Under CSM( compabiliry support mode) :
Launch CSM= Auto/enabled/disabled

Boot device control = UEFI and Legacy opROM / Legacy opROM only/ UEFI only

Boot from storage devices= Both, Legacy opROM first/ Both, UEFI first/ Legacy opROM first/ UEFI driver first/ ignore

Boot from PCIe/PCI Expansion devices= Legacy opROM first/ UEFI driver first

Thers also another for boot from Network devices, but it shouldnt matter?

Can I see in the BIOS that the mod is OK?

Thanks very much, now it works.
Found another site that claimed ”fast boot disabled” and ”CSM disabled”.
I went for this and now windows 10 is installing.

I would rather like to use an option to move the existing OS( like samsung data migrator) but it didnt work before anyway( to save time during fine summer days and do the clean install later). I dont know why, I could see and select the samsung 970 evo as target drive.

[Edit]installation of w10 did work, but no boot afterwards. Can not see Pata SS or something like in the boot options so I need to check the modded bios again.

@AAKEE After Windows stops copying installation files (and restarts), you have to choose "Windows Boot Manager" as boot device in UEFI.

help, I have x97 gaming 3, I bought ssd samsung 970 evo, but it does not see either in the BIOS or in windows 7. what to do

Zitat von agentx007 im Beitrag #3262

---

@AAKEE After Windows stops copying installation files (and restarts), you have to choose "Windows Boot Manager" as boot device in UEFI.

---

@treeshka 1) You need Win7 SP1 compatible driver for NVMe support (download it from win-raid NVMe driver thread or from Samsung website), which has to be added manually on "select drive for installation stage" - simply click "add driver" in bottom left side of installation window. If you can't find it, you have to use generic driver, which means updated installer for NVMe support (adding USB3.0 drives is recommended with later platform).
2) Windows instalator has to copy boot files in order for BIOS/UEFI to see NVMe drive as bootable.
Compatible MB should see it in hard drive section.
Make sure you don't have to disable SATA ports or other stuff, to enable/"switch on" M.2 port.
Check in MB manual for information about that.

@AAKEE ASUS BIOS flashback needs FAT32 pendrive, and correct file name for update to work (in my Sabertooth X79 case, it wanted "SABERX79.cap").

can you do this on a intel board (d5400xs) with 5400 chipset? the bios does have something called "UEFI Boot enabled/disabled"