| Previous | Next |
| STATUS_GENERIC_COMMAND_FAILED | STATUS_TRANSACTIONAL_CONFLICT |
STATUS_SXS_FILE_HASH_MISSING
The manifest has no usable verification hash for an assembly file
STATUS_SXS_FILE_HASH_MISSING means that an assembly file lacks the verification information expected by the side-by-side operation. Assembly manifests can provide a hashalg and hash for a declared file; when verification is required, absence of that metadata is distinct from a computed hash mismatch.
Do not invent or copy a hash into an installed manifest without rebuilding the package. The algorithm, encoded value and file bytes must originate from the same trusted build. A missing hash is a metadata/packaging defect, whereas STATUS_SXS_FILE_HASH_MISMATCH means existing metadata did not validate the file.
What to inspect
- Inspect the exact
fileelement and determine whether it lackshash,hashalgor both. - Compare the manifest with the producer's packaged artifact to identify whether metadata was stripped or generated incorrectly.
- Redeploy the complete verified assembly instead of editing the component-store manifest in place.
References
- Microsoft: application manifests
- Microsoft: assembly manifests
- Wine: activation-context implementation
Looking for a different code? Search another status or error code.
