Check integrity and review changes

Use Check integrity when you want to know whether current file bytes still agree with saved checksum evidence.

What the check does

Archive Witness completely reads the selected file and calculates the configured checksums needed for comparison. The result is retained as an observation. The saved checksum is not replaced merely because a check ran.

A match means the current bytes agree with the compared saved checksum evidence. A mismatch means they do not.

Unexpected files

An unexpected path is first a Location question. Checking the file can give you more evidence, but a unique match does not automatically accept the path.

After review you may choose:

• Accept location — adopt the path without changing checksum authority.
• Accept location and save checksum — adopt the path and save the reviewed/current byte identity as checksum authority.

If a fresh read during the stronger action no longer matches what you reviewed, Archive Witness leaves the location unexpected and does not save the checksum. Review the updated evidence instead.

Changed versions

When current bytes differ and the change is intentional, Accept current version lets you choose the evidence used for the decision.

For one file, Archive Witness can offer the latest suitable check or a fresh read. For multiple files, it can use available checks and read the rest, or read every selected file again. The interface shows evidence times rather than applying a hidden age cutoff.

Accepting a version changes the saved checksum authority. It does not write different content to the archive.

Unexpected does not mean corrupted

A new path, missing expected file, checksum mismatch, or media warning are distinct findings. Review the relevant Location, Integrity, and Media evidence before deciding what happened.