We're using the latest 4.4.4.0 C/C++ TA on Windows in a service that is running in an elevated mode. Our users are still from time to time are still experiencing this error, even though all their network interfaces are enabled and drivers are updated. It doesn't happen often, but we get someone roughly once a fortnight.
We're unable to help those users, because none of the FAQ steps apply. I can share the screenshots from Device Manager and Network Connections showing that all interfaces are enabled.
because none of the FAQ steps apply.
Covered in a few FAQ articles:
To sum up:
0. As mentioned before, there are no visible disabled adapters and customer updated their drivers.
1. We're not using static version of TA.
2. We're storing the key using `TA_CheckAndSavePKey` and `TA_SYSTEM` flag.
3. We're calling then `TA_Activate` and send some extra data with system info. Some users keep getting the `TA_E_ENABLE_NETWORK_ADAPTERS` error. The same key activates without issues on other machines.
I can privately send the product key of one of these users, but I'm not going to do this publicly on the forum.
Are they also on latest version of Windows? If not, also do that. Yes, Windows has bugs. And yes, Microsoft fixes bugs in Windows. But you actually have to update to get those fixes.
Arbitrarily staying back on Windows XP, 7, 8, or 10, is just silly internet nonsense that only benefits hackers.
So, update to Windows 11 (it's free), and apply all security & features updates.
If, after doing that, they still get errors, then the problem is they have faulty network adapters. Cheap chinese adapters, or incorrect drivers installed. Or both.
You can confirm this by running Get-WMIObject -Class "Win32_NetworkAdapter" | Format-List * in PowerShell and see if all the real adapters are correctly reported as a “physical adapter” and if they have an associated MAC address. If not, you know which adapter either has a broken driver install and/or the adapter itself is broken.
Long story short: if they actually apply all updates to Windows and actually update their drivers, and the hardware is functioning, then everything will work fine.
To whomever reads this in the future, this is the full PowerShell command that (if I understand the above description correctly) is going to show the physical network adapters and their mac addresses on a given system (so that you don't need to spend more time looking for it):Get-WmiObject -Class "Win32_NetworkAdapter" | Where-Object -Property PhysicalAdapter -eq True | Format-List -Property Name,PhysicalAdapter,MacAddress
In PowerShell later than 5.0, where Get-WmiObject is deprecated, use Get-CimInstance instead.
As for the viability of upgrading to Windows 11, we all know that this is not possible for all hardware configurations and Windows 10 is going to be supported until 2025, so it would be nice if the default support answer wasn't “you must buy new hardware to use our product”. And I'm not talking about some age-old configurations, but perfectly sensible i5 CPUs and motherboards.
As for the viability of upgrading to Windows 11, we all know that this is not possible for all hardware configurations and Windows 10 is going to be supported until 2025, so it would be nice if the default support answer wasn't “you must buy new hardware to use our product”.
I agree. However, driver writers (despite claiming compatibility with old versions of software) typically only write-for and test-on the newest versions of the OS.
That's just the reality of the software industry. I wish it wasn't. But it is. And we don't have the time or money to chase down every buggy driver that is ever released (because there are so goddamn many of them). So, the solution is almost always: update to the latest and things are magically fixed.
What shall we do when we get the following error from that PowerShell script:
Invalid class "Win32_NetworkAdapter"
User clearly has a working WiFi physical interface that is used to connect to a network.
Either they're on an old version of Windows or they have a corrupted / virus infected version of Windows.
… or they typed the command wrong.
I believe i'm experiecing the same issue here which I can't activate the product Across from http://www.acrosscenter.com which is using TurboActivate as their support told me and asked me to check https://wyday.com/limelm/help/faq/#disabled-adapters.
My computer was latest model Razer Blade 15 with Windows 11 which I believe it should be regarded as new enough.
The error code was 28 (TA_E_ENABLE_NETWORK_ADAPTERS).
My network interface screenshot: https://drive.google.com/file/d/1Ivaxf0QPrYeNGDnrgP88f3CATLwr0zv-/view?usp=sharing
I have checked the info from powershell by the command:
Get-WmiObject -Class "Win32_NetworkAdapter" | Format-List -Property Name,PhysicalAdapter,MacAddress
And got the following results:
Name : Microsoft Kernel Debug Network Adapter
PhysicalAdapter : False
MacAddress :Name : WAN Miniport (IKEv2)
PhysicalAdapter : False
MacAddress :Name : WAN Miniport (L2TP)
PhysicalAdapter : False
MacAddress :Name : WAN Miniport (PPTP)
PhysicalAdapter : False
MacAddress :Name : WAN Miniport (PPPOE)
PhysicalAdapter : False
MacAddress :Name : WAN Miniport (IP)
PhysicalAdapter : False
MacAddress : 2C:32:20:52:41:53Name : WAN Miniport (IPv6)
PhysicalAdapter : False
MacAddress : 2C:32:20:52:41:53Name : WAN Miniport (Network Monitor)
PhysicalAdapter : False
MacAddress : 2E:93:20:52:41:53Name : Bluetooth Device (Personal Area Network)
PhysicalAdapter : True
MacAddress : 4C:44:5B:DB:FB:09Name : Killer(R) Wi-Fi 6E AX1690i 160MHz Wireless Network Adapter (411NGW)
PhysicalAdapter : False
MacAddress : 4C:44:5B:DB:FB:05Name : WAN Miniport (SSTP)
PhysicalAdapter : False
MacAddress :
Hope it helps to find out the root cause and please let me know if any further information needed.
Thanks all for your help on this issue in advance.
Your physical adapter is not reporting as a physical adapter.
1. Disable VM.
2. Update the drivers (and install the correct one for your adapters).
3. Update Windows.
Also, we don't provide support for end-users. Contact the company that provided you the software. Locking this topic.
Bart Walczak
Wyatt O'Day
Vincent Tse