Failed to download package: Bad Hash (0x80090002)

I need a solution

I created an MSI and added it to a new software release. I distributed it to all the site servers and deployed it to 3 computers along with my test computer. I had to change the MSI later on, so I had to rebuild it. I deleted the msi from the Software Library via the GUI and added my modified version. I re-distributed the package again. I normally run a SQL query to see if the package is ready:

SELECT rrsp.Name,sps.Status,vc.Name FROM RM_ResourceSoftware_Package rrsp
JOIN SWDPackageServer sps ON sps.PackageId = rrsp.Guid
JOIN vComputer vc ON vc.Guid = sps.PkgSvrId
WHERE rrsp.Name like '<%Package name%>'
order by rrsp.Name

When I deployed it to my test machine again I got the message in the logs:

PackageDownload    AeXPackageDelivery.dll    AeXNSAgent.exe    Failed to download package ‘{55555-3333-6666-7777-abcdefabcdef}’ from: \<SoftwareLibraryShare>55555-3333-6666-7777-abcdefabcdef, local blocks: 0/1, error: Bad Hash (0x80090002)

PackageDownload    AeXPackageDelivery.dll    AeXNSAgent.exe    Failed to download package ‘{55555-3333-6666-7777-abcdefabcdef}’ from:…, local blocks: 0/1, error: Bad Hash (0x80090002) 

I checked the sig and snapshot for that package on the NS and matched it with the same package on the package server. They both matched, but when I checked the same data on the endpoint via C:Program FilesAltirisAltiris AgentAgentsSoftwareManagementSoftware Delivery{55555-3333-6666-7777-abcdefabcdef}, everything is from the first time I deployed the MSI. Also, when the file gets downloaded, the MSI has 0 bytes and the task fails because it took longer than expected. I deployed it throughout the day and still the same issue. If I deploy it to a computer that never had the software, it deploys just. Any insight as to why this is happening and how to resolve it?

I have tried to delete the folder struction where the MSI is downloaded to and also deleted the whole folder C:Program FilesAltirisAltiris AgentAgentsSoftwareManagementSoftware Delivery{55555-3333-6666-7777-abcdefabcdef}. I noticed when I did that the folder {55555-3333-6666-7777-abcdefabcdef} never regenerates in C:Program FilesAltirisAltiris AgentAgentsSoftwareManagementSoftware Delivery.



SEP 15 – file hash calculated incorrectly

I need a solution

Just started to test SEP 15, and installed it on my test machine using the default policy.

It identified a file, NTOSKRNL.EXE, with the following filehash:


This hash is not correct, as using the powershell get-filehash command provides this instead:


Which is a known file on VT.  Any idea why Symantec’s hash calculation would be incorrect?  Or what I should do next?




Avamar 7.5: PuTTY releases older than v0.63 fail to connect with “Server unexpectedly closed network connection” due to new MAC entries in the SSH server configuration file

Article Number: 504576 Article Version: 6 Article Type: Break Fix

Avamar Server,Avamar Server 7.5.0-183

In cryptography, a message authentication code (MAC), sometimes known as a tag, is a short piece of information used to authenticate a message—in other words, to confirm that the message came from the stated sender (its authenticity) and has not been changed. The MAC value protects both a message’s data integrity as well as its authenticity, by allowing verifiers (who also possess the secret key) to detect any changes to the message content.

The sshd_config for Avamar 7.5.x or greater version supports the following MACs:

grep MAC /etc/ssh/sshd_config

MACs,hmac-sha2-512,,hmac-sha2-256,,,,hmac-ripemd160PermitEmptyPasswords no
After a fresh install when attempting to login to the Avamar grid using the 3rd party application PuTTY, following error is seen:

/var/log/messages can show the following error when logged via a console such as lights out port (RMC for Gen4t, RMM for Gen4s, vSphere Console for AVEs etc):

Oct 30 12:27:19 testavamar sshd[6087]: fatal: no matching mac found: client hmac-sha1,hmac-sha1-96,hmac-md5 server,hmac-sha2-512,,hmac-sha2-256,,,,hmac-ripemd160

PuTTY releases less than version 0.63 doesn’t support these MACs

Recent install of a 7.5.x system

MAC entries were added to the sshd config file (/etc/ssh/sshd_config) on the Avamar Server

Download a PuTTY version that is greater than or equal to 0.63 and then ssh into the Avamar Server.

Note: As of September 28, 2017, the latest version of PuTTy is 0.70


  • No Related Posts