SCCM error 0x80091007 is a content validation problem: during a Configuration Manager task sequence or a content download, the hash of the content the client received does not match the hash it expected. I see it most often when package or application content is downloaded from a Distribution Point.
The error message
Failed to run the action.
The hash value is not correct.
Error: 0x800910071. Use smsts.log to find which content failed
Instead of redistributing random packages, I first look in smsts.log for the step that returned 0x80091007 and the package or content ID it was working on.
2. Check the content status on the Distribution Point
Confirm that the content is in a successful state on the target DP. If the content status is failed or inconsistent, validate the content and redistribute it to the DP when needed.
3. Verify the Boundary Group and the selected DP
Check in LocationServices.log which Distribution Point the client actually used. If the problem only happens on a specific subnet or site, review the Boundary Group to DP relationship as well.
4. Read the client content logs
CAS.log: content and cache decisionsContentTransferManager.log: the transfer requestDataTransferService.log: the actual data transfer
Reading these logs on the same timeline shows which content the client downloaded and from which source.
5. Check the client cache
If you suspect corrupt or partially downloaded content in the cache, first confirm the content ID from the logs. Narrow the problem down to that content instead of blindly deleting the whole CCMCache.
6. If the source content changed
If the package or application source files were changed manually after the content was updated in Configuration Manager, the version on the DP and the expected hash can drift apart. Manage source changes through the Update Content process in Configuration Manager.
When does a RAM check make sense?
You will find suggestions online to replace memory for 0x80091007. If the same content keeps failing the hash check on only one device, and the DP and content chain checks out as healthy, a hardware or memory test can be a secondary check. It should not be the first troubleshooting step.
My troubleshooting order
- Find the failing step and content in
smsts.log. - Verify the DP distribution in Content Status.
- Check the Boundary Group and the selected DP.
- Follow the LocationServices → CAS → ContentTransferManager → DataTransferService chain.
- Check whether the source content was changed afterwards.
- Redistribute the affected content if needed.
- If the same content works on other clients but fails on one device, move on to the client cache, disk and RAM layer.
Conclusion
With 0x80091007 the key question is not “should I redistribute the package?” but which content came from which DP, and why did the hash not match? When you read the logs and the content status together, the problem can be narrowed down to the DP, boundary, transfer, cache or source content layer.
