argus17We have had numerous customers report that the moment they installed the new Windows 10 anniversary update, it breaks their turboactivate activation and they have to activate again. If you remember, this same issue occurred when people were upgrading from Windows 7 to Windows 10 and it caused major headaches back then, since almost every customer had to reactivate again. Is this seriously going to happen every time there is any major Windows update? How in the heck are you actually storing the activation data? I have to imagine there is a better alternative, since I have run the anniversary update myself, and it doesn't seem to mess with the saved data of any other program I have installed. But sure enough, both of the applications I have that use turboactivate both broke. And of course, if you aren't allowed to freely activate new computers all the time, all of your customers will start emailing you saying they have run out of activations.
As I said, we already went through this once since turboactivate broke when you upgraded to Windows 10, and apparently we are starting to go through it all again.
Between this, the terrible issue with network adapter fingerprinting, and the fact that 4.0 is over 6 months behind schedule, I'm seriously starting to doubt the future of this product. This is just far too many serious issues. We have other products that use 2 other licensing options, and neither of them have had any of these issues.
Anyways, I figured people should be aware of these issues and start preparing for their angry customers contacting them in bulk
Are you using TA_SYSTEM or TA_USER when you save the activation data? We have had no reported issues when TA_SYSTEM is used. And we cannot reproduce it on our end.
Also, if it's a case of the customer losing the activation data (because TA_USER is used instead of TA_SYSTEM), simply re-activating with the same product key is the fix. It will use the same activation in LimeLM.
We're going to look into this more and try to reproduce it.
In the meantime, like I said above, the solution is for the customer to re-activate with the same key. You don't need to deactivate them in the interface -- LimeLM will recognize the same computer.
argus17Wyatt wrote:> In the meantime, like I said above, the solution is for the customer to re-activate> with the same key. You don't need to deactivate them in the interface -- LimeLM> will recognize the same computer.
That is what we initially recommended, but the customers all informed us that is actually DOES think it's a new computer apparently, so they can't just re-activate unless they have spare activations. That's why we are getting contacted so much, because these customers have all run out of spare activations, since turboactivate seems to think that the computer has changed during the update. Again, this exact same thing happened when people originally upgraded to Windows 10 over a year ago. They couldn't just re-activate, since turboactivate thought it was a new computer. So it is a bit more serious.
Hmm... can you send me a couple of product keys where (a) this is happening to customers upgrading from windows 10 to Windows 10 Anniversary and (b) where they've "re-activated" with the same computer.
There was an issue with customers "losing" their activation who had (a) multiple (more than 1) network cards who (b) upgraded from Old Windows (XP, Vista, 7, 8, 8.1) to Windows 10. This was due to a significant change in how Windows 10 reports network devices. A temporary workaround is in TurboActivate 3.4.7 (which has been out for about 2 weeks), and a permanent fix is in 4.0 (out soon).
We have not seen this behavior when upgrading to new Windows 10 builds.
But please send me a couple of keys showing the behavior you're reporting. My email is wyatt@wyday.com
I had been thinking of upgrading to Win10 Anniversary Edition build 1607 anyway (from the previous Win10 build), but after reading this I brought it forward on my home PC to see if I have a support problem.
I have _not_ been able to reproduce this problem. I'm not saying the OP is wrong, but I'm glad to report that not every LimeLM installation seems to be affected.
Btw my app always registers using TA_USER, because I don't want the installer to require elevated permissions. That would cause problems in my market area.
argus17DonMilne wrote:> I have _not_ been able to reproduce this problem. I'm not saying the OP is> wrong, but I'm glad to report that not every LimeLM installation seems to> be affected.> > Btw my app always registers using TA_USER, because I don't want the> installer to require elevated permissions. That would cause problems in my> market area.Yes, that's not surprising. It seems to be a problem for TA_SYSTEM only, so if you're using TA_USER, then this thread isn't relevant. We have many more reports now in the last few weeks, so this continues to be a problem.
Why is it that the original Windows 10 install and these major Windows 10 updates keep erasing the lime activation data and making the software think it's a new computer?
Hmm. Wyatt earlier on seemed to be suggesting that the problem is more with TA_USER, and he'd never heard of it happening with TA_SYSTEM. Confusing.
Oh, and in case I wasn't clear earlier: I was not required to reactivate. The Win10 upgrade seemed to be no affect at all.
>> "Why is it that the original Windows 10 install and these major Windows 10 updates keep erasing the lime activation data and making the software think it's a new computer?"
You need to email me product keys showing this behavior. My guess, 1 of 2 things is happening:
1. The customer is using your app on a different computer and lying about it.
Or...
2. The customer isn't upgrading from Windows 10 to Windows 10 Anniversary, but rather upgrading from old-Windows (XP, Vista, 7, 8, 8.1) to Windows 10 Anniversary AND they have multiple network cards. The solution is to use TA 3.4.7 in the short term. The long term solution is to use TA 4.0 (when it's out -- soon).
I was guessing about TA_USER / TA_SYSTEM. Much more information is needed to make any sort of accurate statement. If the user is "becoming deactivated" it's likely not because those files are being deleted. Especially if they cannot re-activated with the same product key.
Upgrading between Windows 10 builds and "losing the activation" is not reproducible by us. We've tried. We have many computers some running on the "Release" Windows 10 build, some running on the "Insider" build (meaning "large system upgrades" come bi-weekly). We've never been able to reproduce this.
Please give me more information so we can look into this.
