Intermittent Wi-Fi connectivity loss after using WSL2 (Intel AX211) - adapter remains connected but cannot reach gateway

Nobody has claimed this yet.

### Windows Version

Microsoft Windows [Version 10.0.26200.8894]

### WSL Version

2.7.10.0

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

- [x] WSL 2
- [ ] WSL 1

### Kernel Version

6.18.33.2-2

### Distro Version

Ubuntu 24.04.3 LTS (Noble Numbat)

### Other Software

Jupyter Notebook / JupyterLab (although the issue also occurs when only using the WSL shell).

### Repro Steps

1. Boot Windows normally.
2. Start Ubuntu under WSL2.
3. Use WSL for some time. Sometimes I only use the shell, sometimes I run Jupyter Notebook.
4. After an unpredictable amount of time, Wi-Fi connectivity is lost.
5. The issue is intermittent, but recently it has become much more frequent (3-4 times in a single morning).
6. Rebooting Windows always restores connectivity.

### Expected Behavior

Wi-Fi connectivity should remain stable while using WSL2.

### Actual Behavior

Hardware:
- Laptop: HP OMEN 16
- Wireless adapter: Intel(R) Wi-Fi 6E AX211 160MHz

When the issue occurs:

- Windows still shows the Intel AX211 adapter as connected.
- The adapter remains in the "Up" state.
- The IP address, default gateway and DNS servers are still assigned.
- Ping to the local gateway fails (100% packet loss).
- Internet connectivity is completely lost.
- "netsh wlan show interfaces" hangs indefinitely.
- "Disable-NetAdapter -Name Wi-Fi" hangs indefinitely.
- "Get-NetAdapterStatistics" returns successfully.
- HNS service is still running.
- vmcompute is still running.
- "wsl --status" still responds normally.
- The only reliable recovery is rebooting Windows.

### Diagnostic Logs

The following troubleshooting steps have already been performed:

- Tested with the latest Intel Wi-Fi driver.
- Tested with the HP-provided Wi-Fi driver.
- Repaired Windows using the Windows Update repair option.
- Disabled Wi-Fi 6 by forcing the adapter to use 802.11ac only.
- Previously tested networkingMode=mirrored with dnsTunneling=true.
- The problem still occurs.

Additional observations:

- The issue initially seemed related to Jupyter, but it also occurs when only using the WSL shell.
- HNS and vmcompute continue running after connectivity is lost.
- WSL itself continues working normally.
- The adapter appears connected but cannot even reach the local router.
- The issue has become significantly more frequent. Initially it was difficult to reproduce, but it is now occurring several times per morning while using WSL2. This has made it much easier to reproduce the problem.

Start with the WSL2 and Ubuntu repro steps, then collect the listed Windows networking state when the Intel AX211 becomes unreachable. Compare runs with and without Jupyter Notebook and review the behavior of netsh wlan show interfaces, Disable-NetAdapter, Get-NetAdapterStatistics, HNS, vmcompute, and wsl --status; done means isolating a reproducible trigger and documenting a verified fix or mitigation.

Written by the indexing model from the issue text.