Error Cases

Pomfort SealVerify can detect different error cases. The application will tell you the reason of the error. In any case the Seal Info will give you the needed information to contact the original sealer of the drive to talk to him about a possible reason and solution to the problem. Here are the different error cases the application will be able to give you.

File Does Not Exist

As soon as a file fails you will already see it in the ongoing process:

Ongoing process with “File does not exist” error

When the verification is completed you will see the clear protest sign that clearly expresses the failed verification. You can find the reason for the failure in the verification result column or select the failed file in the table for more details about it:


Hash Is Not Equal

In this case the file exists but the hash doesn’t match with the original checksum:

Screen Shot 2016-05-20 at 10.26.18

File Size Not Equal

This error case is a special case of hashes do not match. It will tell you additionally that the file size of the existing file does not match the original:

Screen Shot 2016-05-20 at 10.29.20

No MHL File Found / MHL File Was Altered

If the drive is sealed and an MHL file was altered or does not exist anymore, Pomfort SealVerify recognizes that the seal was broken. You will see the following error message:

Screen Shot 2016-05-20 at 10.32.13

Files Uncheckable

In case you are only verifying MHL files without a seal or files have been copied by hand onto the drive after sealing it with Silverstack you may run into files that cannot be checked because they are not referenced in any MHL file. You will get the following finished verification status:

Screen Shot 2016-05-20 at 10.45.28

Unresolvable Error

A critical error happens e.g. when the MHL files cannot be parsed by Pomfort SealVerify:

Critical Error


One possible reason for this error could e.g. be that the drive was not sealed and the MHL file is corrupt.