M.2 won't boot Windows 10: Plextor M8Pe on ASUS Z170 PRO GAMING

Nurglitch

Commendable
Jan 29, 2017
2
0
1,520
The combination is:

Plextor M8Pe SSD 256GB M.2 2280 PCIe Gen 3x4 NVMe drive installed on ASUS Z170 PRO GAMING LGA 1151 DDR 4 Z170 GW motherboard. The CPU is i5-7600K, 4.2GHz, 6MB.

It is a fresh build and I am trying to install Win 10 from scratch. There is also a SATA Toshiba drive [TOSHIBA DT 3TB 64MB 3,5'' 7200rpm SATA3] installed. The M.2 I would like to use as a system drive, the Toshiba as storage drive. Fairly obvious.

What happens:
The motherboard absolutely won't accept a UEFI Win 10 install USB. I tried creating it with Rufus in pretty much all the UEFI modes. When in UEFI only it will appear on boot list, but trying to boot from it just causes a brief black flash and the BIOS reopens. If it is created in mixed mode the same happens, unless I choose the legacy USB mode and then it seems to install just fine. Same happens for USB created with the Windows tool - it seems to install properly.

To even make the Plextor drive visible from BIOS I use it in SATA mode (apparently in ASUS language "M.2" means "don't use M.2", so if M.2 interface is selected in advanced BIOS settings the drive is not visible. So it is running in SATA mode and the Plextor welcome screen show properly during boot, it is also visible from BIOS and on the list of bootable devices. However if I choose to boot from the drive (after seemingly installing Win 10 on it) a carret (underscore) flashes briefly a few times on the screen and I land back in BIOS.

Did anyone have a problem like that? Did you manage to fix it? I'm halfway set on just ditching the effing M.2 and buying a regular SATA SSD :/

This film shows what happens when I try to boot from M.2 with "installed" Win 10 on it. The BIOS settings are default, Win 10 was NOT installed from UEFI USB as my bios just doesn't seem to allow it. You can see at the beginning what happens. Afterwards I try to switch
CSM to auto - again with no result.

(Sorry for the very special music, it was the only way to remove the background noise :) )

[video="https://www.youtube.com/watch?v=TUMEaCPhsEE"][/video]

 
Solution
Thank you.

I actually did get it to work in the end, not quite sure how. I did disconnect the SATA HDD. I changed some settings in BIOS (I am now mortally afraid of going there again) and tried to run it from the Rufus USB stick with no luck. Then I tried running it again from the standard Windows Tool one and lo and behold, it gave me the UEFI option. It went smoothly from then on. I still don't know exactly what made it work.

I am a bit jarred by this experience. Tech was supposed to get more mature and grown up, not more tinker-y and hit and miss.

dgingeri

Distinguished
Try this:
1. disconnect any and all other SATA or USB devices except the keyboard, mouse, install USB drive, and the NVMe drive.
2. boot up and see if it gives you the option to boot to the USB install drive, if so, boot from that
3. See if the installer lets you install to the NVMe drive, if so, do the install. This step should assign the NVMe drive in the UEFI secure boot config as the main boot device
4. once the OS is installed, check the bios to make sure that the boot sequence is "Windows Boot Manager" (or something like that. I can't remember the specific term Asus uses there.) and nothing else in the entire boot sequence.
5. see if the OS boots properly. If so, shut down and connect all your other drives and devices.
 

Nurglitch

Commendable
Jan 29, 2017
2
0
1,520
Thank you.

I actually did get it to work in the end, not quite sure how. I did disconnect the SATA HDD. I changed some settings in BIOS (I am now mortally afraid of going there again) and tried to run it from the Rufus USB stick with no luck. Then I tried running it again from the standard Windows Tool one and lo and behold, it gave me the UEFI option. It went smoothly from then on. I still don't know exactly what made it work.

I am a bit jarred by this experience. Tech was supposed to get more mature and grown up, not more tinker-y and hit and miss.
 
Solution