HP Driver Packs 🤦

[Planehazza]

Wish it was as simple as it is with Dell, jeez.

 

We have some older (but not stupid old) 255 G7 laptops. Can I find full driver packs for them? Can I s***e.

I've installed the MIK tool for SCCM, which lets me tap into HP and pull down the driver packages, but I cannot see 255 G7 listed regardless of which of the many OS options I pick (all W10/11). For reference, this is the HP driver pack list, and 255 G7 is nowhere to be found. The same is echoed in the MIK SCCM tool.

 

https://hpia.hpcloud.hp.com/downloads/driverpackcatalog/HP_Driverpack_Matrix_x64.html

So before I start pulling down all the softpacks from the HP site and importing them one by one into a driver package, has anyone got a better idea? I really do not want to pull down 10-15 driver packs per device type. I'm not rally a fan of using things like Driver Monkey to pull infs from an existing install, but I guess I'll have to if that's the only option...

 

Thanks!

Edited May 16, 2024 by Planehazza

[mrbios]

Scrap the MIK tool, get this https://msendpointmgr.com/driver-automation-tool/

 

I've got HP desktops and HP laptops. Never really had any issue with HP drivers using the above tool.

[RyanT001]

We had the exact same issue with this model of laptop... Gave up looking in the end as from what I could tell, a driver pack simply doesn't exist.

 

Ended up having to download them one by one from HP.

[WHOAMI3904]

Wish it was as simple as it is with Dell, jeez.

 

We have some older (but not stupid old) 255 G7 laptops. Can I find full driver packs for them? Can I s***e.

I've installed the MIK tool for SCCM, which lets me tap into HP and pull down the driver packages, but I cannot see 255 G7 listed regardless of which of the many OS options I pick (all W10/11). For reference, this is the HP driver pack list, and 255 G7 is nowhere to be found. The same is echoed in the MIK SCCM tool.

 

https://hpia.hpcloud.hp.com/downloads/driverpackcatalog/HP_Driverpack_Matrix_x64.html

So before I start pulling down all the softpacks from the HP site and importing them one by one into a driver package, has anyone got a better idea? I really do not want to pull down 10-15 driver packs per device type. I'm not rally a fan of using things like Driver Monkey to pull infs from an existing install, but I guess I'll have to if that's the only option...

 

Thanks!

 

I had a similar issue to this before.

 

I ended up going to the driver page for the laptop. Downloaded the drivers I needed and then unzipped them using 7-zip so that they were in a deployable format. After that I made a separate deployment share, with just those drivers loaded into WDS for that share and the MDT images within it, and called the deployment share the laptop model. That seemed to work for us.

 

However I was using WDS and MDT. I’m not too familiar with SCCM or intune so I’m not sure if it’s the same or not.

 

Hope this helps.

[Planehazza]

Scrap the MIK tool, get this https://msendpointmgr.com/driver-automation-tool/

 

I've got HP desktops and HP laptops. Never really had any issue with HP drivers using the above tool.

 

Have just installed this thanks. HP is greyed out on the Make and Model page so cannot query HP drivers. Wonder if I'm missing a requisite as it's moaning about Lenovo.

 

EDIT: sorted. HP Doesn't like "Windows 10" as the OS; you have to be more specific. Alas, still no 255 G7 option, obviously because it taps into the same catalogue that HP's own tool does. I'm going to have to install this tool on a 255 G7 and pull the drivers I think. First, lunch...

Edited May 16, 2024 by Planehazza

[mrbios]

Have just installed this thanks. HP is greyed out on the Make and Model page so cannot query HP drivers. Wonder if I'm missing a requisite as it's moaning about Lenovo.

 

HP and Dell differ slightly in the way you can pull their driver packs. With HP you have to select a specific windows build, and older models will disappear as you go up the builds. Not that it matters for the actual windows build you're installing on.

 

I did just have a search for the 255 model and as Ryan mentioned above, seems that model doesn't have a package.

 

The tool is really good though for automating modern driver package deployment though, i'd recommend tinkering around for your other devices with it.

[Planehazza]

HP and Dell differ slightly in the way you can pull their driver packs. With HP you have to select a specific windows build, and older models will disappear as you go up the builds. Not that it matters for the actual windows build you're installing on.

 

I did just have a search for the 255 model and as Ryan mentioned above, seems that model doesn't have a package.

 

The tool is really good though for automating modern driver package deployment though, i'd recommend tinkering around for your other devices with it.

 

Yeah I just edited my post but you beat me to it. It does look promising, especially when we have Lenovos too. I'll see what I can do to pull drivers out of a working device after some food

 

Thanks!

[PotNoodleTech]

HP have always been garbage at driver packs. I don't know why anyone buys them.

[MartinByard]

We bought some 255 models during covid and had an issue with the driver packs, I think its due to these being from the Home range and not being an Enterprise model - thus there are no driver packs available for enterprises to use.

 

I ended up letting one build using the factory image, making sure everything was installed and the latest version (at the time) and then creating a driver pack from that machine:

 

[color=#0101FD][font=SFMono-Regular]Export-WindowsDriver[/font][/color][color=#006881][font=SFMono-Regular] -Online[/font][/color][color=#006881][font=SFMono-Regular] -Destination[/font][/color][color=#161616][font=SFMono-Regular] C:\HP255_drivers[/font][/color]

[Davit2005]

We used Dell desktops at a previous place then they swapped them out for HP 800's was a nightmare to get the drivers installed even resulting in a bluescreen a number of times due to a USB 3 driver. In the end I used native Windows 10 drivers and jus added the drivers that were missing or needed manufacturer driver.

 

HP/Aruba switch firmware is slightly better although needing an account to get them and even then some are not available still without a call to HP.

[Norphy]

We bought some 255 models during covid and had an issue with the driver packs, I think its due to these being from the Home range and not being an Enterprise model - thus there are no driver packs available for enterprises to use.

 

I ended up letting one build using the factory image, making sure everything was installed and the latest version (at the time) and then creating a driver pack from that machine:

 

[color=#0101FD][font=SFMono-Regular]Export-WindowsDriver[/font][/color][color=#006881][font=SFMono-Regular] -Online[/font][/color][color=#006881][font=SFMono-Regular] -Destination[/font][/color][color=#161616][font=SFMono-Regular] C:\HP255_drivers[/font][/color]

 

I did the same trick with the Geobooks and have done it for other devices where things like webcams and fingerprint sensors are a bit more obscure. It's a useful tool to know about!

[mrstrong]

yes, this is how to do it from the OG

 

https://deploymentbunny.com/2016/02/26/powershell-is-king-export-drivers-from-windows/