Finding and adding only the correct device driver to the Boot image

It seems to me, people tend to add way to many drivers to their boot images, which in some cases make WinPE unstable, and subsequent make the Deployment fail. It also makes it near impossible to figure out which driver versions/types are actually included, as that info is kind of limited from within the Boot Image node itself …

What I do, is find the exact drivers needed for my WinPE environment to work on the specific model(s), and add only those drivers.. If I Can boot WinPE, and gain access to the network (IPCONFIG) and hard disk (DISKPART – list disk), I do not update my boot image, even if I choose to add a new NIC to the deployed OS itself!

In this example I will use a DELL latitude E6320, because this particular machine has a network driver not already included in WinPE.

The first thing to do is go into the device manager and check which driver the network card is using. I usually do this from the Win7 preloaded OS that comes with the machine (you know! before reinstalling). If this is not an option, you can do something similar from within WinPE using DrvLoad.exe, and wmic, but more about that in a later post!!

As you can se from the picture, the Network adaptor is using an Intel® 82579LM Gigabit Network Connection driver.


The problem you then run into, is that, this is not the name of the driver in the Intel driver package. The driver is defined as an INF and the actual name of the driver is found within the particular INF. To find the name of the INF you can check the driver details in properties of the driver. It will show you the SYS file which is always name the same as the INF


As you can see, the driver in question should be e1c6232.inf, and if you download the newest NIC driver package from Intel (or get it from your vendor), and open that driver in notepad (or in this case Notepad++), you will find the driver you need inside the INF.


Now the driver must be imported into ConfigMgr. Normally I would import all the NIC drivers, and the look for the same info from within ConfigMgr. Do an import only, no need to add to category, package or Boot Image, at this point. Once imported your NIC drivers will look something like this.

image ,

By highlighting the driver you can even see which other drivers are included, and which platforms it I applicable to:


You can see that this particular driver works on Windows 7 x86 SP1, and that it also supports Intel® 82579V Gigabit Network Connection.

The info corresponds to that found in the running OS, so it’s clearly the driver needed in the Boot image. Finally all there is left to do is inject and update DP, and the boot image should work like a charm.


By |2011-07-05T15:04:00+00:00July 5th, 2011|Hardware & Drivers, OS Deployment|13 Comments

About the Author:

Michael Petersen
Twitter: @OSDeployLinkedin: Michael PetersenMicrosoft Community Contributor


  1. Chris Nackers July 25, 2011 at 17:37 - Reply

    Excellent post, I constantly discuss this same issue with clients all the time.

  2. PWStrain July 26, 2011 at 6:58 - Reply

    I’ve taken to getting all the drivers working as you state, then using DriverMax and exporting everything that isn’t a default windows driver, then importing them into SCCM, adding the NIC and Storage drivers only if needed. Saved much time at a recent client with 41 different laptop / desktop models to re-image.

  3. […] I use this method… Finding and adding only the correct device driver to the Boot image – CoreTech Blog It seems to me, people tend to add way to many drivers to their boot images, which in some […]

  4. Chad July 28, 2011 at 23:49 - Reply

    The day before I saw your article I worked out a method of using the VEN & DEV ID to find the right drivers.

    select D.*, DHID.*, DM.* from v_CI_DriversCIs AS D
    inner join v_CI_DriverHardwareIDs AS DHID on DHID.CI_ID = D.CI_ID
    inner join v_CI_DriverModels AS DM on DM.CI_ID = D.CI_ID
    where DHID.HardwareID = ‘PCIVEN_8086&DEV_10BD’
    Order by HardwareID

  5. Mikael October 6, 2011 at 8:21 - Reply


    Great post.
    But, back in the old days, when using modems, there where always a generic driver for the modem. Made it possilbe to have a connection, not the best speed, but a connection.

    Why do not all the vendors, support for a generic NIC driver(10MB/s, full duplex) Ee all wouldnt hassel anymore with all the drivers in the WinPE?
    Since many vendors, do have the support within the WinPE, but some dont.


  6. Dustin Mobley January 31, 2013 at 16:00 - Reply

    How do you determine what Windows PE your enviornment currently is?

  7. 공공기관/언론사 – 언론사 전화번호…

    Coretech Blog » Blog Archive » Finding and adding only the correct device driver to the Boot image…

  8. blog May 12, 2014 at 21:23 - Reply

    Greetings! I’ve Been Following Your Website For A Long Time Now And Finally Got The Bravery To Go Ahead And Give You A Shout Out From Austin Texas! Just Wanted To Mention Keep Up The Good Job!

  9. February 12, 2016 at 5:23 - Reply

    Try to standardize your work outfit and, if
    it’s not too much for you, also your diet.
    In a sense, and although technically not 100 percent correct, it is to your phone what the BIOS
    is to your computer. This is easily done by connecting your phone to
    your computer or removing your SD card and using an adapter to copy or move items.

  10. Mackenzie April 29, 2016 at 15:25 - Reply

    You’ve got interesting articles here. Your website can go viral, you
    need some initial traffic only. How to get initial traffic???
    Search google for: Marihhu’s myblog

  11. Colin January 25, 2017 at 18:21 - Reply

    Thank you .. but, how does one go about accessing an Micro SD Drive from WinPE when the SD drivers are generic Microsoft ones but are not loaded by WinPE?

  12. Andrew September 2, 2017 at 3:19 - Reply

    Nice article, thanks

Leave A Comment