A user of mine replaced the motherboard in one of their PC's, but did NOT reinstall Windows.
Now they are getting an Activation Error, complaining that there are network adapters on the system that are disabled.
I gave them the link to the help FAQ and they followed all the steps for fixing this issue, but it did not make a difference. They have both network adapters enabled, and they deleted any hidden adapters, and have run it in Administrator mode too.
We are all thinking that somehow TA remembers the old motherboard's network adapters, even though they are long gone.
What steps should we take?
Thanks,Paul
Hey Paul,
More information is needed:
1. Version of Windows (version & architecture).2. Version of TurboActivate (version & architecture).3. Exact function call failing.4. Exact parameters to that function that is failing.5. Exact return code from the function that is failing.6. Exact steps taken (did they run Windows update? Did they actually update their drivers? how exactly did they "delete[...] any hidden adapters"?)
JRICome on... You had plenty of reports about faulty "Disabled Network Adapters" reports from TA/TF in the past. We have customers contacting us about this issue every months. TA/TF is the only problematic licensing software on their computer. No matter what you say about "stupid" users messing up with their computers (that's your opinion and I do not agree with that), or that you have enhanced this in a the past... an end-user should NEVER have to type advanced command lines to fix the behavior of any licensing library.
>> "Come on... You had plenty of reports about faulty "Disabled Network Adapters" reports from TA/TF in the past."
All incorrect detection of not-enabled adapters have been fixed more than 2 years ago. So, use the latest version of TA / TF (4.0.9.6 as of this moment).
>> "We have customers contacting us about this issue every months."
Are they on modern Windows (8, 8.1, 10)? They should have no problem with adapters enabled or disabled. If they do, they should do 2 things:
1. Update their network drivers.2. Update their Windows installation (don't follow stupid blog-spam advice to turn off automatic updates).
If they still have problems on modern Windows (and you're using the latest TA/TF *and* they updated their drivers and OS) then contact us and we'll investigate.
We haven't had legitimate reports of TA or TF returning this error on modern Windows. If a customer got this error on modern Windows then one of the following was always true:
1. They weren't using the latest TA or TF (don't waste your time -- or our time -- tracking down bugs we've already fixed)
2. They had disabled Windows updates. Don't do this. It's incredibly stupid to run un-secured software.
3. They were using buggy network drivers (solved by an update to their drivers).
This is all covered here (it's a frequently asked question, hence it being answered in the FAQ): https://wyday.com/limelm/help/faq/#disabled-adapters
>> "an end-user should NEVER have to type advanced command lines to fix the behavior of any licensing library."
Agreed. And they don't have to if you're using the latest version of TA / TF (for the past 2 years) and they have their PC up to date.
If you believe TA / TF is incorrectly detecting network adapters (i.e. saying network adapters are disabled when they appear to be enabled) then report it to us and we'll investigate.
Wyatt wrote:> Hey Paul,> > More information is needed:> > 1. Version of Windows (version & architecture).> 2. Version of TurboActivate (version & architecture).> 3. Exact function call failing.> 4. Exact parameters to that function that is failing.> 5. Exact return code from the function that is failing.> 6. Exact steps taken (did they run Windows update? Did they actually update> their drivers? how exactly did they "delete[...] any hidden> adapters"?)
Wyatt,
The user reported to me that the problem went away after a couple days. They never provided me the requested info. I'm not sure if they took any more steps, but the impression they gave is that no further steps were taken, merely waited a couple days and tried again.
Not sure if that helps you any in understanding the original problem. Obviously, this is a rare situation in which a user replaced a motherboard (replacement was a different model with different network adapters) and didn't reinstall windows.
Paul
