Intune Driver Packs — Automated OEM Driver Management for Intune & Configuration Manager
Enterprise-grade automation for downloading, extracting, and packaging OEM driver packs and BIOS firmware updates for Microsoft Configuration Manager (ConfigMgr/SCCM) and Microsoft Intune — for HP, Dell, Lenovo, Microsoft Surface, and Acer. Build SCCM drivers and Intune drivers as ready-to-deploy driver packs and BIOS packages automatically.
A free community tool — created by Maurice Daly
Driver & BIOS packaging for Microsoft Configuration Manager and Intune
The Driver Automation Tool automates downloading, extracting, and packaging OEM driver packs and BIOS/firmware updates for Microsoft Configuration Manager (ConfigMgr/SCCM) and Microsoft Intune. It supports HP, Dell, Lenovo, Microsoft Surface, and Acer, and can build ConfigMgr packages, Intune Win32 apps, or standalone WIM files — fully automated, including unattended scheduled builds.
Explore the driver & BIOS catalog, follow the ConfigMgr & Intune setup guide, or view community usage reports.
Global Statistics
Loading Statistics.
Feedback-driven innovation
Every release is shaped by the people who use the tool. Issues and feature requests raised on GitHub, together with the in-app feedback you send directly from the tool, feed a continuous loop of refinement — turning real-world usage into new capabilities and fixes.
- 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
Overall sentiment from ratings submitted through the tool.
Everything you need for driver and BIOS management
A comprehensive toolkit designed for endpoint administrators who need reliable, automated packaging workflows.
Automated Driver Downloads
Accelerated downloads via curl.exe with HTTP resume support, configurable retry logic (10 retries, 60s delay), and automatic hash verification for every package.
Multi-OEM Support
Full support for HP, Dell, Lenovo, Microsoft Surface, and Acer — with automatic catalog discovery and per-manufacturer extraction logic.
BIOS Update Management
Comprehensive BIOS update support with version comparison, release classification (Recommended/Critical), minimum version validation, and hash verification.
WIM Packaging
Create WIM packages using DISM (built-in) or wimlib (multi-threaded) with configurable compression: XPRESS (fast), LZX (maximum), or None.
ConfigMgr Integration
Native Configuration Manager support with automatic package creation, content distribution to DPs, WinRM/WMI connectivity, and deployment state tracking.
Intune Integration
Full Microsoft Intune support with device code or app registration auth, chunked Azure Blob uploads (4–100 MB), parallel threading, and Win32 app packaging.
Deploy to ConfigMgr, Intune, or standalone WIM
Four deployment modes to match your environment and workflow — from fully automated to manual distribution.
Configuration Manager
Automatic package creation, content distribution to distribution points, WinRM & WMI hardware inventory, deployment state tracking (Production, Pilot, Retired).
Microsoft Intune
Interactive (Device Code) or App Registration auth, toast notification previews, configurable upload chunk size and parallel threads, automatic Win32 app packaging.
WIM Package Only
Direct WIM creation for manual distribution workflows without ConfigMgr or Intune dependency.
Download Only
Download and extract driver/BIOS packages without any packaging — ideal for manual review or custom workflows.
Native Microsoft Intune integration
Driver and BIOS packages are automatically packaged as Win32 apps and published straight to Intune — no manual content prep, wrapping, or detection scripting required. Everything is reported and managed directly within the Microsoft Intune admin center.
Automatic Win32 packaging
Each driver and BIOS package is built into the .intunewin format and uploaded as a Win32 app with install/uninstall commands, detection rules, and metadata generated for you.
Full device visibility
Report on deployments directly in the Intune admin center. Admins get complete visibility of exactly which devices are being updated, with per-app install, pending, failed, and not-applicable status at a glance.
Scoped assignment filters
Assignment filters limit the scope of devices receiving each update, so a package only targets the matching manufacturer, model, and SystemID — devices only ever receive the packages built for them.
Intune client update process
Once published, driver and BIOS update packages can be deployed as available or required apps through Intune. Users install from the Company Portal, or the package is pushed automatically. A Windows toast notification gives the user the option to proceed immediately or defer — if no action is taken, the install continues automatically after 5 minutes.
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.
Toast Notifications
Fully branded and customisable Windows toast notifications keep end users informed at every stage of the update process — from pending updates through to successful completion.
Each notification is fully customisable — replace the default branding with your own logo and tailor the messaging to match your organisation's IT communication standards.
Built for the modern enterprise
Support for the latest Windows versions, architectures, and enterprise security requirements.
Windows 11 Support — All Builds
Full driver and BIOS support for all current Windows 11 builds
x64 & Arm64
Architecture support for both traditional x64 and modern Arm64 devices
Custom Driver Packs
Capture system drivers via PNPUtil or build from a local INF folder
BIOS Password Security
DPAPI machine-scope encryption with Intune detection and remediation scripts
CMTrace Logging
All operations logged in ConfigMgr Trace-compatible format with 5 MB auto-rotation
Up and running in minutes
A portable application with no installer — download, configure, and start building packages.
Download
Get the latest release from GitHub — a single, portable PowerShell application with no installer required.
~30 secondsConfigure
Set your storage paths, select your deployment platform (ConfigMgr, Intune, or WIM-only), and configure proxy if needed.
~2 minutesSelect Models
Choose your OEMs, OS versions, and architectures. Use Known Model Lookup to highlight devices in your environment.
~1 minuteBuild Packages
Click Build — the tool downloads, extracts, packages, and optionally uploads everything automatically with full progress tracking.
AutomatedEnterprise-ready out of the box
Proxy support, background processing, config backup, and a modern UI experience.
Proxy Support
System default, manual host:port with optional authentication, or bypass — full enterprise network compatibility.
CURL Download Engine
Accelerated downloads using curl.exe with signature validation, silent or visible window mode, and automatic retry handling.
Background Processing
All long-running tasks run in isolated PowerShell runspaces — the UI stays fully responsive during downloads, DISM operations, and uploads.
Config Import/Export
Backup and restore all settings via .reg file for easy migration between machines or standardized deployment across teams.
Assignment Filters & Requirement Scripts
Auto-generate Intune assignment filters and Win32 requirement scripts that scope each driver/BIOS package to matching manufacturer, model, and SystemID — so devices only receive packages built for them.
Extended Log Viewer
Built-in CMTrace-compatible log viewer with severity icons, timestamps, and one-click export to CMTrace.
Light & Dark mode
Switch between light and dark themes instantly at runtime — no restart required. The entire UI adapts immediately to match your preference.
Built for reliability and performance
A modern desktop architecture with isolated background processing and secure credential handling.
PowerShell WPF Application
Enterprise-grade desktop application built with PowerShell and WPF, supporting Windows 11 and Windows Server 2016+.
Background Runspaces
Long-running operations execute in isolated PowerShell runspaces with WPF DispatcherTimers for UI synchronization — no freezing, no blocking.
Secure Credential Handling
BIOS passwords encrypted with DPAPI machine-scope. Intune credentials managed via MSAL device code or app registration — never stored in plain text.
Telemetry API
Optional, transparent telemetry via Azure Table Storage. Only anonymous package counts and model data — no PII, no credentials, no internal IPs.
Choose your driver source: SCCM Driver Packs or 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: the Dell Command | Update catalog, the HP Client Management Script Library (CMSL), or the Lenovo System Update catalog. 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.
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.
The OEM's monthly Configuration Manager driver-pack release — the broadly validated baseline. Used by all other manufacturers too.
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.
Creates the ConfigMgr/SCCM package and distributes content to your distribution points.
Exports WIMs, payloads and an import script for air-gapped or offline site servers.
Wraps the pack as a Win32 .intunewin app, uploads it, and creates a model-based assignment filter.
Builds a standalone WIM for custom task sequences or your own deployment workflow.
Downloads and extracts the driver source with no packaging — bring your own process.
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. Explore the guides:
Transparent and optional
If you opt in, only anonymous package counts and model data are collected — no PII, no credentials, no internal IPs.
What's collected
- Driver packages created (count)
- BIOS packages created (count)
- Associated device models
- Package success/failure status
What's NOT collected
- No personally identifiable information
- No credentials or passwords
- No internal IP addresses
- No user names or emails
Ready to automate your driver packaging?
Download the latest release and start building OEM driver and BIOS packages in minutes.
Frequently Asked Questions
Common questions about automating driver and BIOS firmware updates for Microsoft Configuration Manager and Microsoft Intune.
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, and Acer.
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, and Acer.
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 for HP, Dell, Lenovo, Surface, and Acer.
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 and BIOS/firmware updates for HP, Dell, Lenovo, Microsoft Surface, and Acer devices are supported out of the box.
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.