I've upgraded an App-v program on the App-V sequencer. I updated the package on my SCCM server and then added a Mandatory date to the existing advertisment to re-deploy the package. I tested the app on a few clients and they all got this error The program for advertisement "DA0204C3 has failed because download of the content "DA000144" - "[Virtual application]" has failed. The download failed because the content downloaded to the client does not match the content specified in the content source. Possible causes: The content on the distribution point has been manually modified, or a local administrator on the computer has modified the content in the computer's hash. Solution: Refresh the content on the distribution point and retry the download. I've refreshed the content but still get the error. Are there any tricks to getting this to work?Orange County District Attorney

Have you already tried upgrading the package to a new source version? Refreshing does not regenerate the hash IIRC.

Yes, I have a few times. I noticed that when updating the App-v package I used the "Update Package" right-click menu option. I pointed the wizard at the newly-updated files. After this, the hash issues started. This morning I came in to take a look at my package source and smspkgd$ locations to see if I could see any problems with the files such as hidden files perhaps. The source and SCCM share locations were empty. Not sure what happened. I did then copy the updated-files, manually, to the package source location and then updated all DPs with a new source version. This worked. I think in the future I'll stay away from the "Update Package" menu option and instead manually copy the new files to the source location. I had read that when packages are configured as "compressed" when they are updated, the compressed package is deleted before being updated / replaced. This would seem to help alleviate any hash-related problems. Although I can't see this as an option for App-v packages, perhaps for other standard SCCM packages I might use this strategy.Orange County District Attorney

ConfigMgr never touches (other than 'read') the package source locations or updates files in that directory. It just copies the content to the DPs. So I don't know what you expected that ConfigMgr will do with the source files ...