Lost activations after upgrading to Windows 10

Hey Matt,

Upgrading the operating system won't cause users to be deactivated unless they're also changing other things. So, for instance, if they change the operating system and replace the harddrive, then yes they'll need to reactivate.

We're changing this behavior in TurboActivate 4.0 (so that an operating system upgrade isn't a "hard change"). Also, in the next week, we'll be changing the algorithm server-side so that customers who get deactivated because of changing the OS and replacing the harddrive, they can just re-activate using the same product key.

Hi Wyatt,

Sounds good in principle, but I am now getting a couple of support emails a day from people who's activations have been nuked. Not sure why - perhaps I am using too old a version of TurboActivate?

Will your server side changes work with older TA versions or will I need to update and make a release? Unfortunately getting people to upgrade versions is about as likely as getting them to read an email asking them to deactivate/reactivate during the W10 upgrade..

Any news on verified trials?

cheers,Matt

FYI our deployed TA version is 3.4.3

Firstly, you should use 3.4.6. A number of bugs are fixed, including some false positives where computers were seen as different even though they weren't.

Not sure why - perhaps I am using too old a version of TurboActivate?

Yes, that's the first problem.

Will your server side changes work with older TA versions or will I need to update and make a release?

You should release an updated version with the latest TurboActivate. Also, when we release the server-side changes, existing customers will just be able to re-activate with the same product key (as I said above). Unless of course they changed more than the OS + one other soft component (like harddrive / RAM / graphics card).

Any news on verified trials?

It's coming with TA 4.0.

Thanks Wyatt,One quick further question: I see that you have x86 and x64 versions of the TA.exe as well as the dll. Currently I do the TA_BOTH thing which works fine, but deploy the 32 bit TA.exe which also works fine. The new version seems to work fine as well - can I continue to deploy just the 32 bit TA.exe?

thanks,Matt

Yes, but make sure the version of TurboActivate.exe matches the version of the TurboActivate.dlls you're using. (So, always use the .exe/.dll pair from the same TurboActivate version).

Hello Wyatt,

is there a possibility to avoid the lost activation when a user upgraded to Win 10? We get a lot of support emails - every license has to be manually deactivated if a user switches to Win 10 (not making any other changes).

Thanks!Jan

Hi Wyatt, I've followed all your instructions in this topic, and our software uses the latest version of TurboActivate. However, our users are still losing their activations when upgrading to Windows 10. According to your comment earlier, "Upgrading the operating system won't cause users to be deactivated unless they're also changing other things". Many of our users haven't changed anything except the operating system, yet they are still encountering the problem. Please help!

Many of our users haven't changed anything except the operating system, yet they are still encountering the problem.

My guess is that they did change multiple things, but send me a sample of product keys to wyatt@wyday.com. The keys should have:

1. A previous activation.
2. A new activation that TurboActivate sees as different.

If you don't have keys like that, then you need to tell me their old key and their new key.