Automated driver downloads
OEM catalogues parsed on a schedule, with a resumable cURL download engine, configurable retries and hash verification for every package.
Free for the community. No licence key, no seat count.
The whole driver pipeline, in one window.
Driver Automation Tool downloads, extracts and packages OEM driver and BIOS updates for Configuration Manager, Intune and standalone WIM — across eight hardware vendors, on a schedule you set.
Runs on your own infrastructure. Telemetry is transparent and optional.
Captured from Driver Automation Tool 10.2.5. Light and dark themes switch instantly at runtime.
SUPPORTED OEMSHPDellLenovoMicrosoft SurfaceAcerASUSFujitsuPanasonic
New additions (Build 10.2.5+)ASUSFujitsuPanasonic
Community
Built in the open, shaped by the people running it.
Anonymous, opt-in telemetry from real deployments — the same figures that drive what gets fixed and built next.
Gathering the latest figures…
0%Positive feedback
Overall sentiment from ratings submitted from inside the tool.
- Issues and feature requests tracked openly on GitHub
- One-click positive and negative feedback built into the tool
- Insights prioritise the fixes and features that matter most
Core capabilities
Everything the packaging job actually needs.
Not a wrapper around a download link — the parts that make driver and BIOS management survive contact with a real fleet.
BIOS update management
Firmware packaged alongside drivers, DPAPI-encrypted BIOS passwords, and maintenance windows that defer a flash rather than forcing it.
Intune Win32 publishing
Packages uploaded as .intunewin Win32 apps with detection rules, assignment filters and Company Portal metadata generated for you.
Scheduled, unattended builds
A headless runner and a Windows Scheduled Task keep packages current overnight, so new releases are packaged before anyone asks.
CMTrace logging
Every phase logged in the format your team already reads, with a built-in viewer that filters info, warnings and errors.
Config import and export
Move a working configuration between environments, or keep it in source control alongside the rest of your build tooling.
One build, four destinations
Deploy to ConfigMgr, Intune, or a standalone WIM.
Pick the destination per model. The same catalogue, the same schedule — the tool handles the packaging format each platform expects.
Configuration Manager
Driver and BIOS packages created, distributed and content-updated in place, with pilot and production states.
Microsoft Intune
Win32 apps with detection rules and auto-generated assignment filters so each pack targets only matching hardware.
Standalone WIM
A single compressed image per model for MDT, OSD or offline import into another environment.
Download only
Sources downloaded and extracted to disk, ready for your own packaging pipeline.
Hardware coverage
Eight vendors, one catalogue.
Driver packs for every OEM below. BIOS and firmware packaging is available where the vendor publishes a machine-readable firmware catalogue.
HP
Driver packs and BIOS from the HP catalogue, plus Latest Drivers via the HP Client Management Script Library.
DriversBIOSLatest drivers
Dell
Driver packs and BIOS from the Dell catalogue, plus Latest Drivers via the Dell Command | Update catalog.
DriversBIOSLatest drivers
Lenovo
Driver packs and BIOS matched by release date, plus Latest Drivers via the Lenovo System Update catalog.
DriversBIOSLatest drivers
Microsoft Surface
Surface driver and firmware MSI packs, including Arm64 devices such as Surface Laptop 7 and Surface Pro 11.
DriversFirmwareArm64
Acer
Driver packs from the Acer catalogue, with BIOS matched from the firmware catalogue and an XML source fallback.
DriversBIOS
ASUS
Driver packs for ExpertBook and ExpertCenter commercial hardware, matched on the reported model code.
Drivers
Fujitsu
Driver packs for LIFEBOOK, STYLISTIC and ESPRIMO hardware, matched on the baseboard SKU.
Drivers
Panasonic
Driver packs for TOUGHBOOK hardware, matched on the baseboard product identifier.
Drivers
Counts are live from the driver & BIOS catalog.
Intune integration
Published, filtered and reported — without the manual prep.
Driver and BIOS packages are built into .intunewin Win32 apps and pushed straight to Intune. No content prep, no wrapping, no detection scripting, and everything reports in the Microsoft Intune admin center.
Automatic Win32 packaging
Each pack is built into the .intunewin format and uploaded as a Win32 app with install/uninstall commands, detection rules and metadata generated for you.
Scoped assignment filters
Filters limit the scope of devices receiving each update, so a package only targets the matching manufacturer, model and SystemID.
Full device visibility
Per-app install, pending, failed and not-applicable status at a glance, reported natively in the Intune admin center.
Client experience
What the person at the desk actually sees.
Once published, packages deploy as available or required apps. Users install from the Company Portal, or the package is pushed automatically — a Windows toast offers the choice to proceed or defer, and continues on its own after five minutes.
Company Portal — Available App
Step 1 of 5
Company Portal — Available App
End users open the Intune Company Portal and locate the driver or BIOS update published as an available app. They click Install to begin the process on demand.
Notifications
Toasts that look like they came from your IT team.
Windows toast notifications keep end users informed at every stage — from a pending update through to a successful install — with your own branding and wording.
Driver source
SCCM Driver Packs, or the very latest drivers.
From build 10.2.4 onwards, the Driver Automation Tool lets you choose how each driver pack is built. Keep the OEM's SCCM Driver Pack — the Configuration Manager release refreshed roughly monthly — or switch Dell, HP and Lenovo to Latest Drivers to pull the newest individual drivers straight from each vendor's live source. Other manufacturers continue to use their SCCM driver pack.
SCCM Driver Pack
The OEM's monthly Configuration Manager driver-pack release — the broadly validated baseline.
Latest Drivers
The newest Dell, HP and Lenovo drivers pulled straight from each vendor's live catalog, so packs aren't held back by the OEM's SCCM release cadence.
Update cadence
Re-evaluate Latest Drivers packs Daily, Weekly or Monthly on scheduled builds — a new pack is only rebuilt when the driver set actually changes.
Adapts to your setup
Your environment, your choice.
The Driver Automation Tool builds exactly the package your workflow needs. Choose your driver source, retention and deployment target — the tool handles the rest.
Select OEM & modelHP · Dell · Lenovo · Surface · Acer · ASUS · Fujitsu · Panasonic
Driver source? Dell · HP · Lenovo
SCCM Driver Pack
The OEM's monthly Configuration Manager driver-pack release — the broadly validated baseline. Used by all other manufacturers too.
Latest Drivers
Newest individual drivers straight from each vendor — Dell Command | Update, HP CMSL, or the Lenovo System Update catalog.
Retention / update cadence (Latest Drivers)
Keep an existing pack within the window and only rebuild when drivers change: Off · Daily · Weekly · Monthly.
Build the driver packageDownload → Extract → Package
Deployment target?
Configuration Manager
Creates the ConfigMgr/SCCM package and distributes content to your distribution points.
ConfigMgr (Offline)
Exports WIMs, payloads and an import script for air-gapped or offline site servers.
Microsoft Intune
Wraps the pack as a Win32 .intunewin app, uploads it, and creates a model-based assignment filter.
WIM Package Only
Builds a standalone WIM for custom task sequences or your own deployment workflow.
Download Only
Downloads and extracts the driver source with no packaging — bring your own process.
Getting started
Up and running in minutes.
A portable application with no installer — download it, point it at your environment, and start building packages.
- 1
Download
Get the latest release from GitHub — a single, portable PowerShell application with no installer required.
~30 seconds - 2
Configure
Set your storage paths, pick the deployment platform (ConfigMgr, Intune, or WIM-only), and configure a proxy if you need one.
~2 minutes - 3
Select models
Choose your OEMs, OS versions and architectures. Known Model Lookup highlights the devices actually in your environment.
~1 minute - 4
Build packages
Click Build — the tool downloads, extracts, packages and optionally uploads everything, with full progress tracking.
Automated
Under the hood
Enterprise-ready out of the box.
A PowerShell and WPF desktop application for Windows 11 and Windows Server 2016+, built so long jobs never block the window and credentials never touch disk in plain text.
Background runspaces
Long-running work executes in isolated PowerShell runspaces with WPF dispatcher timers for UI sync — no freezing, no blocking.
cURL download engine
Accelerated downloads with HTTP resume, signature validation and automatic retry handling for flaky vendor links.
Proxy support
System default, manual host:port with optional authentication, or bypass — full enterprise network compatibility.
Secure credential handling
BIOS passwords encrypted with DPAPI machine scope. Intune credentials via MSAL device code or app registration — never plain text.
Assignment filters & requirement scripts
Auto-generated Intune filters and Win32 requirement scripts scope each pack to a matching manufacturer, model and SystemID.
Extended log viewer
A built-in CMTrace-compatible viewer with severity icons, timestamps and one-click export straight to CMTrace.
Telemetry
Transparent, and entirely optional.
If you opt in, only anonymous package counts and model data leave the machine. Nothing that identifies you, your users or your network.
What's collected
- Driver packages created (count)
- BIOS packages created (count)
- Associated device models
- Package success / failure status
What's never collected
- No personally identifiable information
- No credentials or passwords
- No internal IP addresses
- No user names or email addresses
Guides
Intune driver packs, made simple.
Intune doesn't ship traditional OEM driver packs — the Driver Automation Tool brings model-specific driver-pack automation to Microsoft Intune. Start with the guide closest to your setup.
Intune driver packsAutomate OEM driver packs as Intune Win32 apps.Intune driversDeploy model-specific OEM drivers via Intune.Intune driver managementThe full download-to-deploy driver lifecycle.Intune driver updatesKeep driver packs and BIOS current on a schedule.Lenovo drivers for IntuneAutomated Lenovo driver packs for Intune.Dell drivers for IntuneAutomated Dell driver packs for Intune.HP drivers for IntuneAutomated HP driver packs for Intune.
Frequently asked questions
Driver and BIOS management, answered.
The questions that come up most often when teams move driver management off manual repackaging.
What is the Driver Automation Tool?
The Driver Automation Tool automates downloading, extracting, and packaging OEM driver and BIOS firmware updates for Microsoft Configuration Manager (ConfigMgr/SCCM) and Microsoft Intune. It supports HP, Dell, Lenovo, Microsoft Surface, Acer, ASUS, Fujitsu and Panasonic.
Which deployment platforms does it support?
Microsoft Configuration Manager (ConfigMgr/SCCM) and Microsoft Intune, plus WIM Package Only and Download Only modes for manual or custom workflows.
How do I create Intune driver packs?
Intune has no traditional OEM driver packs, so the Driver Automation Tool builds them for you: it downloads the latest model-specific OEM drivers, packages them as Win32 apps (.intunewin), creates detection rules, and auto-generates Intune assignment filters so each driver pack only targets matching hardware. You get ready-to-deploy Intune driver packs for HP, Dell, Lenovo, Surface, Acer, ASUS, Fujitsu and Panasonic.
How do I deploy Intune drivers with the tool?
The Driver Automation Tool streamlines Intune driver management and Intune BIOS management by packaging Intune drivers and BIOS updates as Win32 apps (.intunewin), uploading them to Microsoft Intune, and auto-creating assignment filters so each driver package only targets matching hardware. It handles the full workflow of building Intune driver packages and BIOS packages.
How do I create SCCM drivers and driver packages in ConfigMgr?
For SCCM drivers, the tool downloads the latest OEM driver packs, extracts them, and creates Microsoft Configuration Manager (ConfigMgr/SCCM) driver packages and BIOS packages automatically — including distribution point content, package metadata, and pilot/production deployment states.
Which OEMs and hardware are supported?
Driver packs are supported for HP, Dell, Lenovo, Microsoft Surface, Acer, ASUS, Fujitsu and Panasonic. BIOS and firmware packaging is available for HP, Dell, Lenovo, Acer and Microsoft Surface.
Is the Driver Automation Tool free?
Yes. It is a free, community tool provided as-is and distributed via GitHub.
Can I use the latest OEM drivers instead of the monthly SCCM driver pack?
Yes. From build 10.2.4 onwards, the Driver Package Build Type setting lets you choose SCCM Driver Pack (the OEM’s monthly Configuration Manager release) or Latest Drivers for Dell, HP, and Lenovo. Latest Drivers pulls the newest individual drivers from the Dell Command | Update catalog, the HP Client Management Script Library (CMSL), or the Lenovo System Update catalog, with an optional Daily/Weekly/Monthly update cadence.
Can driver and BIOS builds run automatically on a schedule?
Yes. A headless command-line runner and a Windows Scheduled Task option let you keep driver and BIOS packages current unattended, overnight or on a weekly cadence.
Still repackaging drivers by hand?
Point it at your site server or tenant, tick the models you actually deploy, and let it run overnight.
New to the tool? Start with the ConfigMgr & Intune setup guide.