![]() ![]() ![]() 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. ![]() 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. 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. 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. ![]()
0 Comments
Leave a Reply. |