A solution for Intel ProSet Adapter Configuration Utility no longer supported in Windows 11 for managing VLANs

So I finally bit the bullet yesterday and upgraded one of my Windows 10 machine to Windows 11. I figured a lot of Win11 bugs have been ironed out by now, so I decided to get on with it before Win10 support expires in 2025.

I am pretty impressed with the overall upgrade process; all my software and documents were left intact... except for one very big issue. My Hyper-V VMs were no longer working due to the VLAN configuration being hosed.

As it turns out, Intel pulled support for the ProSet utility for Windows 11, which is what I used to configure multiple VLANs on my NIC. So, the solution is to now use Windows PowerShell commands to manually establish VLAN interfaces you need, via the Hyper-V stack. Go ahead and install the Hyper-V host components.

What you are essentially doing is to create a Hyper-V VLAN switch and attach multiple VLAN adapters to it. In the example below, we'll name your VLAN switch "VLAN-vSwitch" and I will assume your NIC is named "Ethernet" (usually by default, or find it out with "Get-NetAdapter" command). And we'll create three VLANs with ID 101, 102, and 103.

In a Windows PowerShell running as Administrator, do the following:

New-VMSwitch -name VLAN-vSwitch -NetAdapterName Ethernet -AllowManagementOS $true

Remove-VMNetworkAdapter -ManagementOS -Name VLAN-vSwitch

Add-VMNetworkAdapter -ManagementOS -Name "VLAN101" -SwitchName "VLAN-vSwitch" -Passthru | Set-VMNetworkAdapterVlan -Access -VlanId 101

Add-VMNetworkAdapter -ManagementOS -Name "VLAN102" -SwitchName "VLAN-vSwitch" -Passthru | Set-VMNetworkAdapterVlan -Access -VlanId 102

Add-VMNetworkAdapter -ManagementOS -Name "VLAN103" -SwitchName "VLAN-vSwitch" -Passthru | Set-VMNetworkAdapterVlan -Access -VlanId 103

Running the Get-NetAdapter command again will now show you the VLAN adapters you created. Let me know if you have any questions!