23.5 Vlans break Windows Powershell Get-NetAdapter

[CHead1]

Hello. Windows 1809.

1. Get-NetAdapter works fine.
2. Install Intel 23.5, Get-NetAdapter still works fine.
3. Create a VLAN, Get-Netadapter fails. (error below)
4. I believe (but can't remember) after removing VLANs get-netadapter works again.
5. Restored to system point and rechecked. Reproducible.
6. sfc /scannow shows no issues. the wbem repository check says it is consistent.

Error:

PS C:\Users\dingo> 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

Powershell Cmds to create vlan:

Import-Module -Name "C:\Program Files\Intel\Wired Networking\IntelNetCmdlets\IntelNetCmdlets"

$IntelNic=Get-IntelNetAdapter -Name "Intel(R) Ethernet Connection (2) I218-V"

$networkVLANs=(

  @{"VLAN"="64"; "Name"="VLAN 64"},

  @{"VLAN"="120";"Name"="VLAN 120"},

  @{"VLAN"="241";"Name"="VLAN 241"},

  @{"VLAN"="255";"Name"="VLAN 255"}

)

foreach($network in $networkVLANs)

{

  Add-IntelNetVLAN -Parent $intelnic -VLANID $network["VLAN"]

  Set-IntelNetVLAN -Parent $intelnic -VLANID $network["VLAN"] -NewVLANName "$($network["VLAN"]) - $($network["Name"])"

}

[VincentT_Intel]

CHead1, Thank you for posting in Intel® Ethernet Community. Let me check this internally and update the thread as soon as possible. Best Regards, Vince Intel Customer Support

[rjt]

Had reported the same problem over the summer in attempting to create vLans. But now that the forums have moved, i have not found the posting.

[VincentT_Intel]

Hi CHead1, To help us investigate the issue, please provide your System Support Utility log. Kindly refer to the download link and steps below: 1- Download from https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows- 2- Open SSU.exe 3- Mark the box "Everything" and then click "Scan". 4- When finished scanning, click "Next". 5- Click on "Save" and attach the file to a post. Looking forward to your response. Best Regards, Vince T. Intel Customer Support

[CHead1]

attached.

[VincentT_Intel]

Hi CHead1, Thank you for providing the log file. We'll look into this and update the thread as soon as possible. Best Regards, Vince T. Intel Customer Support

[VincentT_Intel]

Hi CHead1, We've replicated the issue and the fix will be incorporated in the future SW release. However, there's currently no ETA on when it will be available. Please let us know there's other assistance needed. Best Regards, Vince T. Intel Customer Support

[TM-AN]

@VinceT_Intel​  So, 23.5.2 is out, but the issue remains?

Best Regards,

Tobias

[VincentT_Intel]

Hi @TM-AN​ 

Thank you for posting in Intel® Ethernet Community.

Yes, the issue remains.

Best Regards,

Vince T.

Intel Customer Support

Under Contract to Intel Corporation

[EBoca1]

Issue reproducible here as well on 23.5.2. As a side effect Docker also no longer starts after adding Intel VLANs (presumably due to failing Powershell network commands above).

[VincentT_Intel]

Hi CHead1, TM-AN, EBoca1, The Team and VLAN configuration issues are expected to be resolved in the next SW Release available in early Q2 (April/May). The Intel Ethernet Team appreciates your patience while we work to fix the issues you are experiencing with the current version of Microsoft* Windows* 10 and also prevent similar issues from reoccurring in future Windows 10 updates. In our investigation of these issues, we were able to find a better workaround for you to use while waiting for the next SW Release. Workaround: Intel® Advanced Network Services (Intel® ANS) fails or hangs after operating system upgrade ---------------------------------------------------------------------------------------------------------- If you upgrade your operating system from Microsoft* Windows* 10 RS4 to Microsoft Windows 10 RS5, or from Microsoft Windows 10 RS5 to Microsoft Windows 10 19H1, trying to create an Intel® ANS team or VLAN may fail or cause Microsoft PowerShell* to hang. The following steps will resolve the issue: 1) If Microsoft PowerShell hangs, reboot your system. 2) Uninstall Intel® PROSet and all of its subcomponents 3) Open the Windows Network and Sharing Center. 4) On the left sidebar, click "Change adapter settings." 5) Double click an Intel Ethernet adapter to open its properties. 6) In the section below the "This connection uses the following items" caption, highlight Intel® Advanced Network Services Protocol and click Uninstall. 7) Run the Intel® PROSet installer and follow the instructions in the install wizard. All Intel ANS features should now work as expected. If you are still experiencing the PowerShell hang issue when creating a Team or other ANS issues, please contact Intel Customer Support - https://www.intel.com/content/www/us/en/support/contact-support.html ---------------------------------------------------------------------------------------------------------- Note: The Intel Ethernet Team is responsible for validating and submitting new driver packages to Microsoft for inclusion on Windows Update. Microsoft does not support Team and VLAN configuration on Window 10. Team and VLAN configuration for Intel Ethernet Adapters on Windows 10 is supported via our Intel® PROSet software. Intel® PROSet is not included on Microsoft Windows Update. Thanks you for being a valued customer. Best Regards, Vince T. Intel Customer Support Under Contract to Intel Corporation

[EBoca1]

Hi Vince,

Solution above does not fix the problem. Get-NetAdapter still throws after creating an Intel VLAN (and I am on Windows 10 1803).

Thanks,

Eric

[YXiao16]

The issue "23.5 Vlans break Windows Powershell Get-NetAdapter" is not fixed in "Intel® Ethernet Adapter Complete Driver Pack" Version: 24.0 (Latest) Date: 6/5/2019

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

Get-NetAdapter works fine.

Create a VLAN, Get-Netadapter fails. (error below)

After removing VLANs get-netadapter works again.

Microsoft Windows

Version 1803 (OS Build 17134.590)

Windows PowerShell

Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\Users\test> 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:\Users\test>

[EBoca1]

Yes. 24.0 has the same issue as 23.5 for me as well, and it is still broken as Xiao mentiones. @VinceT_Intel​ do you know anything about this?

[bilalu]

Vince,

Is it possible to continue to use VLANs and not have the NetAdapter powershell commands fail after the workaround you suggested?

24.1 doesn't seem to have the issue taken care of. Any idea what next version we're expecting and when, that would incorporate the fix?

Thanks

[CUllr]

This issue still exists in release 24.1 on Windows 10 (1903, x64). While any VLANs exist, Get-NetAdapter fails, and so does the lower-level operation:

Get-CimInstance -ClassName MSFT_NetAdapter -Namespace root\standardcimv2

[CHead1]

Hello.

Powershell Get-NetAdapter is still broken after updating to 24.1 on 1903. .... Has not been fixed as indicated.

[VincentT_Intel]

Hi,

We apologize for any inconvenience. The fix for this issue will be incorporated in the next SW release. Please stay tune for update.

Best Regards,

Vince T.

Intel Customer Support

A Contingent Worker at Intel

[CUllr]

It doesn't look like it. The error message may have changed, but the cmdlet is as broken as before:

[CUllr]

Still broken in 24.3. When is this going to be fixed?

[bilalu]

Have also come across this issue: https://forums.intel.com/s/question/0D70P000006SwQq/ians-vlans-seems-to-break-powershell-netadapter-commands-with-the-data-is-invalid

Q2 (April/May) has passed and gone.