Verifying files from clipboard using certain hash does not work

[white]

The only advantage would be to have 4 entries instead of 7 in the combobox.

No, the concept becomes much simpler, less confusing, and has more options. When the verification fails or you know it will fail, you specifically choose another hash type (for this time only). If you want to do more complex things and or save the settings, you choose Configure.

Suppose you verify using a 224-bit hash on the clipboard and verification fails while trying with SHA2, then you can choose SHA3 or SHA2+SHA3. Why would the user choose SHA2+SHA3 when SHA2 already failed? That's confusing.

When changing the option to SHA2+SHA3, settings are stored permanent (stored in wincmd.ini) or for this TC session only, without this being transparent.

My suggestion also provides more options in that the users gets full control over which hash types are checked, in which order they are checked, and this is configured for all hash lengths separately.

The disadvantage would be that you can no longer choose a combination with just 2 clicks.

True, but it is unlikely that people often want to choose a combination. And it is likely that offering a combination there confuses people.

[ghisler(Author)]

Why would the user choose SHA2+SHA3 when SHA2 already failed?

Because they may have a mix of SHA2 and SHA3 hashes, and after having to switch between the two a few times, they realize that and choose the always calculate both.