That incidentally is ANOTHER item that would have become clear from a screenshot since that information is displayed in the title bar along the top of the Rescue interface. The fact that you built Rescue Media from Windows 11 does not automatically mean you're using a Win11 kernel. It might also help to know which WinPE/RE kernel your Rescue Media is using, which CAN but does not NECESSARILY match the Windows kernel of the system from which it was built. The issue of Intel recycling the PCI DEV ID might be a factor. Now none of that explains why your particular Rescue Media doesn't seem to be loading the particular Intel Rapid Storage driver that was copied onto it.
So the strength of your conviction notwithstanding, this has nothing to do with M.2 or NVMe. And for the record, the Rapid Storage controller can even be used with “regular” SATA drives, where it can create this exact issue even there. If your system was capable of being put into AHCI mode, thereby disabling that controller and exposing the NVMe storage interface directly to the OS, then the standard NVMe class driver built into Windows kernels since Win8 / WinPE 4 would work just fine. That is an irritating design limitation of your particular system, because that then requires you to have the appropriate drivers for that controller. The hurdle you're encountering is the Rapid Storage controller, which apparently on your system cannot be disabled. But that has nothing to do with M.2 itself.īut it's actually not even NVMe that's the issue here. An M.2 NVMe SSD can be because NVMe is a newer interface. An M.2 SATA SSD is functionally no different from a "regular" 2.5" or 3.5" SSD.
M.2 slots can be designed to support SATA and/or NVMe SSDs. Do you even realize that the M.2 aspect itself is not a relevant factor? M.2 is simply a physical connector spec.
0 kommentar(er)
