Driver Integration on Z170 System

Hi,
this is my first post here, but I’m using Win7PE SE for several years now without any major problems. I have bought a new computer recently, so I downloaded the latest Win7PE package and adapted it to my system. Everything is working fine except the driver integration / detection.

I integrated the following drivers with the Driver Integration Script (DISM)

-   SATA driver for the Intel 100 series => works
-   SATA driver for the ASmedia  => works
-   NVMe driver for the Samsung 951 =>  code 38 error
-   NIC driver for Killer 2400 => works
-   NIC driver for Intel 219-V => code 38 error
-   USB 3.0 driver => works
-   USB 3.1 driver  => works
-   AUDIO driver => works
-   Intel  INF driver => works mostly, but not a problem
-   Intel MEI driver => missing file, but not a problem

The result after booting up Win7PE is always the same. The NVMe and Intel 219-V drivers are not properly installed (code 38), which means my boot drive isn’t accessible and a network connection via the Intel NIC not possible. The general solution for solving code 38 is to reboot the system, which isn’t really option with a WindowsPE.
I have tried several different builds: Only the NIC drivers, only the SATA drivers, only the drivers which are causing the problems, but the error code won’t go away.  A workaround for the NVMe driver is not to integrate it and install it via device manager on a running Win7PE

So I wondering if someone else here with a Z170 System has the same problems…

PS: There are also issues with Win10PE regarding driver integration, but they differ from the ones with Win7PE.

Welcome Unikat2000,

You can maybe give a try to Dism or Double Driver export function, available in Driver Integration for both drivers.
And for NVMe driver installed via device manager on a running Win7PE, you can try an export with Double Driver or other from there.

Hi Chris,

I tried the double driver tool, but it leads to the same result. Maybe I forgot to mention, that I have already the extracted driver files  (inf / dll / sys / cat)  and had put them into the  Drivers_x64 for integration.  As far as I know double driver just copy these files from my current windows installation.

The questions in my case are: Is this a general problem of WinPE or some specific drivers issue?

Microsoft Windows 7 did not originally support NVME ssd's. No NVMe SSD at that time.
Microsoft has released a NVMe patch.
Update to add native driver support in NVM Express in Windows 7 and Windows Server 2008 R2
By cons, for Win7pese, I do not know. Add the package to Win7 and also, you probably need to capture the change to know what to add for PE.
It is probably easier with Win10PE.


I tried in Win7pese, the driver integration for the NIC x64 driver for Intel 219-V.
 e1d62x64.7z (292.23 kB - downloaded 112 times.)
It ends successfully. But I do not know for the detection at runtime.

Hi Unikat2000,

You should be able to use the Method 1 (link above) to insert native driver support for NVM Express hotfixes in Windows 7 source in a first time.
It is then probably enough at build time, without other additions.
boot.wim folders: Windows\Drivers, DriverStore, inf and registry hives are fully copied with Classpnp.sys, stornvme.sys, storport.sys drivers included.
 

Hi Chris,

i will try integrating the patches (there is also a fix for KB2990941 => KB3087873)  into the win7 source.    You say into boot.wim and not install.wim?

Without the hardware, I have not tried.
I just looked at the result of Add-Package KB2990941 in boot.wim index 2

To try on boot.wim index 2 with mounted wim folders. Or on your extracted wim folder (boot.wim or winre.wim), if you use.
Perhaps it is enough without touching Install.wim, Let us know.

Hi Chris,

after some testing I can confirm that a boot.wim (index 2) with integrated (KB2990941 + KB3087873) contains the generic nvme driver. When used as source for Win7PE the driver will part of the driverstore. On a running Win7PE I can now access the NMVE drive. But the orginal Samsung driver still causes malfunction "code 38" in the device manager and the same issue for the Intel 219-V.

Well in my opionion there are two possible reasons 

a) the drivers or their INF files are  somehow messed up

b) WindowsPE cannot handle these drivers

Do you have the same samsung drivers as here http://www.win-raid.com/t29f25-Recommended-AHCI-RAID-and-NVMe-Drivers.html ?
Section H. Samsung NVMe Drivers: 32/64bit Samsung NVMe Drivers v1.4.7.17 WHQL for Win7 x86/x64

yeah that's the source for all my drivers regarding integration  (NVME / SATA / USB 3.x) over the years.....

The Samsung NVME drivers (when not BSOD'ing) require a reboot after initializing. I pulled the drivers from an existing OEM W7 install to test. The drivers would load, the drive would come up. Then the drive would unmount and not show up in diskpart. Checking the properties, "A reboot is required". Due to time table pressure we shelved W7 for these machines and moved on with W10. You might need to capture what the Samsung installer does after install.

hi,

where do you see "A reboot is required" ? When I add the nvme driver manually via the device manager the drive is recognzied and accessible. I didn' t notice that it unmounts shortly afterwards. in my configuration the problem occured the with automatic driver loading.

As I made a test with the Microsoft NVMe driver in the other thread I also made a test with integrated Samsung device driver.
With driver integration through 'dism' I could access normally my NVMe system drive ("C:") directly after booting into PE, so it seems that driver integration for 7PE is also best made with 'dism'.
I wrote a small script and will post it if it is still needed.
Greets
Holger

[Edit]: Forgot - I did not use the 'Driver integration' script but my own simplyfied script. I think I saw an Intel 219-V somewhere at work, will test it there.