Thank you, this screenshot helps more than the key text. I see two things in the dialog that matter:
There is a Registration Name field set to “misi”. The key data posted here only encodes the product, version, and HWID. There is nothing in it that contains a name, so either the application ignores this field or incorporates it into the signature check. If it is part of that check, the name must match exactly what was used when the key was created, including capitalization. This follows from the key structure, not from something I verified against the binary.
The key field is shown scrolled to the middle of the string, so I cannot tell whether you pasted the entire thing. The key must
ETS1.begin with and contain exactly one period, with no spaces, line breaks, or anything truncated from the end. Clear the field completely, paste it once, then scroll to the beginning and confirm
ETS1.that it is there before pressing OK. A single stray newline character from a forum post is enough to make the signature fail. The nine-group HWID issue from my previous post still applies: the closing one is visible in the dialog
-1C, and this group is not included in the key payload. If you downloaded it from this resource page two hours ago, the build is v1.02, which does not match the previously mentioned 1.0.4 version. So:
- The exact version shown in the title bar or About section, typed out.
- The exact error message displayed by the application after pressing OK, typed out.
If it turns out that the key must be tied to the complete nine-group HWID or to the registration name, I cannot provide it here. Post the HWID, registration name, and version in the resource discussion so that Bin can reissue it.