Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downloading HP Model BIOS update - URL seems to have changed and .cab naming convention. #496

Open
Love-A opened this issue Aug 17, 2023 · 14 comments

Comments

@Love-A
Copy link

Love-A commented Aug 17, 2023

Hi!

I have been having issues downloading BIOS for models using DAT.
The DAT log says:
[Error] - An error occurred while attempting contact http://ftp.hp.com/pub/caps-softpaq/cmit/imagepal/ref/8b94/8b94_64_22H2.cab - The remote server returned an error: (404) Not Found.

Checking the DAT .ps1, this is what determines the URL in version 7.2.2:
$HPXMLCabinetSource = "http://ftp.hp.com/pub/caps-softpaq/cmit/imagepal/ref/" + $($($SKUValue.Split(",") | Select-Object -First 1) + "/" + $($SKUValue.Split(",") | Select-Object -First 1) + "" + $($Architecture.TrimStart("x")) + "" + $OS + ".cab")

Entering the URL above, manually to browser, you get an 404.

So, i tried to find what URL could be vaild for the specific model. Using HPIA with /debug i found out that that uses this URL for the same model to download the .cab:
08-17-2023 11:55:39 -- Downloading 'https://hpia.hpcloud.hp.com/ref/8b94/8b94_64_10.0.22h2.cab?hpia=5.1.10&wf=3&pid=2101628554&osv=10.0.19045&osa=64&m=ui&at=User'

You can use just "https://hpia.hpcloud.hp.com/ref/8b94/8b94_64_10.0.22h2.cab"

With this information, it seems as if the URL in .ps1 doesnt add up anymore, and the naming convetion for the .cab has changed aswell, and would need a tweak.

Dont know if its also supposed to be able to use the "old way" as in the script, or if this is the way now.

@hillihappo
Copy link

@Love-A same for us. Does anyone have a way around this?

@stephannn
Copy link

is this the same issue? #454

@hillihappo
Copy link

@stephannn I don't think so since the link doesn't seams to be working with HTTPS.

http://ftp.hp.com/pub/caps-softpaq/cmit/imagepal/ref/8b41/8b41_64_22H2.cab

@stephannn
Copy link

https://ftp.hp.com/pub/caps-softpaq/cmit/imagepal/ref/8b41/8b41_64_10.0.22h2.cab
as well as
http://ftp.hp.com/pub/caps-softpaq/cmit/imagepal/ref/8b41/8b41_64_10.0.22h2.cab
are working. The H is case sensitive
you also have to change it to the new naming convention

@hillihappo
Copy link

hillihappo commented Aug 21, 2023

@stephannn ahh nice, my fault for not reading every post. I did get it working with your suggested solution, thank you very much! #454

@Love-A
Copy link
Author

Love-A commented Aug 24, 2023

Thank you @stephannn ! I was looking in the Pulls but i must have missed that one!

@niwsen
Copy link

niwsen commented Feb 26, 2024

I still have the issue, but with newer BIOS versions

Any fixes for this? Tried both H and h in the url.

  • URL is https://ftp.hp.com/pub/caps-softpaq/cmit/imagepal/ref/8b41/8b41_64_10.0.23h2.cab DriverAutomationTool 2/26/2024 1:19:50 PM 23232 (0x5AC0)
    ======== Errors(s) Occurred ======== DriverAutomationTool 2/26/2024 1:19:51 PM 23232 (0x5AC0)
    [Error] - An error occurred while attempting contact https://ftp.hp.com/pub/caps-softpaq/cmit/imagepal/ref/8b41/8b41_64_10.0.23h2.cab - The remote server returned an error: (404) Not Found. DriverAutomationTool 2/26/2024 1:19:51 PM 23232 (0x5AC0)
    DriverAutomationTool 2/26/2024 1:19:51 PM 23232 (0x5AC0)
  • Could not download HP EliteBook 840 14 inch G10 Notebook PC BIOS update DriverAutomationTool 2/26/2024 1:19:51 PM 23232 (0x5AC0)
    Warning: Unable to retrieve BIOS Download URL For HP Client Model: EliteBook 840 14 inch G10 Notebook PC DriverAutomationTool 2/26/2024 1:19:51 PM 23232 (0x5AC0)

@harris1m
Copy link

Is there is fix for this yet? We are on the cusp of moving from Dell to HP. I can get around the driver download by manually downloading the SP from HPIA and Copying to the DAT source folder. Ensuring you do not have "Remove driver source packages" ticked. I cannot do the same for BIOS, haven't found the site to download these yet.

ajn142attamu added a commit to ajn142attamu/DriverAutomationTool that referenced this issue Mar 1, 2024
@ajn142attamu
Copy link

ajn142attamu commented Mar 1, 2024

@niwsen and @harris1m I think I've got a fix that will work for y'all in my fork. I've updated the URL to the softpaqs per @Love-A and @stephannn 's findings and added handling for 22H2 and 23H2. It's passed my preliminary testing, but we don't have many HPs in circulation, so I can't do anything more conclusive.

You can copy https://github.com/ajn142attamu/DriverAutomationTool/blob/master/Current%20Branch/7.2.2/DriverAutomationTool.ps1 into C:\Program Files\MSEndpointMgr\Driver Automation Tool and then run it from an admin PowerShell window. You may need to clear the C:\Program Files\MSEndpointMgr\Driver Automation Tool\Temp directory and rename C:\Program Files\MSEndpointMgr\Driver Automation Tool\Settings\OEMLinks.xml to ensure you pull the latest copy of OEMLinks.xml and then the latest copy of all the catalog files.

@niwsen
Copy link

niwsen commented Mar 1, 2024

Thanks ajn142attamu, I will try this monday, when I'm at the customer.

Though yours is 7.2.2 ... do you have the latest from the 7.2.3 in your .ps1 file?

@harris1m
Copy link

harris1m commented Mar 1, 2024

@ajn142attamu Thank you, give me some time to test. Will get back to you all.

@harris1m
Copy link

harris1m commented Mar 1, 2024

BIOS now downloads OK. Correct HPIA URL working.

image

@ajn142attamu
Copy link

Thanks ajn142attamu, I will try this monday, when I'm at the customer.

Though yours is 7.2.2 ... do you have the latest from the 7.2.3 in your .ps1 file?

Yeah, source code for 7.2.3 wasn’t released, and the changelog said the only change was W11-23H2 support. I’ve patched that support into my fork of the 7.2.2 source code so that I could continue being able to try and fix bugs as encountered while getting the benefits of 7.2.3.

@korpx
Copy link

korpx commented May 31, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants