Hash Mismatch issues can be a big headache for the technical teams. Through this post, I am trying to document the SCCM Hash Mismatch issue in my terms. Most of the Hash Mismatch issues are identified through CAS.log “Hash does not match expected.”
Latest Posts – Fix Report Server Cannot Open A Connection Error ConfigMgr | SCCM HTMD Blog (anoopcnair.com) & 11 Days Of Free Intune Training Course By HTMD Community – HTMD Blog #2 (howtomanagedevices.com)
FIX SCCM Hash Mismatch Issues Troubleshooting Guide
P.S – Download HASHDIR.EXE (This HASHDIR.EXE won’t work with SCCM Current Branch) – https://gallery.technet.microsoft.com/where-to-HASHDIRexe-tool-bc4b2f6f . However, you can try to download the script to fix SCCM content mismatch issues here. WMI & ContentLib mismatch – Get-InvalidPKG.
There could be several reasons for the Hash Mismatch issue, such as explained below. FIX SCCM Hash Mismatch Issues Troubleshooting Guide.
1. For Windows 2008 site servers, check whether the below settings are enabled in IIS. For a distribution point that allows clients to transfer content from this distribution point using BITS, HTTP, and HTTPS, for WebDAV Behavior, set Allow hidden files to be listed to True.
2. ConfigMgr 2007 clients may fail to download packages from a Server Share DP with a content hash mismatch error. There is a known issue with IIS 6.0 WEBDAV that occurs when the Virtual Directory points to the root of the drive as the path, such as Z:\. This causes our failure above.
3. Attempts to update or distribute a package to a Branch DP fail with HostingIncomplete and PDPHashMismatchEvent error. Every indication is that this is a hash mismatch; however, testing shows that the hash matches and the directory contents are the same on the Source, DP, and BDP, the only indication of the hash mismatch is in the peerdpagent.log.
4. SMSTS error “Hash could not be matched for the downloaded content.” When deploying a software package in SCCM 2007 via a Task Sequence, containing files containing names containing extended ASCII characters, the Task Sequence may fail with an error code 80004005. An example would be the Spanish word año, where there’s a tilde over the ‘n.’
In my case, the issue was different. If I have a Hash Mismatch issue in the environment, I always prefer to compare the size of packages in the local DP and the parent server? (there could be some diff in size… maybe in KBs or Bytes). Also, compare the PCK file size on both servers? FIX SCCM Hash Mismatch Issues Troubleshooting Guide.
Documented process FIX SCCM Hash Mismatch Issues Troubleshooting Guide
1. Update the package and wait for 1 or 2 hours, depending upon the connectivity.
2. Check the CAS.log to confirm whether the issue has been resolved or not.
3. If “Not Resolved,” then go to step 4.
4. Sometimes, Hash Mismatch may happen because of some hidden files. To resolve that, open up a command window in the root directory that contains your package.
Type Dir /S /A: H and hit enter.
Type attrib -H /S.
5 . Update the package and wait for 1 or 2 hours, depending upon the connectivity. If the issue persists, go to step 6.
6. Remove the package and wait for 1 0r 2 hours (ensure that the package is removed from the DP). Also, I would suggest you remove the PCK file related to that package.
7. Re-distribute the package and check whether the issue is resolved.
These steps should resolve most of the Hash Mismatch issues.
P.S – Download HashDir tool and More Details on Hash Mismatch – See, Link
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…