Your company's ad could live here and reach over 50,000 people a month!

Share This Post

How to deal with multiple hash mismatches during OS Deployment

We recently added another distribution point to the mix and for some reason the task sequences started failing getting the following error at different sections:

The hash value is not correct. (Error: 80091007; Source: Windows)

For each program that does this we found the fix to be

Refresh the distribution points, then update the distribution point straight after. This worked but the time consuming process of re-imaging each time to check whether the packages would download was a problem, also packages that only run in certain scenarios wouldn’t get checked. So we went and created Stand Alone task sequence media, when you create the stand alone cd it will run a hash check for each package it copies to the iso. It then fails and the log CreateTsMedia (C:\Program Files (x86)\Microsoft Configuration Manager\AdminUI\AdminUILog) shows what package you need to refresh and update.

Staging package BU100121
Hash could not be matched for the downloaded content. Original ContentHash = DA8FB4B69DE109376D6B40194BF608D0D6707521, Downloaded ContentHash = F0304FDC174B482DDD2FC17934DF36BE3E24B9F3

I believe you may need to create stand alone media for each OS Deployment/Distribution Point to ensure all the hash values on all the DPs are correct.

Share This Post

I am an SOE Engineer working mainly with SCCM. I hope some of my blogs can help others deal with problems I have come across.

Leave a Reply