Error 28 TA_E_ENABLE_NETWORK_ADAPTERSAnswered

Hi WyDay,

My customers have had this error many times and it never failed to solve by enabling all network devices on their machines. But I've now got a customer whom I've screenshared with to show me the enabled network devices and updated drivers, and the error persists.

They initially had a docking device connected via USB that provided a network slot, it seemed like a possible suspect so we disconnected this, leaving only a physical network connection along with wifi on the device, both enabled, and still no success.

Is there anything else we can try? This is on a Windows 11 machine.

Thanks

Answer

We've covered this quite a few times in our documentation and our forum. Here's a brief summary:

https://wyday.com/forum/t/18927/disabled-network-interfaces/#post-40043

Thanks Wyatt,

Yes I did see and read those.

- We are using the dynamic library version of TurboActivate, v4.4.4.1

- It isn't a Windows Beta version (OS build 22621.1265)

- All Windows updates are installed (Feb 2023)

- All driver updates are installed for the network devices

- Hyper-V is not installed

Interestingly enough, the “Killer(R) Wi-Fi 6E AX1690i 160MHz Wireless Network Adapter (411NGW)” from the thread you linked is exactly the same adapter as in this case, also reporting as not physical.

Is there anything else this user can try?

Go to Intel’s website and download the latest driver from there.

If the customer actually has the latest driver (and not just the ones Windows updates install — which are about 3 years out of date) then the next step is to uninstall that driver in the device manager, restart the machine, and have Windows reinstall it.

If none of that works, use the “Broken WMI” instructions to try to fix the driver: https://wyday.com/limelm/help/faq/#fix-broken-wmi

Long story short, this is a broken device that either Windows or Intel messed up. And it’s not the first time they’ve done something like this. We try to bend over backwards to fix broken machines, but there’s only so much we can do.

, edited

I reported the same last week (a surge of this issue with latest Windows 11) - this is a new problem with fresh new Windows 11 machines, got a new one today - none of the usual fixes appear to work. 

Edit: More hint, for this client, running limelm license check code disables Intel Internet Controller - I226V , the machine is a brand new Intel NUC with Windows 11 installed ….  He sent screenshot before and after, before it's enabled…

, edited
Answer

Well, the same FAQ applies. This is a configuration problem. For some reason Intel is very bad at writing driver installers. Hardware companies writing software has always been a problem in the industry.

So, follow the advice in the FAQ, and covered extensively in this forum. Step 1 is *always* use the latest TurboActivate and use the dynamic version of TurboActivate. Do that before doing anything else.

Then follow the FAQ and the post I linked to earlier.

TurboActivate can't work with broken hardware or broken drivers. The good news is that fixing their computers will also make their experience better in general.

Reply
Discard post