Copied files have different SHA256 hashes
Documentation: Microsoft Learn
Work the problem
A transfer fails verification
Fictional case: Source and destination have the same filename and size, but their SHA256 hashes differ. The source application was still writing during the copy.
Reasoning notebook
Record the evidence that supports your answer and the check you would run next. Your notes stay in this browser — nothing is uploaded.
Why it happens
Hashing compares bytes. Incomplete copies, encoding conversion, changed line endings or a file modified after copying can produce different results. Comparing hashes computed with different algorithms is also invalid.
Check this first
What to look for
Use a stable source so both hashes describe the same version. Then investigate the transfer if they still differ.
Working through it
- Confirm that the two literal paths refer to the intended source and copy, and that both results use SHA256.
- Check whether an editor or transfer process changed encoding or line endings. Stop active writers before repeating the comparison.
- If a fresh copy is appropriate, copy again from the trusted source and recompute both hashes after the copy finishes.
Avoiding it next time
Verify the repair: Compare hashes of the same stable source version and destination, then verify the consuming application can use the file.
Primary documentation
Work through the incident
Investigate mismatched file hashes
A copied deployment package has a different SHA256 hash at the destination.
The sandbox is visible now. Sign in with Google only when you run or check a task; commands and temporary files are discarded when you leave.
Run a command to inspect its result.