This is a report I initially made to Intel directly, as it was triggered by a NIC driver update pushed down Windows Update. Full details are at https://community.intel.com/t5/Ethernet-Products/Hyper-V-vSwitches-do-not-work-with-2-x-drivers-on-a...
Following a similar process to https://taeffner.net/2022/04/multiple-vlans-windows-10-11-onboard-tools-hyper-v/, I am using Hyper-V vNICs to configure VLAN support on Windows 11. This works with the 1.x branch of Intel NIC drivers, e.g. 1.0.2.8. This does not work with the updated 2.x branch, e.g. 2.1.3.15 as automatically installed by Windows Update, nor the most recent 2.1.3.3 distributed by Asus. When configured this way, the vNICs stop receiving packets on any 2.x drivers.
Intel has suggested that I contact Asus as they consider this an OEM issue:
> Since the issue definitely occurring after an update, contact your motherboard manufacturer / Asus for further assistance as the I225-V controller is embedded to the system.
> Just to add, you may consider reach out Asus to update the NVM file for the I225, because the log didn't display the version, such as "NVM Version:"Not Available"
System details:
NIC: (3) I225-V
Working driver version: 1.1.3.28, any other 1.x
Failing driver versions: 2.1.3.15 from Intel/WU, any other 2.x (e.g. 2.1.3.3 from Asus)
OS: Windows 11 22H2 Build 22621.2283
Motherboard: Asus Maximus Z690 Hero
BIOS: 2703 (latest)
Intel ME: 16.1.27.2176 (latest)
