[SOLVED] Dell M2 NVMe PCIE drivers for Windows 10 install not found
- Thread starter EctoBoggan
- Start date
bseklecki_ge
Member
It is just not clear to me why, When Dell repackages Intel RStT, they include two copies: F6 and Non-F6.F6 drivers are for WinPE, it's from hitting F6 to load drivers from the floppy. Everyone has a driver floppy.
bseklecki_ge
Member
To be clear: 1) Is it a supported config and 2) Has anyone successfully accomplished - Integrate the F6 VMD and F6 Non-VMD drivers into a WinPE/Setup/Boot.wim image? and 3) Should one Cross-apply those same F6 drivers into the main image/Install.wim ?
bseklecki_ge
Member
Ignore my last question:
(For the purposes of Google'able questions/answers) My problem is that Intel RST Version [v16.8.4.1011] seems to be the last version that will successfully integrate into [Windows 10 EntIOT LTSC 2019 (v1809)]
Later versions will silently fail to integrate and give an ambiguous numerical error code (iaStorAfs.sys 0xc0000098 ) at boot time.
The Intel and Dell release notes to explicitly mention the change in supported OS Build/Kernel version.
(For the purposes of Google'able questions/answers) My problem is that Intel RST Version [v16.8.4.1011] seems to be the last version that will successfully integrate into [Windows 10 EntIOT LTSC 2019 (v1809)]
Later versions will silently fail to integrate and give an ambiguous numerical error code (iaStorAfs.sys 0xc0000098 ) at boot time.
The Intel and Dell release notes to explicitly mention the change in supported OS Build/Kernel version.
Last edited:
F6 drivers have the basic functionality. You don't get any extras, like dashboards, agents or services.
bseklecki_ge
Member
Okay in that case, one would assume that the DLLs and SYS files would be a different size/crypto checksum in the non-F6. I'll check. Or maybe the mere presence of the EXEs .
But in that case, if one were using NTLite, with different XMLs for modifying WinPE/Boot and Win1x/Install, one would want to have the XML Drivers section reference the same extracted dell set, but with WinPE XML pointing to F6 version.
Alternatively, just automate the silent complete reinstallation of the RST package after the 1st OS boot/login is completed to add all the extra bells and whistles.
But in that case, if one were using NTLite, with different XMLs for modifying WinPE/Boot and Win1x/Install, one would want to have the XML Drivers section reference the same extracted dell set, but with WinPE XML pointing to F6 version.
Alternatively, just automate the silent complete reinstallation of the RST package after the 1st OS boot/login is completed to add all the extra bells and whistles.
Okay, so he solved his problem. But I chime in to add that Kasual is correct here. My Win8.1 box is AMD with AMD soft-RAID. I had to remove all the standard storage device drivers from the .wim in order for Win8.1 to see the RAID.
Not only that, but one has to go the extra step of "Reapply[ing] tasks across editions," removing the OEM drivers from the boot.wim in NTLite and integrating the new driver.
Not only that, but one has to go the extra step of "Reapply[ing] tasks across editions," removing the OEM drivers from the boot.wim in NTLite and integrating the new driver.
bseklecki_ge
Member
For the purposes of Google-indexed support forums:
I took the time and went back and confirmed this:
I can consistently cause this [0xc0000098 iaStorAfs.sys] BSOD error in Setup by attempting to integrate any version of Intel RST F6 drivers newer than v16.x ( For example [v16.8.4.1011]) into Windows 10 LTSC 2019 (Version/Build v1809)
So v16.8.4.1011 seems to be the last version that will integrated to v1809
Later versions versions integrate just fine into LTSC 2021 (v21H2)
This is just rubbish Intel release notes / documentation; maybe someone has a cousin that works there ?
Update: This also appears to be true of WinPE (For example, Acronis TrueImage, Acronis SnapDeploy, Windows WDS/PXE Booting, etc.)
Last edited:
You need the correct driver. Dell has two driver sets, w/ and w/o VROC support. Intel has a similar set of drivers.
Without knowing the exact model M2, it's not going to be obvious. Unless your vendor has specific instructions, some trial & error may be involved until you get one that boots up correctly.
Without knowing the exact model M2, it's not going to be obvious. Unless your vendor has specific instructions, some trial & error may be involved until you get one that boots up correctly.