Welcome to DriverPacks!
I tried using pnputil last year, but it has some serious (IMHO) problems.
Quote taken from here: http://technet.microsoft.com/en-us/libr … 10%29.aspx
Drivers that are located in the path specified by DriverPaths are copied to the driver store ...
So this continues the problem of driverstore bloat. What I use in my SAD2 script is the Microsoft tool dpinst.exe. There are two versions (incompatible with each other) for 32 & 64 bit OS.
Where dpinst excels is that it only installs drivers for the hardware that is present during execution.
About 95% of my script deals with OS detection, path resolution, and driverpack extraction.
The "meat & potatoes" line that gets the drivers loaded is right here:
Start "MicroSoft Driver Installer Tool Running" /wait /separate /realtime /min CMD /C DPInst.exe /c /s
But in order for this to work, dpinst needs to be copied to the root of the folder containing all the drivers.
The batch-script line I was experimenting with for pnputil usage was this:
:: pnputil -a -i %SystemDrive%\D\*\*.inf
But again, this loads ALL the detected drivers into the driverstore. The drivers remain there, even after first install. That's a VERY significant file bloat. Depending on how many DriverPacks you use, that folder may exceed 3 GB in size.