Finding Lenovo drivers and certify hardware, control freak style

Posted on September 27, 2014 · Posted in Lenovo Driver Article

There are several techniques offered to find drivers and certify a fresh hardware model. Here follows the tactic I normally use. For instance I’m certifying the favorable old ThinkPad T420 from Lenovo for Windows 7, however , you can follow this process for just about any Lenovo model or Windows based pc. The overview steps will be the following:

Deploy a clean Windows 7 or Windows 8 image
Identify the missing drivers
Download the missing drivers
Verify the drivers work on the device
Identify if any driver applications are required, hotkeys etc.
Download any needed driver applications and verify which they work with the device
Note 1: Lenovo can give you with model specific guides concerning how to install a clean Windows 7 installation (see but I need to to present you a generic guide, that actually works for just about any hardware or Windows based pc. And without each of the vendor crap-ware.

Note 2: Lenovo initiated a policy of for making deployment-ready packages for a lot of than it’s models (ThinkCentre M82, M92, M92p and ThinkPad Helix, X1 Carbon, L430, L530, X131e, T430, T430i, T430s, T430si, T530, T530i, W530, X230 Tablet, X230i Tablet, T430u, X230s, and T431s). Lenovo store these packages about the Microsoft System Center Configuration Manager (SCCM) and Microsoft Deployment Toolkit (MDT) Package Index page, but as of this writing (August 2013), no packages are for sale to the ThinkPad T420.

Deploy a clean Windows 7 or Windows 8 image

For hardware testing I typically utilize a MDT 2012 Update 1 offline media which I deploy from your USB stick, since it allows me to lay down a clean Windows image within 5 – 7 minutes (assuming SSD). However , you is able to use any deployment solution you prefer provided that it’s automated.

Identify missing drivers

After deploying a clean Windows image towards the Lenovo ThinkPad T420 you need to determine if any drivers are missing. You may either just open device manager and search, or use PowerShell to uncover which drivers are missing. The goal is to learn it ID(s) with the devices which might be missing drivers. For the glance, using device manager is fine, nevertheless , you can really do magic using PowerShell.

Note: Together with missing drivers I investigate Display driver too, to find out if Windows found a “real” driver instead of the Standard VGA driver.

After deploying the clean Windows 7 image to my ThinkPad T420 device manager show the following (realize that I expanded the Display adapters node):


Device Manager after deploying a clean Windows 7 image.

To discover more on it ID to get a device missing a driver you only right-click, select properties, click the Details tab, and choose the Hardware Ids Property.


Device Manager displaying Hardware Ids for “Base System Device”.

Why don’t you consider PowerShell? It’s now possible simply ask the Win32_PNPEntity class for devices that are not configured by running the below one-liner within a PowerShell prompt:

Get-WmiObject Win32_PNPEntity | Where-Object$_.ConfigManagerErrorCode -ne 0 | Select Name, DeviceID


If you would like get fancy, and output the info with a text file, you just add Export-Csv to the command:

Get-WmiObject Win32_PNPEntity | Where-Object$_.ConfigManagerErrorCode -ne 0 | Select Name, DeviceID | Export-CSV C:\Drivers.csv

Drivers CSV

To determine when the Standard VGA driver is being used, you need to use the below command:

Get-WmiObject Win32_PNPEntity | Where-Object$_.Name –Match “VGA” | Select Name, DeviceID


Anyway, it doesn’t matter if that you were using Device Manager or PowerShell you now have a list of device drivers. The secret is to truncate the Hardware Ids to simply included Vendor and Device information, because that will serve learning what device it is when looking for it. As search providers I normally use the Microsoft Update Catalog site ( or maybe plain Google/Bing. Here follows several truncate examples:

PCI\VEN_8086&DEV_0084&SUBSYS_13158086&REV_00\4&306CAAFA&0&00E1 becomes PCI\VEN_8086&DEV_0084
ACPI\LEN0068\5&2890D699&0 becomes ACPI\LEN0068
Then you definately grab the truncated value and search for it. Here follows a good example searching the Microsoft Update Catalog site for the ACPI\LEN0068 device. The actual result says to you which the device can be a Lenovo PM (Power Management) Device.


Searching the Microsoft Update Catalog site.

After in search of every one of the devices it’s simple to compile a quick list with valid named from the devices which are missing drivers. This is actually the listing with the ThinkPad T420.

PCI\VEN_8086&DEV_0116 = Intel HD Graphics 3000
PCI\VEN_8086&DEV_0084 = Intel driver update for Intel(R) WiFi Link 1000 BGN
ACPI\LEN0068 = Lenovo Power Management Device
PCI\VEN_8086&DEV_1C22 = Intel 6 Series/C200 Series Chipset Family SMBus Controller (Synaptics)
USB\VID_147E&PID_2016 = TouchStrip Fingerprint Sensor (AuthenTec)
PCI\VEN_8086&DEV_1502 = Intel 82579LM Gigabit Network Connection
PCI\VEN_8086&DEV_1C3A = Intel Management Engine Interface (MEI)
PCI\VEN_1180&DEV_E823 = Ricoh PCIe SDXC/MMC Host Controller