Well it is finally here, the latest update to the Driver Automation Tool. Sorry this has taken a while to put together but there have been significant changes to both the tool in this build, all of which is thanks to community interaction. In fact the Driver Automation Tool reached something of a milestone recently, with over 20k downloads in the first year of becoming available, so thank you everyone!

So lets go through the list of feature changes:

Graphical Redesign

The new version gets rid of the previous list boxes used for model listings and selected models in favor of a data grid format, this should be more intuitive to use and now includes the ability to search for specific models within the list. This has taken a considerable number of hours to complete, however I think the tool now feels more functional for it.

Below is an example showing the results for a search for ProBook models against the HP model list:

HP Driver Catalogue

In response to those of you using HP hardware and who have mentioned about the fact things like hotkey support require additional drivers, I have added a new tab – HP Driver Catalogue. Here you will see a full list of all additional drivers available based on the OS selection. This way you can automate the download and packaging of those additional drivers;


Note that we will be updating our GitHub scripts section with an automated script to install the content. It is also worth noting that the XML file used for the drivers is around 25MB so it can take a few moments to download

Package Folders

One of the main topics that kept coming up was the fact that the tool created packages in the root folder. So in this version, both drivers and BIOS downloads will create their own folder structure within the packages folder based on the following naming – Driver/BIOS Packages\Make


Revised Settings Tab

Now all of the settings which were previously spread out over several sections are now contained within the ConfigMgr Settings page.

Note: For MDT and download only jobs you will still need to specify the storage locations on the ConfigMgr Settings tab

Storage Location Changes

As requested BIOS packages will now be created in the same location as driver packages.


There are a number of minor fixes in the latest release, most noticeably are is a fixes for packages not distributing correctly after creation, and for Dell Precision Tower model downloads.

Download Link

The Driver Automation Tool can be downloaded from Microsoft Technet – https://gallery.technet.microsoft.com/Driver-Tool-Automate-9ddcc010 




Maurice Daly

Maurice has been working in the IT industry for the past 18 years and currently working in the role of Principal Consultant with TrueSec. With a focus on OS deployment through SCCM/MDT, group policies, active directory, virtualisation and office 365, Maurice has been a Windows Server MCSE since 2008 and was awarded Enterprise Mobility MVP in March 2017.

  • Maro
    Posted at 17:39 March 29, 2018

    Hello, This is a great tool, but we found that the Lenovo driver packages that it downloads, do not download the latest drivers for said model. Is there a way to grab the latest drivers per model for Lenovo Systems?

    • Greg
      Posted at 18:45 March 31, 2018

      That’s a Lenovo problem. They release new drivers but don’t update their catalog right away:


      Guessing it’s by design, it’s not uncommon to see this, even from other manufacturers. Drivers release all of the time, catalog probably updates monthly or quarterly

  • Roger G.
    Posted at 21:05 March 29, 2018
    Roger G.

    Thank you for all your hard work, these changes look great! Can’t wait to use the updated version.

  • Jesse Walters
    Posted at 22:13 March 30, 2018
    Jesse Walters

    I would love to use your tool for MDT with automated BIOS downloads too.

  • Roger Truss
    Posted at 20:55 April 2, 2018
    Roger Truss

    Love the new update, except for one thing. I cannot seem to change the proxy config in the UI. Tried locally on my workstation (win 10 1709) and server (2016).

  • Leave a Reply