TurboActivate randomly returning TA_E_EXPIRED or working as expected on some Windows machines

Hi there,

We are having problems handling what we believe are false positives inTurboActivate anti-tampering checks, but since we are using self-made Pythonbindings we are not really sure if the problem lies on our side instead.

Our application flow is the following:

1. When the application starts, it checks for activation status: 1a. First, a call to IsGenuine is made 1b. If that fails, we resort back to IsActivated so that we can allow users without a persistent Internet connection to still be able to use the product (we don't use IsGenuineEx's grace period features because we are not interested in a time-limited grace period, our clients may have an Internet connection the first time the application is installed, for activation purposes and then be off-line indefinitely).2. If TurboActivate says that everything is fine we start the application as normal, otherwise we show an input dialog asking for the activation code.3. If users enter the activation code we call CheckAndSavePKey() and then Activate()4. We go back to point 1 until either the product is activated, the user quits or he decides to start a "demo" version with most features disabled.

Our binding and a usage example (at the bottom) can be found here (the GUID isdeliberately hidden): http://pastebin.com/u09NA2sm

So far the problem has affected only Windows users (Windows 7 in particular, weare not aware of any user on Windows 8 yet) and while in one case the problemwas transient, we have two machines where we aren't able to activate theproduct. One is a development workstation, while the other is a machine at aclient's premises.

* We are using TurboActivate v3.4.2 (64 bit on Linux, 32 bit on Windows)* The machine in question has the right date, time and time zone settings* Time on that machine is synchronized through the Internet (Control Panel -> Clock, Language and Region -> Date and Time -> Internet Time on Windows 7) using what we believe are standard settings on out-of-the-box Windows 7 installations.* That machine has been rebooted several times, yet the situation didn't improve.

We're looking into this right now. Shoot me an email (wyatt@wyday.com) and I'll send you a test version for Windows so you can see if it fixes the problem for you (it works here, but I just want to make sure).

I've sent you the release candidate version of TurboActivate 3.4.3. Tell me if this fixes the customer's problem. If so, we'll release the fix for all platforms today.

If you don't get the email please tell me and I'll arrange for you to get it another way.

We've just released TurboActivate 3.4.3. This should fix that problem.