Working on certifying drivers for some older model HPs in the shop. My options are:
1. Use Mikael Nystrom’s PowerShell is King – Export drivers from Windows good stuff if you have a box already configured how you want and it’s not Windows 7
(do a get-command export* and you’ll see you can’t use export-windowsdriver in Win 7)
Good Windows 7 Options:
2. If you get stuck installing a driver as an application, check in Program Files/Program Files (x86) for the unpacked files to see if an .inf was dropped there. Be careful pulling the .inf file as some of the softpaqs need the software stack to work properly (see method 4 below for this scenario).
Found the driver for Bluetooth for a ZBook in this folder in Program Files (x86)
3. If HP, I generally find the majority of the unpacked files in c:\swsetup and then I search Program Files.
C:\SWSetup is a common unpack directory for Support Assistant and manual installs.
4. Another HP trick is to use the HP Softpaq Download Manager. Once you load up the model you want, you can right click on any of the given drivers to get the fly out menu and select cva file. If it exists, it will give you install + silent install instructions for those pesky drivers that need to be installed as applications.
Using HPSDM to get the driver package and install instructions.
Install instructions are in a cva that you open with notepad – then scroll to the install section.
A fun tip about the cva file is if you know the softpaq number, you can just find it in this URL (this only works if there is actually a cva – not everything has one – but better than nothing, right??)
This isn’t a very technically deep post but the method is something that has been helpful for me dealing specifically with HP Zbook 14 laptops. I have never had more trouble installing graphics drivers in my entire life than the two years I’ve worked with this model laptop.
Anyway, this post isn’t about much other than to say when you’re updating drivers and nothing seems to be working you can always force the install through device manager.
Just open Device Manager and navigate to Display node. Right click the corresponding display adapter you want to update. Pick Update Driver Software.
I have the AMD card disabled (too buggy in Windows 10) which is why it isn’t present – but this will work for both AMD and Intel.
Next pick Browse my computer for driver software
And finally, navigate to the extracted driver in the SWSETUP folder (or if you’ve manually downloaded and extracted it, navigate to there). And then complete the Wizard.
That’s it! Super simple and saves a lot of headaches.
If you’re an HP customer, you might have noticed more recently than ever that HP’s links are changing on the daily. Why it’s happening isn’t really very important, but it does impact your organization’s desktop engineer (I’m assuming that’s you – accountants don’t read my blog. I know this because I asked the accounting team at my work – they said no). You can (and should, when the page is up) go to the product’s support page and grab the driver pack but that isn’t always an option, or realistic, or even what I feel like doing.
So here’s where I tell you to go ahead and do that in-place upgrade and then download the Softpaq Download Manager. It will launch a catalog that searches for missing/new drivers specific to your model. It can also search for other models, but in my experience, I feel it’s best to only run it on the model in question. NOTE: this requires .Net 3.5 SP1
This is also how I keep my drivers updated in my image. HP doesn’t update the management packs once they are published (at least not for the Zbooks) so every few months I will run a deployment and then the utility to get the drivers. Another cool side-note is that you can build driver packs from this utility to throw in to a task sequence (think large scale Win 10 in place upgrade ((btw, anything more than say 2 is large scale and worth your time to automate)) ).
They all write to C:\Swsetup and get organized into folders by softpaq name. From there I copy them to my driver repository, them extract and import for OSD.