TA_E_ENABLE_NETWORK_ADAPTERSAnswered

My application uses TA v4.4.4.1. It does not use the static version.

I have a user on a brand new Windows 11 machine who gets the TA_E_ENABLE_NETWORK_ADAPTERS error when trying to activate. The machine is on the latest version of Windows 24H2. All drivers have not been updated.

Still the same error when trying to activate.

What can I do to help this customer? Is there a command that you can give me that would extract information to help debug this issue?



 

Answer

Use the latest version of TurboActivate and update the drivers.

New Unknown Errors here - after 6 months of quiet with latest lib, suddenly 3 in last 2 weeks with errors -  got one to return adapter error:

__GENUS             : 2
__CLASS             : MSFT_NetAdapter
__SUPERCLASS        :
__DYNASTY           :
__RELPATH           :
__PROPERTY_COUNT    : 6
__DERIVATION        : {}
__SERVER            :
__NAMESPACE         :
__PATH              :
DeviceID            : {E7EB0C28-D13E-4994-8EE3-78C776815446}
DriverDescription   : ASIX USB to Gigabit Ethernet Family Adapter
DriverVersionString : 3.22.3.0
PermanentAddress    :
PnPDeviceID         : USB\VID_0B95&PID_1790\c&8a2e01b&0&4
WdmInterface        : False
PSComputerName      :

__GENUS             : 2
__CLASS             : MSFT_NetAdapter
__SUPERCLASS        :
__DYNASTY           :
__RELPATH           :
__PROPERTY_COUNT    : 6
__DERIVATION        : {}
__SERVER            :
__NAMESPACE         :
__PATH              :
DeviceID            : {14A1D449-73B0-4CDC-A9BC-8C654D1520B1}
DriverDescription   : Killer Wi-Fi 6 AX500-DBS Wireless Network Adapter
DriverVersionString : 1.0.0.1769
PermanentAddress    : 9CB6D03E4226
PnPDeviceID         : PCI\VEN_17CB&DEV_1101&SUBSYS_A5011A56&REV_00\4&3479c7b5&0&00E1
WdmInterface        : False
PSComputerName      :

Unfortunately it looks like that no-name brand Ethernet adapter (Asix) is malfunctioning. It's not reporting a permanent address. Contact them to fix it, or buy from a more reputable brand.

Another hint today, a company with a large computer network updated ONE machine to Windows11 24H2 update (from 23H2) -  and that machine alone which was working fine before is now experimenting the network adapter disconnecting issue.  The guy has to drive at around midnight 40 min each way today to try to fix it - I asked him to report driver version, adapter and try a rollback of driver… check on other same machine not updated what the driver version is…

As always the solution is to use latest TA (currently 5.0.2), update the OS (which they've done), remove all VPNs (“privacy” VPNs are run by nation-states and criminal organizations – they're not private and they're not useful – they're user-installed malware), and update all drivers.

Occasionally a customer will use some genuine garbage network adapter that's failing – in which case the solution is to not to buy the cheapest adapter they find on Temu / Amazon / Alibaba. That stuff is garbage and is more shocking if it works for more than 10 minutes in its life.

For example, ASIX is not a reputable brand (currently). They might be in 20 years, but right now they produce cheap garbage. Which, again, is perfectly OK if you don't need reliability.

, edited


Here's a new one (we send 5.0.2 to new clients but only getting updated from 5.0 in new installers)
 

This machine not working is on driver 2.1.4.3  (and Win11 24H2)
A working machine (identical hardware) is on driver 1.1.4.43  (and Win11 23H2) and working

"Wasn't able to rollback easily with the dumb Windows rollback button and having a bit of a time finding the older drivers"

Also - Network Adapter UI reports:  Intel driver version  23.90.02 - driver date 9/6/2024
Intel WIFI 7 BE200 3200MHz #3

Powershell:
__GENUS             : 2
__CLASS             : MSFT_NetAdapter
__SUPERCLASS        :
__DYNASTY           :
__RELPATH           :
__PROPERTY_COUNT    : 6
__DERIVATION        : {}
__SERVER            :
__NAMESPACE         :
__PATH              :
DeviceID            : {EE2EC455-D0F6-4279-8C1C-D1B1F49E3B06}
DriverDescription   : Intel(R) Ethernet Controller (3) I225-V
DriverVersionString : 2.1.4.3
PermanentAddress    : D843AE3EB608
PnPDeviceID         : PCI\VEN_8086&DEV_15F3&SUBSYS_7E071462&REV_03\D843AEFFFF285B7E00
WdmInterface        : True
PSComputerName      :

For what the customer is describing it sounds like their machine is in a bad state. Soo… either do a clean install or fix the machine.

If the UI is showing adapters not being shown in commandline then things are broken. We can (and do) fix a lot of problems caused both by users and bad driver-programmers, but it's the customers responsibility to have a machine not in a broken state.

, edited

Maybe he did not send the whole thing - if I ask him to go in Device Manager and Uninstall Device for the WIFI one -  will WYday then ignore that - he is not using the WIFI one, 

He now sent full ouptut





__GENUS             : 2
__CLASS             : MSFT_NetAdapter
__SUPERCLASS        :
__DYNASTY           :
__RELPATH           :
__PROPERTY_COUNT    : 6
__DERIVATION        : {}
__SERVER            :
__NAMESPACE         :
__PATH              :
DeviceID            : {F1D56360-FB2E-4CEF-82EC-C49A3BCE9162}
DriverDescription   : Qualcomm FastConnect 7800 Wi-Fi 7 High Band Simultaneous (HBS) Network Adapter
DriverVersionString : 3.1.0.1262
PermanentAddress    :
PnPDeviceID         : PCI\VEN_17CB&DEV_1107&SUBSYS_E0F7105B&REV_01\4&2bb179bf&0&00E2
WdmInterface        : False
PSComputerName      :

__GENUS             : 2
__CLASS             : MSFT_NetAdapter
__SUPERCLASS        :
__DYNASTY           :
__RELPATH           :
__PROPERTY_COUNT    : 6
__DERIVATION        : {}
__SERVER            :
__NAMESPACE         :
__PATH              :
DeviceID            : {EE2EC455-D0F6-4279-8C1C-D1B1F49E3B06}
DriverDescription   : Intel(R) Ethernet Controller (3) I225-V
DriverVersionString : 2.1.4.3
PermanentAddress    : D843AE3EB608
PnPDeviceID         : PCI\VEN_8086&DEV_15F3&SUBSYS_7E071462&REV_03\D843AEFFFF285B7E00
WdmInterface        : True
PSComputerName      :

__GENUS             : 2
__CLASS             : MSFT_NetAdapter
__SUPERCLASS        :
__DYNASTY           :
__RELPATH           :
__PROPERTY_COUNT    : 6
__DERIVATION        : {}
__SERVER            :
__NAMESPACE         :
__PATH              :
DeviceID            : {CFF8F045-3263-43F4-B7B9-17FDB4B12A5F}
DriverDescription   : Qualcomm FastConnect 7800 Wi-Fi 7 High Band Simultaneous (HBS) Network Adapter
DriverVersionString : 3.1.0.1262
PermanentAddress    : 4C82A904E10B
PnPDeviceID         : PCI\VEN_17CB&DEV_1107&SUBSYS_E0F7105B&REV_01\4&2bb179bf&0&00E2
WdmInterface        : True
PSComputerName      :

__GENUS             : 2
__CLASS             : MSFT_NetAdapter
__SUPERCLASS        :
__DYNASTY           :
__RELPATH           :
__PROPERTY_COUNT    : 6
__DERIVATION        : {}
__SERVER            :
__NAMESPACE         :
__PATH              :
DeviceID            : {8BA2E32E-8233-4444-813F-2821EAE9671D}
DriverDescription   : Qualcomm FastConnect 7800 Wi-Fi 7 High Band Simultaneous (HBS) Network Adapter
DriverVersionString : 3.1.0.1262
PermanentAddress    : 8E82A904E10B
PnPDeviceID         : PCI\VEN_17CB&DEV_1107&SUBSYS_E0F7105B&REV_01\4&2bb179bf&0&00E2
WdmInterface        : True
PSComputerName      :

__GENUS             : 2
__CLASS             : MSFT_NetAdapter
__SUPERCLASS        :
__DYNASTY           :
__RELPATH           :
__PROPERTY_COUNT    : 6
__DERIVATION        : {}
__SERVER            :
__NAMESPACE         :
__PATH              :
DeviceID            : {3FD1E8CC-D3DA-4371-9695-EB05954F7186}
DriverDescription   : Qualcomm FastConnect 7800 Wi-Fi 7 High Band Simultaneous (HBS) Network Adapter
DriverVersionString : 3.1.0.1262
PermanentAddress    : 7E82A904E10B
PnPDeviceID         : PCI\VEN_17CB&DEV_1107&SUBSYS_E0F7105B&REV_01\4&2bb179bf&0&00E2
WdmInterface        : True
PSComputerName      :

__GENUS             : 2
__CLASS             : MSFT_NetAdapter
__SUPERCLASS        :
__DYNASTY           :
__RELPATH           :
__PROPERTY_COUNT    : 6
__DERIVATION        : {}
__SERVER            :
__NAMESPACE         :
__PATH              :
DeviceID            : {1CB19711-EA29-4285-8B41-4E8736F961A0}
DriverDescription   : Qualcomm FastConnect 7800 Wi-Fi 7 High Band Simultaneous (HBS) Network Adapter
DriverVersionString : 3.1.0.1262
PermanentAddress    : 6E82A904E10B
PnPDeviceID         : PCI\VEN_17CB&DEV_1107&SUBSYS_E0F7105B&REV_01\4&2bb179bf&0&00E2
WdmInterface        : True
PSComputerName      :

The latest version of TurboActivate (5.0.2) can handle that fine. Are they actually using the latest version? You said something like you're having them do it manually. Don't do that. Include it in your installer. Customers mess things up.

OK will send him 5.0.2 activator - he said uninstalling the unused device worked but upon reboot it's back?

I don't know what the unusued device is or means. Is it reflected in the log you posted? If so, then that's a bug in Qualcomm's drivers. If not, then you need to give me enough information to actually help you.

Likely a broken Microsoft example driver that MS delivers as part of it's WDK, because Intel makes a similar mistake in some of their “multi-device / single-chip” network drivers. But that's beside the point. In 5.0.2 we work around all current known broken drivers.

, edited

He had a WIFI adapter causing issue, what worked was to physically disconnect the adapter as uninstall caused a reinstall by OS at next reboot. A test installer with 5.0.2 worked. Working on rebuilding all linking to 5.0.2 - hundreds of SKUs here… more and more people suddenly having the issue.

Reply
Discard post