• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Seize the moment! nominate yourself or a tech enthusiast you admire & join the HP Community Experts!
Archived This topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.

‎01-28-2020 08:25 AM

HP Recommended
Product: EliteBook 840 G4 G5 G6
Operating System: Microsoft Windows 10 (64-bit)

I am integrating HP Image Assistant into our environment to remotely update Device Drivers for our company computers. 

During my testing, I keep having the 'Intel WLAN Driver SP100659' for the component, 'Intel(R) Dual Band Woreless-AC 8265' Fail when installing.


I then examined the issue locally on the computer and I determined that the issue is the way the 'Setup.bat' handles the location of the files that comes with SP100659.

 

When HP Image Assistant downloads and then extracts SP100659, it extracts the executable to a folder which names it 'sp100659 Intel WLAN Driver'

 

The Setup.bat in that location has a line that calls the location using, %~dp0UWD\Win64\Drivers\*.inf

This would be fine except the path NEEDS quotes around it. Since HP Image Assistant extracts SP100659 into a folder name with SPACES, the Setup.bat file cannot find the path of the drivers because it needs quotes.

 

Simply changing the line to: pnputil.exe /add-driver "%~dp0UWD\Win64\Drivers\*.inf" /install corrects the issue. But I cannot determine a reasonable way to resolve this in an automated way across hundreds of computers.

 

This needs to be changed within the SP itself so that HP Image Assistant can run the package. How can I request this change to HP so that their utility can properly handle this driver?

Archived This topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.
Didn't find what you were looking for? Ask the community
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.