Troubleshooting and FAQ
Why is my archive read-only?
Archive Witness begins archive sessions read-only by design. Integrity checks, metadata refresh, comparisons, and most evidence review do not need write access. Enable a controlled write only for an operation that actually needs to change archive storage.
Why didn't checking an unexpected file accept it?
Because checking is observation. If the path is correct, use Accept location after review. If you also intend the current bytes to become the saved checksum reference, use Accept location and save checksum.
Does an integrity match prove the file is original?
No. It proves the current bytes match the saved checksum evidence being compared. The strength of the historical conclusion depends on when and how that reference evidence was established.
Why can Media say Warning when Integrity matches?
They measure different things. Integrity compares bytes with saved checksum evidence. Media testing exercises decoding. The exact same bytes can match their saved checksum and still contain a stream or format problem.
Why can a recovered file read successfully even if DDRescue reported bad sectors?
A recovered image can contain readable replacement/zero-filled regions where original sectors were not recovered. Preserve the DDRescue mapfile and review the recovery guidance.
Can Archive Witness repair from another copy?
Peer comparison can help select another version and Restore can perform a controlled, verified replacement. Review Peer comparison and Restore before writing.
Where does Archive Witness store its application data?
The installed application stores catalogs, evidence history, settings, and job logs in %USERPROFILE%\Archive Witness Data. Registered archive files remain in their original locations. Open Settings to view the exact application-data path; click the displayed path to open the folder.
Does uninstall remove Archive Witness data?
No. Update, Repair, Reset, reinstall, and uninstall leave %USERPROFILE%\Archive Witness Data in place. To remove all retained application data, uninstall Archive Witness and then delete that folder. The licensing cache is separate package-private data and may be removed by Reset or uninstall.
How do I reset unexpected settings?
Open Settings, select Restore defaults, and then select Save settings. This resets preferences to their defaults without deleting catalogs, evidence history, archive files, licensing, or the completed first-run status.
Why am I not receiving beta updates?
Automatic checks require Archive Witness to have been installed through the website's Install with updates link. Installing the standalone MSIX does not establish that update association. Download the current .appinstaller file from the Archive Witness website and open it to repair the association. Update checks also require internet access and may be controlled by organizational Windows policy.
How do I switch between Beta and Stable?
Open the desired channel's Install with updates link on the Archive Witness website. Windows does not normally downgrade an installed package, and uninstalling a newer Beta does not roll its retained catalog data back to an older schema. Review Install, update, and switch release channels before leaving a Beta that is newer than Stable.
What should I include in a support request?
Describe what you expected, what happened, the Archive Witness version, and the relevant result or job details. Avoid sending private archive paths, filenames, or checksum evidence unless they are necessary and you are comfortable sharing them. See Support and feedback.