iANS VLANs seems to break Powershell "NetAdapter" commands, with "The data is invalid".

[bilalu]

I've a I210-T1 following a bit of a saga of finding an adapter for Windows 10 that can do VLANS....

I find that I can't manage any Windows network adapter using PowerShell's NetAdapter commands while there are any VLANs defined with this adapter.

Bit of a blow. Especially when certain changes in Windows (I think there was an update or a network reconfig courtesy of Hyper-V) cause all the VLAN interfaces to drop (and then you can't add them back with the same name because they're still floating around somewhere - full network reset fixes it - painful). Does this problem needs it's own "Ask"?

Mildly redacted example below.

PS C:\WINDOWS\system32> Get-NetAdapter   Name InterfaceDescription ifIndex Status MacAddress LinkSpeed ---- -------------------- ------- ------ ---------- --------- bluetooth Bluetooth Device (Personal Area Netw... 38 Disconnected XX-YY-ZZ-AA-BB-CC 3 Mbps ethernet-main Killer E2400 Gigabit Ethernet Contro... 39 Up XX-YY-ZZ-AA-BB-CC 1 Gbps ethernet-intel-parent Intel(R) Ethernet Server Adapter I21... 40 Disconnected XX-YY-ZZ-AA-BB-CC 0 bps wifi Qualcomm QCA9377 802.11ac Wireless A... 5 Disconnected XX-YY-ZZ-AA-BB-CC 0 bps       PS C:\WINDOWS\system32> Add-IntelNetVLAN -VLANID 17 -ParentName "Intel(R) Ethernet Server Adapter I210-T1"   VLANID VLANName ParentName ------ -------- ---------- 17 VLAN17 Intel(R) Ethernet Server Adapter I210-T1       PS C:\WINDOWS\system32> Get-NetAdapter Get-NetAdapter : The data is invalid. At line:1 char:1 + Get-NetAdapter + ~~~~~~~~~~~~~~ + CategoryInfo : InvalidData: (MSFT_NetAdapter:ROOT/StandardCimv2/MSFT_NetAdapter) [Get-NetAdapter], CimException + FullyQualifiedErrorId : Windows System Error 13,Get-NetAdapter   PS C:\WINDOWS\system32> Get-IntelNetVLAN | Remove-IntelNetVLAN   PS C:\WINDOWS\system32> Get-NetAdapter   Name InterfaceDescription ifIndex Status MacAddress LinkSpeed ---- -------------------- ------- ------ ---------- --------- bluetooth Bluetooth Device (Personal Area Netw... 38 Disconnected XX-YY-ZZ-AA-BB-CC 3 Mbps ethernet-main Killer E2400 Gigabit Ethernet Contro... 39 Up XX-YY-ZZ-AA-BB-CC 1 Gbps ethernet-intel-parent Intel(R) Ethernet Server Adapter I21... 40 Disconnected XX-YY-ZZ-AA-BB-CC 0 bps wifi Qualcomm QCA9377 802.11ac Wireless A... 5 Disconnected XX-YY-ZZ-AA-BB-CC 0 bps       PS C:\WINDOWS\system32>

Even commands that directly target unrelated network adapters fail:

PS C:\WINDOWS\system32> Get-NetAdapterBinding -Name ethernet-main   Name DisplayName ComponentID Enabled ---- ----------- ----------- ------- ethernet-main Microsoft Network Adapter Multiplexor Protocol ms_implat False ethernet-main QoS Packet Scheduler ms_pacer True ethernet-main Internet Protocol Version 4 (TCP/IPv4) ms_tcpip True ethernet-main Client for Microsoft Networks ms_msclient True ethernet-main Intel(R) Advanced Network Services Protocol iANSProtocol False ethernet-main Microsoft LLDP Protocol Driver ms_lldp True ethernet-main Hyper-V Extensible Virtual Switch vms_pp False ethernet-main Link-Layer Topology Discovery Mapper I/O Driver ms_lltdio True ethernet-main File and Printer Sharing for Microsoft Networks ms_server True ethernet-main Internet Protocol Version 6 (TCP/IPv6) ms_tcpip6 True ethernet-main Win10Pcap Packet Capture Driver Win10Pcap True ethernet-main Link-Layer Topology Discovery Responder ms_rspndr True ethernet-main Npcap Packet Driver (NPCAP) INSECURE_NPCAP True ethernet-main Npcap Packet Driver (NPCAP) (Wi-Fi) INSECURE_NPCAP_WIFI True ethernet-main VirtualBox NDIS6 Bridged Networking Driver oracle_VBoxNetLwf True ethernet-main Bridge Driver ms_l2bridge True       PS C:\WINDOWS\system32> Add-IntelNetVLAN -VLANID 17 -ParentName "Intel(R) Ethernet Server Adapter I210-T1"   VLANID VLANName ParentName ------ -------- ---------- 17 VLAN17 Intel(R) Ethernet Server Adapter I210-T1       PS C:\WINDOWS\system32> Get-NetAdapterBinding -Name ethernet-main Get-NetAdapterBinding : The data is invalid. At line:1 char:1 + Get-NetAdapterBinding -Name ethernet-main + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidData: (MSFT_NetAdapterBindingSettingData:ROOT/StandardCi...dingSettingData) [Get-NetAdapterBinding], CimException + FullyQualifiedErrorId : Windows System Error 13,Get-NetAdapterBinding   PS C:\WINDOWS\system32> Get-IntelNetVLAN | Remove-IntelNetVLAN   PS C:\WINDOWS\system32> Get-NetAdapterBinding -Name ethernet-main   Name DisplayName ComponentID Enabled ---- ----------- ----------- ------- ethernet-main Microsoft Network Adapter Multiplexor Protocol ms_implat False ethernet-main QoS Packet Scheduler ms_pacer True ethernet-main Internet Protocol Version 4 (TCP/IPv4) ms_tcpip True ethernet-main Client for Microsoft Networks ms_msclient True ethernet-main Intel(R) Advanced Network Services Protocol iANSProtocol False ethernet-main Microsoft LLDP Protocol Driver ms_lldp True ethernet-main Hyper-V Extensible Virtual Switch vms_pp False ethernet-main Link-Layer Topology Discovery Mapper I/O Driver ms_lltdio True ethernet-main File and Printer Sharing for Microsoft Networks ms_server True ethernet-main Internet Protocol Version 6 (TCP/IPv6) ms_tcpip6 True ethernet-main Win10Pcap Packet Capture Driver Win10Pcap True ethernet-main Link-Layer Topology Discovery Responder ms_rspndr True ethernet-main Npcap Packet Driver (NPCAP) INSECURE_NPCAP True ethernet-main Npcap Packet Driver (NPCAP) (Wi-Fi) INSECURE_NPCAP_WIFI True ethernet-main VirtualBox NDIS6 Bridged Networking Driver oracle_VBoxNetLwf True ethernet-main Bridge Driver ms_l2bridge True       PS C:\WINDOWS\system32>

[Caguicla_Intel]

Hello Bilal,

Thank you for the prompt reply.

Please allow us to further investigate on this issue. Rest assured that we will get back to you within 1-3 business days.

Best regards,

Crisselle C

Intel Customer Support

A Contingent Worker at Intel

[Caguicla_Intel]

Hello Bilal,

Thank you for the patience on this matter.

We've tried to install SW version 24.5 in our lab system with fresh install Windows 10 build 1909, the system has I210-T1 and I219-V, we haven't encountered any issue with the driver installation.

With this, we would like to ask if you have you tried performing Clean Driver Installation? If not yet, sharing the steps below on how perform a clean driver installation for any Intel® Ethernet Controller/Adapter

1. Open Windows* Device Manager:  

Windows® 10:Right-click Start > Device Manager

2. Double-click Network adapters to expand the section.

3. Right-click the Intel® Ethernet Connection (model) and select Properties.

4. Click the Driver tab.

5. Click Uninstall.

6. Check "Delete the driver software for this device" and click OK.

7. Press the Windows key + R, then type "%Temp%" (without the quotation marks) delete everything from that folder, then install our latest driver from the Download Center.

https://downloadcenter.intel.com/download/22283/Intel-Ethernet-Adapter-Complete-Driver-Pack

We look forward to hear an update from you.

Best regards,

Crisselle C

Intel Customer Support

A Contingent Worker at Intel

[bilalu]

Hi Chriselle,

Appreciate the guidance. I'll follow what you suggested and if that doesn't work, reinstall Windows 10 from scratch, and report my findings.

Regards,

Bilal

[Caguicla_Intel]

Hello Bilal,

Thank you for the reply.

We will be waiting for your update after trying out the steps above. Hopefully, that would resolve the issue to avoid reinstalling OS which would take some time and effort.

Looking forward to hear from you.

Best regards,

Crisselle C

Intel Customer Support

A Contingent Worker at Intel

[Caguicla_Intel]

Hello Bilal,

Please let us know if you were able try out the recommended steps above. We'd also like to share with you that we have received multiple report regarding this issue and we are currently investigating on this.

Sharing the thread below for your reference:

https://forums.intel.com/s/question/0D50P00004ZOeho/v245-drivers-for-intel-i211-on-windows-10-64bit-not-working?language=en_US

We look forward to your response.

Best regards,

Crisselle C

Intel Customer Support

A Contingent Worker at Intel

[Caguicla_Intel]

Hello Bilal,

We sincerely apologize for all the inconvenience we might have caused on this matter.

After further checking with our engineers, we regret to inform you that this is a known issue and the fix will be available in the SW release 25.0. In the mean time, the temporary workaround is by disabling secure boot and disabling device driver signing. 

Thank you for the patience and kind understanding.

Best regards,

Crisselle C

Intel® Customer Support

A Contingent Worker at Intel

[bilalu]

Hi Chriselle,

Thanks - you saved me a week of further lost productivity setting up my Windows environment from scratch. Couldn't bring myself to do it so far.

Bilal

[Caguicla_Intel]

Hello Bilal,

Good day!

Please be informed that SW 25.0 to fix the E1R driver certificate issue was now available for download. Sharing the download link with you below and feel free to update us after trying it out.

https://downloadcenter.intel.com/download/22283/Intel-Ethernet-Adapter-Complete-Driver-Pack

We look forward to your response.

Best regards,

Crisselle C

Intel® Customer Support

A Contingent Worker at Intel

[bilalu]

Hi Chriselle,

I didn't give it much attention, but it seems that the signing issue is still present in 25.0.

Bilal

[Caguicla_Intel]

Hello Bilal,

We sincerely apologize for the delay on our response.

The issue with the certificate for the E1R driver should be fixed in SW 25.0 release. Can you share if it is the same exact error message you got when updating the driver to latest version?

Looking forward to hear from you.

Should there be no response form you, we'll follow up after 3 business days.

Best regards,

Crisselle C

Intel® Customer Support

[bilalu]

Hi Chrisselle,

I did install v25. Code 39, like before. Driver version 12.18.9.6 from Nov 19.

Regards,

Bilal

[Caguicla_Intel]

Hello Bilal,

Thanks for the prompt reply.

We will further investigate the issue with our engineers. Rest assured that we will send an update within 2-3 business days.

Hoping for your kind patience.

Best regards,

Crisselle C

Intel® Customer Support

[Caguicla_Intel]

Hello Bilal,

Appreciate your patience on this matter.

Please be advised that the issue in VLAN breaking Get-NetAdapter is not yet fixed in SW 25 and this will be addressed on future release.

In regards to 'Code 39' error you encountered, we have checked that this was addressed in driver release SW 25. You may visit the forum link below wherein your fellow users stated that this issue has been fixed.

https://forums.intel.com/s/question/0D50P00004ZOehoSAD/v245-drivers-for-intel-i211-on-windows-10-64bit-not-working

However, we understand that you have tried the SW 25 already. With this, we'd like to check if you have tried to reinstall the driver to check if it will help in fixing the issue?

We look forward to your reply.

In case we don't hear from you, we'll follow up after 3 business days.

Best regards,

Crisselle C

Intel® Customer Support

[Caguicla_Intel]

Hello Bilal,

We'd like to check if you have received our previous message? In case you need more time to provide the requested information, please do not hesitate to let us know.

Awaiting to your reply.

In case we don't hear from you, we'll follow up after 3 business days.

Best regards,

Crisselle C

Intel® Customer Support

[bilalu]

Hi Chriselle,

Wow... it worked.

I'd put in the original manufacturer hard drive with a not-so-altered image. It worked there, so I thought I have to reinstall Windows on my main hard drive.

After putting back the main hard drive, thought I'd try one more time, and IT WORKED! ARGH! Why? I don't know if opening my box and discharging the power had any effect.

Excellent! The Get-NetAdapter, etc commands work as well, with VLANS added and all.

Let's hope this issue doesn't regress, but at least for now, we can sleep easier!

Thanks to the team for fixing this issue. Ideally, it shouldn't've been there in the first place, but we've arrived.

Regards,

Bilal

[Caguicla_Intel]

Hello Bilal,

Thank you for the update.

We are glad to hear that the issue has now been resolved and the Get-NetAdapter is working fine as well.

Please be informed that we will now proceed in closing this request. Thank you very much for your time and cooperation throughout the process. Should you have any other concerns or assistance needed in the future, feel free to post a new question and we will be glad to be of help.

Have a wonderful day ahead!

Best regards,

Crisselle C

Intel® Customer Support

[bilalu]

Hi Chriselle,

Thank you also for your support and continued follow-up throughout the process.

Regards,

Bilal