Filter virtual/filter network adapters by Name and Description in .NET 9/10

[Copilot]

Changes proposed in this pull request

• Filter network interfaces by checking both Name and Description properties against pattern list
• Add patterns for WAN Miniport and Microsoft Wi-Fi Direct Virtual Adapter to filter list

Related issue(s)

• NetworkInterfaces - .net10 shows strange adapters. #3286

Copilot generated summary

Copilot summary

.NET 9/10 changed NetworkInterface.GetAllNetworkInterfaces() to expose virtual/filter adapters. These appear in two forms:

1. Suffixed in Name: "vEthernet (Default Switch)-WFP Native MAC Layer LightWeight Filter-0000"
2. In Description field: Name="LAN-Verbindung* 1", Description="WAN Miniport (SSTP)"

Previous implementation only checked Name, missing adapters where patterns appear in Description.

Fix: Check both properties

// Before: only Name
if (NetworkInterfaceFilteredPatterns.Any(pattern => networkInterface.Name.Contains(pattern)))
    continue;

// After: Name OR Description  
if (NetworkInterfaceFilteredPatterns.Any(pattern => 
    networkInterface.Name.Contains(pattern) || 
    networkInterface.Description.Contains(pattern)))
    continue;

Filter patterns (applied to both fields):

• Hyper-V Virtual Switch Extension Filter
• Hyper-V Virtual Switch Extension Adapter
• WFP Native/802.3 MAC Layer LightWeight Filter
• Npcap Packet Driver (NPCAP)
• QoS Packet Scheduler
• Ethernet (Kerneldebugger)
• Filter Driver
• WAN Miniport
• Microsoft Wi-Fi Direct Virtual Adapter

Impact: Filters all virtual/filter adapters regardless of whether pattern appears in Name or Description. Preserves legitimate interfaces (Ethernet, WLAN, Bluetooth).

Ref: dotnet/runtime#122751

To-Do

• Update documentation to reflect this changes
• Update changelog to reflect this changes

Contributing

By submitting this pull request, I confirm the following:

• I have read and understood the contributing guidelines and the code of conduct.
• I have have added my name, username or email to the contributors list or don't want to.
• The code or resource is compatible with the GNU General Public License v3.0.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>NetworkInterfaces - .net10 shows strange adapters.</issue_title>
<issue_description>Since .net 9 / 10 the network interfaces shows a lot of adapters:

Possible workaround?

• Blacklist of adapter names?

Reported to dotnet/runtime dotnet/runtime#122751</issue_description>

<agent_instructions>Try to figure out if there is an elegant way filter out this new behaviour microsoft has introduced in .net9/10 to show more network interfaces. If not possible, implement a blacklist. Search in the dotnet issue that is linked what has changed.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[BornToBeRoot]

@copilot what is with the WAN Miniport / Microsoft Wi-Fi Direct Virtual Adapter , i see this in the description of some "LAN Connections"

[Copilot]

@copilot what is with the WAN Miniport / Microsoft Wi-Fi Direct Virtual Adapter , i see this in the description of some "LAN Connections"

Added "WAN Miniport" and "Microsoft Wi-Fi Direct Virtual Adapter" to the filter list in commit ac3ac82. These virtual adapters (used for VPN/PPP connections and Wi-Fi Direct peer-to-peer) will now be filtered out along with the other virtual/filter adapters. Testing confirms all WAN Miniport variants (SSTP, IKEv2, L2TP, PPTP, IP, IPv6) and Wi-Fi Direct adapters are now filtered while legitimate network interfaces remain visible.