Network Adapters Problems

Hi,

We've notice that since the new version of Turbo Activate a lot of our customers have problems registering and are getting TA_ENABLE_NETWORK_ADAPTERS error.

I've solved this manually with some of the customers however this is not sustainable if you have thousands of licenses and therefore thousands of potential problems. The problem is usually solvable by updating Windows, checking if there are any malfunctioning Network Adapters, removing them manually, sometimes reinstalling drivers, often changing customer's antivirus settings etc. Unfortunately most of our (and I am sure other users') customers are not computer experts. Following those steps with them is very time consuming and frustrating for both sides. I can imagine it's not a problem if you have corporate customers and sell hundreds of licenses to to one customer but it's very difficult to handle if you sell to individual customers all having different systems, hardware, 3rd party software etc.

It would be very useful for us if Network Adapters were not used in hardware fingerprint or if we could have an option to disable that. This problem already cost us tens of man hours and is likely to cost more in the future. Judging from frequency it pops up in the support forum we are not the only ones suffering from it.

I think the issue is urgent. It's killing our productivity and reputation. It pops up very often even on support forum here. Please consider fixing the issue.

The next version of TurboActivate will give more specific errors for cases where things are broken (and you'll be able to give a magic "Fix this problem" button in your app that runs through the fix).

I get that customers mis-configure their machine (install broken drivers, don't update their computers, actively block updates, run broken anti-viruses, etc.). That being said, taking into account network adapters as a fraction of the fingerprint is important. We tried not doing it, or even just doing it for non-customer-broken network adapters. It ended in a disaster.

I agree it's a fault of system misconfiguration or malicious software (usually some random 3rd party antiviruses) and that must be frustrating for you that you can't just use official Windows APIs and avoid problems.

Still it's a big practical problem and I want to thank you for considering it. Even something like "this specific {name} adapter is malfunctioning" would already be very helpful.

Reply
Discard post