Intune Driver Updates — Keep OEM Drivers & BIOS Current
Automate Intune driver updates instead of rebuilding packages by hand. The Driver Automation Tool re-checks OEM catalogues, downloads newer model-specific driver packs and BIOS updates, and republishes them as Intune Win32 apps — for HP, Dell, Lenovo, Microsoft Surface, and Acer.
Drivers and firmware move constantly. Keeping Intune driver updates current usually means repeating the same download-extract-package-upload cycle for every model. The Driver Automation Tool runs that cycle for you, on a schedule, with version comparison so only genuinely newer packages are rebuilt.
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.

How update automation works
Catalogue re-check
Compares your packaged versions against the live OEM catalogue to find newer driver packs and BIOS releases.
BIOS version comparison
BIOS updates are classified (Recommended/Critical) with minimum-version validation before packaging.
Scheduled runs
A Windows Scheduled Task or the command-line runner refreshes packages overnight or weekly, unattended.
Republish to Intune
Updated packs are rebuilt as .intunewin Win32 apps and uploaded to Microsoft Intune automatically.
Hash verification
Every downloaded update is hash-verified so only intact, authentic content is packaged.
Per-model precision
Updates stay model-specific, so devices only receive the driver and BIOS versions meant for them.
Refreshing Intune Win32 driver packages



Frequently asked questions
How do I keep Intune driver packs up to date?
Schedule the Driver Automation Tool to re-run on a cadence. It compares your existing package versions against the OEM catalogue, downloads any newer driver packs or BIOS updates, and republishes them as Intune Win32 apps automatically.
Does it handle BIOS and firmware updates?
Yes. BIOS updates are downloaded, version-compared, classified as Recommended or Critical, validated against minimum versions, and packaged for Intune alongside driver packs.
Can updates run unattended?
Yes. The headless command-line runner and a Windows Scheduled Task let driver and BIOS updates run overnight or weekly with no manual steps.
Will it rebuild packages that have not changed?
No. Version comparison means only models with a newer driver pack or BIOS release are rebuilt, avoiding unnecessary re-uploads.
Related pages
Want the full picture?
See everything the Driver Automation Tool can do — driver packs, BIOS updates, ConfigMgr and Intune deployment — on the main site.
Tell Me More