Driver Automation ToolDriver Automation Tool

Minimum supported version: The Driver Automation Tool now requires v10.1.9.0 or later as of 17 August 2026 due to functional changes. Older versions can no longer connect to the API — please upgrade to continue.

Setup Guide

Step-by-step instructions to download, install, configure, and start using the Driver Automation Tool.

Getting Started

Follow these steps to download, extract, and launch the Driver Automation Tool for the first time.

Prerequisites & System Requirements

Before installing, ensure the host machine meets the following requirements. The tool runs entirely locally in PowerShell and needs administrative rights for registry and imaging operations.

OptionDescription
Driver Automation Tool versionv10.1.9.0 or later is required to connect to the API — older clients are blocked (HTTP 426) and prompted to upgrade
Operating SystemWindows 10 or later, or Windows Server 2016 or later
PowerShellWindows PowerShell 5.1 (built-in) or PowerShell 7+
Administrator PrivilegesRequired — settings are stored in the HKLM registry and DISM WIM operations need elevation
Disk SpaceSeveral GB of free space in temporary storage; varies by OEM/model selection
Internet AccessRequired to download OEM catalogs and driver/BIOS packages

Required PowerShell Modules

Depending on which OEMs and deployment platforms you use, the following modules must be installed. Missing modules cause the relevant integration to silently fail.

OptionDescription
HPCMSLHP Client Management Script Library — required for HP catalog parsing and SoftPaq discovery. Install-Module -Name HPCMSL
ConfigurationManagerShips with the ConfigMgr console — required for Configuration Manager integration
Microsoft.GraphRequired for Microsoft Intune integration (Graph API)
HP support: the HPCMSL module is required for HP catalog parsing and SoftPaq discovery — HP models will not appear without it. Install it from an elevated PowerShell session with Install-Module -Name HPCMSL.
Minimum supported version: the Driver Automation Tool requires v10.1.9.0 or later to connect to the API, effective 17 August 2026, due to functional changes. Older versions are blocked (HTTP 426) and prompted to upgrade — always run the latest release from GitHub.
1

Download from GitHub

Navigate to the Driver Automation Tool GitHub repository. Click the green

<> Code
button to reveal the download options, then select Download ZIP to download the entire repository as a ZIP archive.

GitHub repository — Download ZIP option
GitHub repository — Download ZIP option
2

Extract to a Suitable Location

Extract the downloaded ZIP file to a permanent location on your local machine, for example:

C:\DriverAutomationTool

Avoid extracting to temporary folders, the Desktop, or deeply nested paths. The tool stores settings per machine, so a consistent location ensures your configuration persists across sessions.

Important: Ensure the extracted folder is not blocked by Windows. Right-click the ZIP file before extracting, go to Properties, and check "Unblock" if present.
3

Launch from Administrative PowerShell

The Driver Automation Tool requires Administrator privileges for registry access (HKLM) and DISM WIM operations. Open PowerShell as Administrator and navigate to the extracted folder:

# Navigate to the tool directory

cd C:\DriverAutomationTool

# Launch the tool

.\Start-DriverAutomationTool.ps1

# Or launch with dark theme

.\Start-DriverAutomationTool.ps1 -Theme Dark

If you see an execution policy error, you may need to allow the script to run:

Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process

Alternatively, to set the execution policy for all sessions, invoke PowerShell using:

PowerShell.exe -ExecutionPolicy Bypass
Driver Automation Tool — Launching from PowerShell
Driver Automation Tool — Launching from PowerShell
4

End User License Agreement

On first launch, you will be presented with the End User License Agreement (EULA). Review the terms carefully before proceeding — by accepting, you acknowledge that the Driver Automation Tool is provided as-is, without warranty of any kind, and without formal support. Use of the tool is entirely at your own risk.

End User License Agreement
End User License Agreement
5

Configure Storage Locations

Before building packages, configure your storage paths in the Common Settings view. These paths determine where downloads are staged and where finished packages are stored.

OptionDescription
Temporary StorageWorking folder for downloads, extraction and WIM staging — must be a local path (UNC not supported for DISM)
Package StorageFinal output location for WIM and .intunewin packages — supports UNC/network paths
Purge DownloadsClear all cached content from temporary storage immediately
Clean on ExitAutomatically remove temporary files when the application closes
Tip: The Temporary Storage path must be a local path — DISM does not support UNC paths for WIM operations. Package Storage can be a network/UNC path for centralized access.
Storage location configuration
Storage location configuration
6

Build Your First Package

In Model Selection, choose your OEMs, OS version and architecture, then click Refresh Models to load the catalog. Tick the models to build (use Select All / search to filter), pick a Deployment Platform and Package Type, then click Build Package.

A Build Progress modal shows each model moving through the pipeline — Download → Extract → Package → Upload — with a status circle per stage:

● Grey — pending
● Blue — in progress
● Green — complete
● Red — failed

Live detail streams into the Activity Log at the bottom of the view, and the status bar shows elapsed time. Click Abort to cancel a run.

Interface Overview

The window has three areas: a title bar (theme toggle, window controls, support link), a sidebar grouped into Main (Model Selection), Configuration (ConfigMgr Settings, Intune Settings, Common Settings, Custom Driver Pack), and Tools (View Extended Log, About), and the content area for the active view.

Themes

The tool ships with two themes — Dark (default) and Light — toggled instantly via the sun/moon button in the title bar (no restart). You can also launch directly into a theme:

.\Start-DriverAutomationTool.ps1 -Theme Light

Check for Updates

On startup the tool checks GitHub for a newer release and, if one is available, prompts you to update. You can re-check any time from the About view via Check for Updates.

1 of 7