X:\windows\system32>wmic /namespace:\\root\microsoft\windows\storage path msft_disk get Model,BusTypeĬopyright (C) 1999-2013 Microsoft Corporation. Volume 1 SYSTEM FAT32 Partition 260 MB Healthy Hidden Volume 0 N Windows NTFS Partition 232 GB Healthy Volume # Ltr Label Fs Type Size Status Info NUC10i3FNK with Crucial MX500 M.2 SATA SSDĭisk ID: In each scenario the USB key is removed prior to running the diskpart or wmic commands. I have collected information relating to how the devices are detected on v3.1, using a NUC10i3FNK with M.2 SATA and M.2 NVMe. If the device in the M.2 socket is an NVMe, the M.2 Device is Disk 1 and the USB key is Disk 0.
Using the same driver set, and WinPE v3.1, booting via USB with a board where the M.2 socket has a SATA SSD, the M.2 device is Disk 0 and the USB key is Disk 1. I'm trying to install a Samsung 970 evo plus 1tb on the bottom M.2 nvme slot of my Z490-E Gaming because I prefer my graphics card on the upper PCI-E slot (so the graphics card is making the upper nvme slot inaccessible).
Some NVMe SSDs like Samsungs 950 Pro SSD are natively bootable in LEGACY mode.
I then located an INF-version of the Samsung 950 NVMe Controller Driver on the Interweb, in a form suitable for pointing to and loading at Win7 install initialization time. Using a fixed driver set, WinPE v3.0, booting via USB with a board where the only disk installed is in an M.2 socket, either SATA SSD or NVME, WinPE will give the M.2 device Disk 0 and the USB key Disk 1. I wanted to know where I can find the firmware of this disk to try to reinstall it. The issue has been seen on 5 different boards so far, two different chipset manufacturers and 3 different board manufacturers. After much testing it appears that current WinPE detects an NVMe in an m.2 socket as a different type of disk (as expected) but then gives priority to other interfaces when it comes to disk numbering. So here is the proof that Windows will load the AMD RAID driver onto a non-AMD controller because it is loading it for the storage device and not the controller. While unknown as to what version this issue started with, the problem is replicated in WinPE v3.1 but is not replicated in v3.0. So rcbottom.inf is loaded on the physical hardware device for the NVMe, and then the NVMe (as a disk that can have volumes) is loaded under disk.inf.