How to Find and Download Current HP Driver Packs for SCCM/Intune Deployment

The old HP Driver Pack Matrix table of direct download links from 2014-2016 is dead. HP retired those links years ago, and typing them into a browser now just gets a 404 or a redirect to a generic support page. If you’re still building EliteBook or ProBook images against that table, every link will fail.

This covers the two ways HP actually expects you to find current driver packs in 2026: HP Image Assistant for one-off or manual work, and HP CMSL (the PowerShell module) for a repository you can point SCCM or Intune at automatically. Both pull live from HP’s catalog, so they don’t go stale the way a static link table does.

Why the old link table stopped working

HP periodically deprecates old SoftPaq numbers as models fall out of the support window, and the direct download URLs die with them, even when a newer driver pack for the same platform still exists under a different SoftPaq ID. A static table of links from a decade ago has no way to reflect that. The fix isn’t finding a fresher table, it’s using the tools HP updates live: HPIA and the HP Driver Pack Catalog behind it.

Find your platform ID first

Every lookup method wants the platform’s four-character System ID, not “EliteBook 840 G9”. Pull it from the BIOS/board info on the machine itself:

# PowerShell, run as Administrator
Get-CimInstance -ClassName Win32_BaseBoard | Select-Object Product

# Or from an offline WinPE/OSD context
wmic baseboard get product

The value returned (something like 8990 or 861F) is the Platform ID used throughout HPIA, HP CMSL and the driver pack matrix. Keep a note of it per model you image.

Option 1: HP Image Assistant, for manual or one-off work

Download the current HPIA build from HP’s Client Management Solutions page. Run it interactively against a live machine and it analyses the installed hardware, compares it to HP’s catalog, and lets you download just the current driver pack rather than hunting SoftPaq numbers by hand.

For scripted or silent use (useful in a task sequence or a quick test before you build automation), the core switches are:

HPImageAssistant.exe /Operation:Analyze /Action:Install /Selection:All ^
  /Silent /ReportFolder:C:\HPIA\Logs /SoftpaqDownloadFolder:C:\HPIA\Downloads

Swap /Action:Install for /Action:List if you only want a report of what’s available without applying anything. Exit code 3011 means a reboot is needed; the 4102-4104 range covers analysis failures, both worth handling explicitly if you’re wrapping this in a script.

Option 2: HP CMSL, for SCCM and Intune automation

For a repeatable pipeline rather than a one-off download, install HP CMSL and build a local SoftPaq repository your SCCM distribution point (or Intune Win32 app packaging step) syncs against:

Install-Module -Name HPCMSL -Force

MD \\CM01\Share\Softpaqs\EliteBook840G9
CD \\CM01\Share\Softpaqs\EliteBook840G9
Initialize-Repository
Set-RepositoryConfiguration -Setting OfflineCacheMode -Cachevalue Enable
Add-RepositoryFilter -Platform '8990' -Os win11 -OsVer 24H2 -Category Driver,BIOS,Firmware
Invoke-RepositorySync
Invoke-RepositoryCleanup

Each repository folder maps to one platform. Re-run Invoke-RepositorySync on a schedule (a weekly scheduled task on the DP is enough for most estates) and it pulls whatever HP has published since the last sync, no manual link-chasing required.

Wiring it into SCCM and Intune

SCCM/ConfigMgr: point a driver package or a “Run Command Line” task sequence step at the synced repository folder using HPIA’s offline mode, so it installs from your DP rather than reaching out to HP during imaging:

HPImageAssistant.exe /Operation:Analyze /Action:Install /Selection:All ^
  /Offlinemode:"\\CM01\Share\Softpaqs\EliteBook840G9" /Silent ^
  /ReportFolder:C:\HPIA\Logs

Intune: there’s no direct offline-repository equivalent, so the common pattern is wrapping HPIA (or a CMSL-built driver pack) as a Win32 app with the silent switches above, deployed as required after Autopilot enrolment, or run as a platform script during ESP.

Frequently asked questions

Is the old HP Driver Pack Matrix page coming back?

No. HP has moved to the live matrix and catalog-driven tools described above. Treat any bookmarked 2014-2016 SoftPaq URL as permanently dead rather than temporarily broken.

Do I need HPIA and HP CMSL, or just one?

HPIA on its own covers manual and small-scale work fine. Add HP CMSL once you’re maintaining more than a couple of models, since scripting the repository sync saves you re-running HPIA by hand every patch cycle.

Does this work for desktops and workstations too?

Yes. HPIA, CMSL and the driver pack matrix cover HP’s EliteDesk, ProDesk and Z-series workstation lines the same way, using the same platform ID lookup.