DIFx deprecation

%3CLINGO-SUB%20id%3D%22lingo-sub-132894%22%20slang%3D%22en-US%22%3EDIFx%20deprecation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132894%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20extensively%20used%20dpinst%20from%20the%20Microsoft%20Windows%20Driver%20Kit%26nbsp%3Bfor%20my%20Windows%207%20and%20Windows%2010%20deployments%20to%20allow%20building%20a%20universal%20image%20and%20I%26nbsp%3Brealize%20that%26nbsp%3Bdpinst.exe%20is%20no%20longer%20available%20in%20the%20Microsoft%20Windows%20Driver%20Kit%20as%20of%26nbsp%3BWin10AU.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIs%20pnputil%20intended%20to%20be%20the%20replacement%20tool%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20use%20dpinst%20in%20my%20unattend.xml%20as%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CRUNSYNCHRONOUSCOMMAND%20action%3D%22%26quot%3Badd%26quot%3B%22%3E%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CORDER%3E1%3C%2FORDER%3E%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CDESCRIPTION%3EDriver%20Installation%20Pass%201%20of%203%3C%2FDESCRIPTION%3E%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CPATH%3E%22C%3A%5Ctemp%5Cdrivers%5Cdpinst.exe%22%20%2Fpath%20%22C%3A%5Ctemp%5Cdrivers%22%20%2Fq%20%2Fse%3C%2FPATH%3E%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3C%2FRUNSYNCHRONOUSCOMMAND%3E%3C%2FP%3E%0A%3CP%3EYes%20three%20passes%2C%20to%20ensure%20daughter%20and%20grand-daughter%20devices%20get%20found.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20joy%20of%20dpinst%20is%20it%20only%20installs%20what%20is%20needed.%26nbsp%3B%20Using%20the%20same%20logic%20with%20pnputil%20as%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Efor%20%2FR%20%22c%3A%5Ctemp%22%20%25i%20in%20(*.inf)%20do%20pnputil%20-i%20-a%20%22%25i%22%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPnputil%20adds%20ALL%20drivers%20it%20finds%20to%20the%20Driver%20FileRepository%2C%20then%20detects%20and%20installs%20which%20slows%20the%20process%26nbsp%3Bdown%20and%20takes%20up%20unnecessary%20space%20when%20deploying%20a%20universal%20image.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWill%20dpinst%20ever%20come%20back%20to%20the%20land%20of%20living%20code%3F%20or%20rather%2C%20please%20update%20it%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132955%22%20slang%3D%22en-US%22%3ERe%3A%20DIFx%20deprecation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132955%22%20slang%3D%22en-US%22%3E%3CP%3EMy%2010GB%20driver%20pack%20contains%20drivers%20for%20two%20dozen%20make%2Fmodels%20of%20systems.%26nbsp%3B%20The%20problem%20with%20building%20the%20drivers%20into%20the%20image%20prior%20to%20deployment%20is%20that%20it%20bloats%20the%20image.%26nbsp%3B%20It%20even%20runs%20the%20risk%20of%20poisoning%20the%20image%20by%20bloating%20the%20registry%20with%20hundreds%20of%20unneeded%20entries.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBy%20installing%20the%20drivers%20at%20deployment%20from%20a%20cache%2C%20only%20a%20small%20amount%20of%20space%20is%20permanently%20used.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAlso%2C%20by%20leaving%20Windows%20to%20do%20its%20thing%20by%20installing%20drivers%20in%20its%20own%20time%2C%20it%20leaves%20the%20system%20in%20an%20undesirable%20state%20for%20the%20first%20user%20logon%3B%20which%20we%20use%20as%20an%20auto-logon%26nbsp%3Bto%20install%20hardware-specific%20OEM%20software%20which%20often%20times%20cannot%20complete%20because%20it%20is%20waiting%20on%20hardware%20to%20be%20detected%20by%20Windows%20and%20drivers%20to%20be%20loaded.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBy%20forcing%20driver%20installation%20on%20my%20terms%20during%20unattend.xml%20using%20dpinst%20I%20ensure%20that%20all%20hardware%20devices%20are%20loaded%20when%20I%20want%20them%2C%20not%20when%20Windows%20gets%20around%20to%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132925%22%20slang%3D%22en-US%22%3ERe%3A%20DIFx%20deprecation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132925%22%20slang%3D%22en-US%22%3E%3CP%3EDPInst%20was%20intended%20for%20driver%20testing.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20believe%20you%20can%20achieve%20what%20you%20want%20using%20PowerShell%20with%20the%20%22Add-WindowsDriver%22%20cmdlet%20with%20the%20%22-Recurse%22%20option.%26nbsp%3B%20There%20is%20also%20a%20command-line%20option%20with%20%22DISM%20%2FOnline%20%2FAdd-Driver%20%2FDriver%3A%3CFOLDER%3E%20%2FRecurse%22.%3C%2FFOLDER%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I have extensively used dpinst from the Microsoft Windows Driver Kit for my Windows 7 and Windows 10 deployments to allow building a universal image and I realize that dpinst.exe is no longer available in the Microsoft Windows Driver Kit as of Win10AU.

 

Is pnputil intended to be the replacement tool?

 

I use dpinst in my unattend.xml as:

                <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Description>Driver Installation Pass 1 of 3</Description>
                    <Path>"C:\temp\drivers\dpinst.exe" /path "C:\temp\drivers" /q /se</Path>
                </RunSynchronousCommand>

Yes three passes, to ensure daughter and grand-daughter devices get found.

 

The joy of dpinst is it only installs what is needed.  Using the same logic with pnputil as:

 

for /R "c:\temp" %i in (*.inf) do pnputil -i -a "%i"

 

Pnputil adds ALL drivers it finds to the Driver FileRepository, then detects and installs which slows the process down and takes up unnecessary space when deploying a universal image.

 

Will dpinst ever come back to the land of living code? or rather, please update it?

 

 

2 Replies

DPInst was intended for driver testing.

 

I believe you can achieve what you want using PowerShell with the "Add-WindowsDriver" cmdlet with the "-Recurse" option.  There is also a command-line option with "DISM /Online /Add-Driver /Driver:<folder> /Recurse".

My 10GB driver pack contains drivers for two dozen make/models of systems.  The problem with building the drivers into the image prior to deployment is that it bloats the image.  It even runs the risk of poisoning the image by bloating the registry with hundreds of unneeded entries.

 

By installing the drivers at deployment from a cache, only a small amount of space is permanently used.

 

Also, by leaving Windows to do its thing by installing drivers in its own time, it leaves the system in an undesirable state for the first user logon; which we use as an auto-logon to install hardware-specific OEM software which often times cannot complete because it is waiting on hardware to be detected by Windows and drivers to be loaded.

 

By forcing driver installation on my terms during unattend.xml using dpinst I ensure that all hardware devices are loaded when I want them, not when Windows gets around to it.