WSL2 causes host-wide Intel BE200 Wi-Fi failure in both NAT and mirrored modes, followed by shutdown hang and BSOD

Nobody has claimed this yet.

### Windows Version

Version: 10.0.26200

### WSL Version

2.7.11.0

### Are you using WSL 1 or WSL 2?

- [x] WSL 2
- [ ] WSL 1

### Kernel Version

6.18.33.2-2

### Distro Version

Ubuntu 22.04

### Other Software

Hardware: HP OMEN MAX Gaming Laptop 16-ah0xxx
BIOS: F.22 (2026-04-29)

Wireless adapter:
Intel(R) Wi-Fi 7 BE200 320MHz

Hardware ID:
PCI\VEN_8086&DEV_272B&SUBSYS_00F48086&REV_1A

Intel Wi-Fi driver:
24.70.0.3 (2026-07-29), NDIS 6.89

An enabled third-party NDIS binding is present on the Intel WLAN adapter:
Realtek LightWeight Filter (NDIS6.40)
Component ID: nt_rtf64

### Repro Steps

1. Boot Windows and connect to Wi-Fi using the Intel BE200 adapter.
2. Confirm that Windows networking works normally.
3. Start Ubuntu WSL2, through VS Code Remote WSL.
4. Use network applications inside WSL.
5. After an intermittent period, networking stops working on both WSL and the Windows host.
6. The WLAN adapter may still appear connected and may retain its IP address and default route, but traffic does not pass.
7. Reconnecting Wi-Fi, restarting WSL, or restarting network services does not reliably restore connectivity.
8. Attempt to shut down Windows. Shutdown frequently hangs indefinitely.
9. A forced power-off or forced restart is required.
10. After reboot, Event Viewer shows WHEA-Logger 17 for the Intel BE200, Netwaw18 6062, and Hyper-V/virtual networking events.

The problem has occurred with both networkingMode=nat and networkingMode=mirrored. Mirrored mode additionally produces repeated Hyper-V VmSwitch Event ID 15 errors indicating that FSE switch port configurations could not be restored because the object name was not found.

### Expected Behavior

Starting or using WSL2 should not reset or permanently wedge the physical Wi-Fi adapter.

A temporary adapter reset or corrected PCIe error should recover without causing host-wide network loss, Windows shutdown hangs, or a forced restart.

### Actual Behavior

Starting or using WSL2 intermittently causes complete network loss on both WSL and the Windows host.

The physical Intel BE200 adapter fails to recover correctly. Windows may still display the adapter as connected and retain an IP address, but network traffic stops.

A normal Windows shutdown then frequently hangs, requiring a forced power-off.

The issue occurs in both NAT and mirrored networking modes, so it is not limited to mirrored networking. Mirrored mode additionally produces FSE/VmSwitch port restoration failures.

Related events include:

- WHEA-Logger Event ID 17:
Corrected PCI Express AER errors for
PCI\VEN_8086&DEV_272B&SUBSYS_00F48086&REV_1A

- Intel Netwaw18 Event ID 6062:
Wi-Fi Driver Info

- Hyper-V-VmSwitch Event ID 15:
Failed to restore FSE switch port configuration.
Status: object name not found.
UniqueEvent: 45

Between 2026-09-10 and 2026-09-11, the logs contained:

- Hyper-V-VmSwitch Event 15: 54
- WHEA-Logger Event 17: 30
- Netwaw18 Event 6062: 28
- Kernel-Power Event 41: 9

Seven DRIVER_POWER_STATE_FAILURE (0x9F) bugchecks were recorded between September 1 and September 4. At least one inspected dump showed nwifi!FilterDetach in the blocked detach path.

A KERNEL_MODE_HEAP_CORRUPTION (0x13A) bugcheck occurred on September 10. The dump is:

[091026-14953-01.dmp](https://github.com/user-attachments/files/32088867/091026-14953-01.dmp)

### Diagnostic Logs

I have attached the following diagnostic archive:

[WSL_BE200_support_PRIVATE_2026-09-11.zip](https://github.com/user-attachments/files/32089407/WSL_BE200_support_PRIVATE_2026-09-11.zip)

The archive contains:

- Five Windows minidumps related to the 0x9F and 0x13A crashes
- Windows WLAN history report
- Hyper-V VmSwitch Event ID 15 events
- WHEA-Logger Event ID 17 events for the Intel BE200 PCIe endpoint
- Intel Netwaw18 Event ID 6062 events
- Kernel-Power Event ID 41 and bugcheck records
- WLAN AutoConfig and Host Network Service events
- Windows Reliability Monitor records
- WSL version, status, distribution and .wslconfig
- Intel BE200 driver information and advanced adapter properties
- NDIS adapter bindings, including the enabled Realtek LightWeight Filter
- Current Windows network configuration
- A manifest and a public issue summary

A live WSL networking WPR/WFP trace is not included because tracing was not active during the previous failures. The retained event logs, WLAN report and crash dumps were collected after the incidents.

The problem has occurred with both NAT and mirrored networking modes. Mirrored mode additionally produces repeated FSE/VmSwitch port restoration errors.

The archive contains potentially private diagnostic information and is intended for Microsoft support analysis.

No source file, test, or entry point is named. Start by reviewing the attached minidump, WSL_BE200_support_PRIVATE_2026-09-11.zip, Event Viewer evidence, and the behavior in both NAT and mirrored modes; a useful result would isolate whether WSL, Hyper-V VmSwitch, the NDIS binding, the Intel driver, or the PCIe endpoint is responsible and define a reproducible recovery or fix.

Written by the indexing model from the issue text.