Skip to content

FAQ

Activation – ENABLE_NETWORK_ADAPTERS

Error Message: TA_E_ENABLE_NETWORK_ADAPTERS – FOR WINDOWS OS

This error indicates a problem with your network card that is affecting our activation system. We use a licensing system provided by Wyday.com and it requires network adapters to be functional and use such info in their hardware signature. This also why if you replace your motherboard, the license has to be released and reactivated.

Follow these steps to resolve the issue:

1. Ensure that any files downloaded from our website are unblocked. To do this Right-click the file, select ‘Properties,’ and check the ‘Unblock’ box if it is available.

2.Type ‘NCPA.cpl’ in the Windows search box.

Enable the adapters at least once to ensure the licensing program runs smoothly. If you don’t have Intel i225-226 ethernet adapters, this usually works. Also for each ethernet adapter, press Properties and Select Configure and update drivers.

3.Still an issue? Open PowerShell as an administrator. To do this, search for PowerShell, right-click it, and choose ‘Run as administrator.’

4.Copy and send us the following information after running the two commands below. The new method described in paragraph 5 might fix it better:

Get-NetAdapter -Name “*” -Physical

Enable all network adapters:

Get-NetAdapter | ? status -ne up | Enable-NetAdapter 

Perform the following steps in PowerShell (as administrator):

cd C:\Windows\System32\wbem

mofcomp C:\Windows\System32\wbem\NetAdapterCim.mof

mofcomp C:\Windows\System32\wbem\en-US\NetAdapterCim.mfl

 

5.Check ‘Device Drivers’ in ‘Computer Management.’ Download the drivers for your network adapters from the manufacturer’s website.

if you’re on a new machine and any of the network adapters are Intel try this: https://www.intel.com/content/www/us/en/support/intel-driver-support-assistant.html

It seems that Intel/Microsoft made some missteps either with drivers or firmware. Recently Intel created a firmware/driver upgrade portal. Running this assistant will most likely fix this issue.

If the issue persists, we might need to schedule a screenshare meeting to review the process together.