Create an account on the HP Community to personalize your profile and ask a question
01-06-2020 12:16 PM
I recently set up third-party software updates in SCCM to be able to push out HP drivers and BIOS updates. When selecting the drivers and BIOS updates and publishing them I get errors on some of the updates.
The update downloads fine but then I get a hash fail:
SyncUpdate: 20004850-0000-0000-5350-000000084418 - Hash for downloaded content file does not match update 20004850-0000-0000-5350-000000084418 expected hash1. STATMSG: (SRVMSG_SMS_ISVUPDATES_SYNCAGENT_UPDATECONTENT_HASH_FAIL). SMS_ISVUPDATES_SYNCAGENT STATMSG: (SRVMSG_SMS_ISVUPDATES_SYNCAGENT_UPDATECONTENT_FAIL). SMS_ISVUPDATES_SYNCAGENT
Other updates download fine and I've been able to deploy them.
My understanding that that this means the file hash for the file being downloaded has changed since the third-party update was created in the catalog. The only fix for this is HP needs to correct/update the third-party update so the hash matches the latest file being downloaded.
Can this be updated?
01-09-2020 11:03 AM
@JakeSWTC Welcome to HP Community!
Please provide the product number.
Note: Please ensure the complete product name/number for a quicker response from the community, as we need to know what we are dealing with to provide an accurate solution:
Click here for steps on finding the information we need!
Remember: Do not share any of your personal information such as serial, phone number, email ID, etc.
Keep us posted,
If you would like to thank us for our efforts to help you,
Give us a virtual high-five by clicking the 'Thumbs Up' icon below, followed by clicking on the "Accept as solution" on this post,
Have a great day!
01-10-2020 09:04 AM
This isn't in regards to a specific piece of hardware but many of them. SCCM pulls the information from:
The hashes of the drivers and BIOS downloaded from there are not matching the updates.
01-30-2020 01:26 PM
I'm having the exact same problem as the original poster. Can HP provide a helpful reply? I've already tried re-synching the catalogs through HP and on my SCCM server. But, when I try to publish the update I get the same error in the SMS_ISVUPDATE_SYNCAGENT log. The update I'm trying to publish is sp99740. I've also verified there are no blocked certificates in SCCM
02-11-2020 07:51 AM
I tried this suggestion and it is working for me now:
After enable "Require SSL" in Software update point Properties.
Deleted all files under folder "C:\Program Files\Microsoft Configuration Manager\ISVTemp"
then resynced and published the updates again.
that worked for me