My windows app uses the cryptlex lexactivator library. Recently I’ve had a lot of reports from customers that the app is forgetting the activation code, so that when they start the app it thinks it is not activated.
This has been happening for an old version of the app, which uses version v3.11.1 of lexactivator.
So far I cannot explain why this is happening.
Can you give some pointers of what might be going wrong, and how to fix it?
Have you had any similar reports, maybe its triggered by a windows update or something?
This issue was caused by a temporary glitch on February 7 (Friday), impacting users running LexActivator versions older than 3.19.0.
We understand that many users are still using older versions, and we sincerely regret any disruption this may have caused. However, we strongly suggest you to keep the LexActivator version up to date.
we strongly suggest you to keep the LexActivator version up to date.
Yes I do in general.
However this is for “v4” of our app, which we no longer update.
Our app is now at “v5”, and this is the one I update regularly and do update the lexactivator library.
