TA_E_ENABLE_NETWORK_ADAPTERS exception on latest Windows 10 version

Hi, I am getting exception 0x1c (28) thrown from TA_Activate() on 64-bit Windows 10 Pro Version 1803 running on a standard HP Z400 (Xeon E5-1620).

This fails with the Example.C case (in API/C) as distributed with the TurboActivate software (of course using our own GUID and product key).

I have read the existing thread on this topic as referenced from the TurboActivate.h header file. My network adapter (Intel 82579LM Gigabit Adapter) is enabled and has the latest drivers installed for it.

I can get it to work ONLY if am running it as administrator, but this is generally not possible for all of my intended clients.

This is a showstopper for us. Please help asap.

Also, the same Example.c code activates fine on a Mac. The problem appears to be Windows 10.

1. After you run the app as admin does it fix the problem when running under non-admin? If so, then TurboActivate fixed the problem of the adapter (TA has a number of workarounds and fixes built in to fix customers misconfigured computers. But a lot to f the fixes require admin rights)

2. What version of TurboActivate?

Thank you for your speedy reply. To answer your questions,

1. The problem does not go away after running it as admin. I still get the same error when trying to activate with a non-admin user.

2. I am using the dynamic library, downloaded directly from my account on your site two days ago.

In the upcoming newer version of TA (4.1 -- out soon, no hard date), we're adding a new error code that you might get instead of TA_E_ENABLE_NETWORK_ADAPTERS. Namely, "TA_E_BROKEN_WMI"

Walk through the steps (including the PowerShell command): https://wyday.com/limelm/help/faq/#fix-broken-wmi

That error really only happens because one of the following happened:

1. A driver was not correctly installed.2. The Windows update failed partially.3. Some sort of "cleaner" "helper" utility broke the PC.

I found the problem. I am working on a Unix emulator environment within Windows (UWIN). From within Windows (standard Explorer or CMD shell), everything seems to be working correctly (and, TA_Activate runs successfully). However, an app launched from a UWIN shell will not activate, and that is where I get the failure (even though the network itself is just as accessible and working fine).

This will not be a problem for us though, since we only use UWIN for development purposes. I am not sure it is worth the trouble to get it to activate from within UWIN.

Reply
Discard post