Enable Network Adapters issueAnswered

Hello,

I'm seeing the “Enable Network Adapters” ( TA_E_ENABLE_NETWORK_ADAPTERS ) error on several PCs we have in the field… and as of today, that includes my own Windows 10 desktop PC. 

  1. Our application is run on (no less than) Windows 10 / 11 x64 only.  We have used TurboActivate for several years without much issue.  
  2. I have already updated my Network Adapters to the latest drivers.  
  3. We are using the latest Turbo Activate DLL version for Windows - v5.0.2.0.  (It is NOT the static lib) Link to an image → https://www.dropbox.com/scl/fi/7us5c21mdyoslg7zwnrzo/LimeLM-TurboActivate-DLL.PNG?rlkey=ec4mtra0nh4rpnwgloatp7tnr&st=7qn7ofu3&dl=0
  4. I have already double checked that the PC's Network adapters are enabled.  In my case the WIFI adapter is the one being used.
    Link to an image → https://www.dropbox.com/scl/fi/nek2k2ufe10x4t6e5aevx/Verified-PC-Network-Adapters-Enabled.PNG?rlkey=jzo6a5nwltxz66du5pedmyewe&st=43fw2ycz&dl=0
  5. To simplify things, I am running the test app provided by LimeLM for Turbo Activate to eliminate any chance of this issue being related to our app's code in any way.
    - When I run that (with our app GUID and the TurboActivate.dat file copied to its folder), it runs and immediately has the same - TA_E_ENABLE_NETWORK_ADAPTERS - error. 
    Link to an image → https://www.dropbox.com/scl/fi/bvjqqc2uq8wgs83n60zfn/LimeLM-Turbo-Activate-Example-app-Enable-Network-Adapters.PNG?rlkey=zv875afqzcjnjm20qmlh69ygs&st=b4cdwiai&dl=0
  6. I have also ran the TurboActivate.exe to check that also.  I get the same result.
    Link to an image → https://www.dropbox.com/scl/fi/robfivbibliwe74vv6qgd/LimeLM-TurboActivate-EXE-Enable-Network-Adapters.PNG?rlkey=7rhe3b9i7wugol545fd5h2u83&st=1fqltb29&dl=0
  7. The key does not seem to affect this in any way, I get the same error regardless of the key in use.  In fact, even when I run the TurboActivate.exe, I immediately get the error, so I can't deactivate to try another key anyway. 
Answer

Follow this including providing all the information from the last command: https://wyday.com/limelm/help/faq/#fix-broken-wmi

Yes!  This was the issue.  Thanks very much!  I had found this and tried it about 15 mins ago, sorry I didn't capture the output, but this fixed my issue.  I was about to post about it to update the thread and I saw that you had answered already.
Much Appreciated!

, edited