 | 1 | initial version |
This is probably due to 1) the Windows 11 driver for your adapter using the Windows NetAdapterCx framework, 2) the NetAdapterCx framework not strictly following the Network Driver Interface Specification (NDIS) rules, and 3) the Npcap driver expecting all adapter drivers to strictly follow that specification and reporting an error if they don't.
This should be fixed in Npcap 1.74, which was released today (2023-04-20). (The Npcap driver no longer reports an error for that particular violation of the specification; the 1.60 driver also didn't check for that particular violation.)
