Windows 10 driver injection doesn't install during sysprep

[Jonathan Cool]

Hi,

First, informations about my stuff :

Server :

FOG Version : Running Version 1.3.5-RC-8 ; SVN Revision: 6066
OS : Debian GNU/Linux 8

Specifications :

• all images are on a Synology NAS storage : mounted with NAS_ip:/images
• french user

I discover recently the drivers injection method with scripts fog.postdownloadscript and fog.drivers.
With Win7x64, it’s work by using the hack registry method to add C:\Windows\DRV in the DevicePath.
I read in this topic some people have troubles to inject drivers on a Win10x64 computer using this method.
I just realize quick test with 3 models (Optiplex7010, 820G1, HP8000) and it’s seem to works … :
Just after the deploy, i check if the C:\Windows\DRV contained files, check if the registry hack has been realize and i check if all drivers are installed …

Optiplex7010 :

• C:\Windows\DRV : OK
• registry hack : OK
• all drivers are installed

HP8000 :
i didn’t find Win10x64 drivers for this computer BUT after the deploy, i can see the registry hack has work …

HP820G1:

• C:\Windows\DRV : OK
• registry hack : OK
• some drivers are absents … maybe i forgotten some files when i created the folder drivers on NAS …

To conclude, i ask some questions to myself … this method work or this method NOT work for Win10x64 ? That’s is the question !

Enc : Screenshot of my Optiplex7010 results …
link text

[george1421]

@Jonathan-Cool said in Windows 10 driver injection doesn't install during sysprep:

To conclude, i ask some questions to myself … this method work or this method NOT work for Win10x64 ? That’s is the question !

I will tell you that you need to debug that HP8000 a little better, the scripts will copy the files if everything is correct.

That is different than if windows oobe will load the drivers. Step 1 is getting the drivers onto the target computer. Step 2 is telling windows where to find the drivers.

The registry hack will work for Win7.
The registry hack will NOT work for Win10. For Win10 you must update the unattend.xml file to tell it where to look for the drivers.

[Jonathan Cool]

i think there is a misunderstanding.
The HP8000 is an old computer and there is no drivers for the Win10 OS.
So, I didn’t copy any files in my FOG Drivers folder.
I ran a task with this computer just ONLY to see if the reg hack work.

[george1421]

@Jonathan-Cool said in Windows 10 driver injection doesn't install during sysprep:

So, I didn’t copy any files in my FOG Drivers folder.
I ran a task with this computer just ONLY to see if the reg hack work.

Not a logical test since: no files copied == no drivers loaded == reg key added but no valued added because nothing to load.

But I understand the logic behind your test.

[UWPVIOLATOR]

@george1421 @Wayne-Workman I am seeing this issue too on Win 1709 EDU. Sysprep isn’t looking in C:\Drivers even though unattended file is telling it to. Windows Update picks up some drivers but not all. If I go into Device Manager and manually point to C:Drivers it will load the driver for that one device.

What am I missing?

    <settings pass="offlineServicing">
        <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DriverPaths>
                <PathAndCredentials wcm:action="add" wcm:keyValue="1">
                    <Path>C:\Drivers</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>

[Tom Elliott]

@uwpviolator maybe this can help in general for everybody?

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-device-drivers-to-windows-during-windows-setup

[Tom Elliott]

There’s also this: https://docs.microsoft.com/en-us/windows-hardware/customize/desktop/wsim/add-a-device-driver-path-to-an-answer-file

[george1421]

@uwpviolator I ran into the same issue when I was working on our 1709 image (which was put on hold for the moment). I ended up with a hack to use dism in the setupcomplete.cmd to load in all of the drivers in c:\drivers directory.

[george1421]

@tom-elliott said in Windows 10 driver injection doesn't install during sysprep:

@uwpviolator maybe this can help in general for everybody?
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-device-drivers-to-windows-during-windows-setup

Interesting that one says to use WinPE instead of NonWinPE. That sounds counter intuitive, but if it works…

[UWPVIOLATOR]

@george1421 Are you able to share that info?

[george1421]

@uwpviolator Info?

What I saw was a contradiction between my settings

<component name="Microsoft-Windows-PnpCustomizationsNonWinPE"

and what Tom found in his first link

<component name="Microsoft-Windows-PnpCustomizationsWinPE"

The microsoft document said to use Microsoft-Windows-PnpCustomizationsWinPE which is counter intuitive to Microsoft-Windows-PnpCustomizationsNonWinPE from my guide. I have not had a chance yet to see of this location that Tom found actually works, being monday and all…

[UWPVIOLATOR]

@george1421 said in Windows 10 driver injection doesn't install during sysprep:

@uwpviolator I ran into the same issue when I was working on our 1709 image (which was put on hold for the moment). I ended up with a hack to use dism in the setupcomplete.cmd to load in all of the drivers in c:\drivers directory.

This is what I was referring to. How did you call this in the setupcomplete.cmd to pull drivers from C:\Drivers?

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-and-remove-drivers-to-an-offline-windows-image

[george1421]

@uwpviolator Ah, sorry. I thought you were talking about my last post.

Well it sucks getting old, I didn’t use dism (after looking at the code) this is what I used to force the drivers in.

REM Inject any missing drivers for hardware discovered during oobe
forfiles /p "C:\Drivers" /s /m *.inf /c "cmd /c pnputil -a @Path"

[UWPVIOLATOR]

@george1421 Testing that now. Both of the other ways did not work for me.

[UWPVIOLATOR]

@george1421 This seems to be working for me. I think I must be missing some drivers that I did not upload to FOG or my model doesn’t like 1709 which by a few forum post might be the case. M$ really screwed up with 1709. Its like the Vista of the Win 10 builds.

[george1421]

@uwpviolator I’ve found that I need to call that pnputil 2-3 times to find all hardware hidden behind other hardware.

I agree that 1709 did some bad things to the non SCCM image cloners.

[UWPVIOLATOR]

@george1421 So in setupcomplete.cmd should I tell it to sleep for a period of time between the command or do you just do

REM Inject any missing drivers for hardware discovered during oobe
forfiles /p "C:\Drivers" /s /m *.inf /c "cmd /c pnputil -a @Path"
forfiles /p "C:\Drivers" /s /m *.inf /c "cmd /c pnputil -a @Path"
forfiles /p "C:\Drivers" /s /m *.inf /c "cmd /c pnputil -a @Path"

Also can I do about non .inf that want to be installed? Example HP Hot Key to make keyboard FN keys work?

[george1421]

@uwpviolator Putting a 5 or 10 second sleep would not hurt. That would give the drivers a chance to init before you make pass Next.

As for self installers, I would tag them onto the end of the setupcomplete.cmd file. Just make sure you are sure of the silent install switches.

I do something a bit more complex with my setupcomplete.cmd I have it check for a certain batch file name in the c:\drivers directory. If that batch file exists I call that batch file towards the end of the setupcomplete.cmd file. Remember that directory comes from the fog server with hardware specific drivers. Well if there are self extracting .exe installers in the driver pack that are hardware specific I include them in the driver directory on the fog server. Those get copied over and the setupcomplete.cmd file will call the batch file in the c:\drivers directory which installs the hardware specific .exe drivers and applications.

[UWPVIOLATOR]

@george1421 Do you mind sharing that part of you setupcomplete? I am still checking to see if the driver I am missing is just a inf but this could be helpful in the future.

[george1421]

@uwpviolator Sure no problem, but I hate to disappoint you the stuff is not very sexy.

In the setupcomplete.cmd file I have this line.

if exist "c:\drivers\drvinstall.cmd"  call "c:\drivers\drvinstall.cmd"

If we have .exe type drivers that we need to install on the target computer then we will place the .exe files in the drivers directory with the drvinstall.cmd batch so they are copied to the target computer when the rest of the .inf drivers are copied over.

Here is an example of a drvinstall.cmd batch file.

@echo off
echo Please wait wile we install some things you'll need
%~dp0\Bluetooth\Setup.exe /quiet /passive /norestart
%~dp0\WiFi\setup.exe -quiet -passive -norestart 

One other (new) thing is we looked at how we were installing the drivers via pnputil. We have a bit cleaner command syntax.

pnputil.exe /add-driver "c:\drivers\*.inf" /subdirs /install