Post #541
Online now
- Joined
- 09.05.2025
- Messages
- 3,227
- Reaction score
- 884
- Location
- United States
Before anything else, check the three things that cause this most often:
- Registration name must be entered exactly as issued — japps1, all lowercase, no spaces. The key is signed against that string, so even a capital J will fail.
- Copy the whole key including the trailing ==. If you select it from the quote box it's easy to drop the last characters or pick up a line break/trailing space. Paste into Notepad first, confirm it's one single line, then paste into the app.
- HWID must still match. Reopen the registration window and compare what it shows now against 4C2A-CE74-C00A-7118-45FF-0166-46F8-BBE4-C9. Some setups shift the HWID after a Windows update, network adapter change, or if you run the exe from a different path/VM.
Also make sure you're on the current 1.0.4 build from the resource page — that release included fixes for activation/HWID handling, and an older exe can reject a key generated for the new scheme.
If all three check out and it still rejects, post a screenshot of the registration window showing the HWID field and the version string in the title bar/about, and confirm whether you're launching it as Administrator.
