I wrote before about the Peimg tool and its ability to let you inject drivers into an offline Windows PE image. There is another tool provided for installing drivers to a booted Widnows PE image. This tool is Drvload and it can be helpful in loading drivers that might give you trouble when trying Peimg.

If you are automating things in your image startnet.cmd is a logical place for this command-- before or after the wpeinit call would depend upon if you were loading a nic driver or not.

The only parameter you need pass it is the path to an .inf file (which should obviously be in a folder with any required source files it depends upon). If the driver. sys file requires a reboot, you won't be able to use Drvload, but if it is the inf you supply that is requesting a reboot, Drvload will ignore it.

One cool thing about it is that you can load multiple drivers in a single command line, but specifying multiple .inf files (separated by comma's). Wildcards are not supported.

As you would expect, if any drivers failed to install non-zero %errorlevel% value (zero for success).

Note: This tool replaces the earlier drvinst command line tool from earlier releases of Windows PE.