wsl: Mirrored networking mode is not supported: Windows version 26200.7171 does not have the required features.

[vishiswoz]

Windows Version

Microsoft Windows [Version 10.0.26200.7171]

WSL Version

2.6.1.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.2-1

Distro Version

Ubuntu 24.04

Other Software

No response

Repro Steps

>wsl --shutdown

>bash
wsl: Mirrored networking mode is not supported: Windows version 26200.7171 does not have the required features.
Falling back to NAT networking.
wsl: Failed to configure network (networkingMode Nat), falling back to networkingMode VirtioProxy.
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

Expected Behavior

I'm trying to get mirrored or NAT networking working so I can use vscode server on the remote instance. It's unable to connect and through a lot of Googling i find it won't work on VirtioProxy. I am unsure why I can't get NAT or mirrored to work. I have confirmed that I have all network services running and the enabled features. This was working before but has broken on a recent windows update (25H2) that I installed yesterday.

Actual Behavior

Networking didn't setup properly

Diagnostic Logs

WslLogs-2025-11-27_08-37-52.zip

[github-actions]

Diagnostic information

.wslconfig found
Appx package is not installed

[htharoldht]

me too! apt updgrade cannot work

[OneBlue]

Cătălin Emil Fetoiu (@CatalinFetoiu): The logs show that virtual machine platform is enabled:

FeatureName : VirtualMachinePlatform
State       : Enabled

Could you have a look ?

[vruss]

Having exact same error

[daviewales]

Related? #13068

[Natzukashi]

Related? #13068

No that didn't resolve the issue for me. Strange it was working perfectly a few hours ago!

[th3nolo]

I'm seeing a very similar fallback pattern on another Windows 11 25H2 machine.

Details:

OS: Windows 11 Pro N 25H2
Windows build: 10.0.26200.8328
WSL version: 2.7.3.0
Kernel: 6.6.114.1-1
Default distro: Ubuntu-D-Drive
Distro version: WSL2

Configuration/runtime behavior:

%UserProfile%\.wslconfig includes:
[wsl2]
networkingMode=mirrored
memory=22GB
processors=16
swap=8GB

[experimental]
autoMemoryReclaim=disabled
sparseVhd=true

• Windows Subsystem for Linux Settings shows Networking mode = Mirrored.
• The memory/swap settings are being applied, so .wslconfig is being read.
• wslinfo --networking-mode still reports nat after wsl --shutdown and after a full Windows reboot.
• ip route inside WSL confirms NAT-style routing, e.g. default gateway in a 172.29.x.x range.
• VirtualMachinePlatform and Microsoft-Windows-Subsystem-Linux are enabled.
• HypervisorPlatform was initially disabled; after enabling it with DISM and setting bcdedit /set hypervisorlaunchtype Auto, then doing a full reboot, the runtime mode is still nat.
• Services checked from Windows: hns, vmcompute, and WSLService are running.

One possible wrinkle: this is a relocated/imported-style distro. The registered default distro is Ubuntu-D-Drive, with a BasePath under E:\WSL\Ubuntu, not the usual Store Ubuntu path under %LOCALAPPDATA%. I do not think that is the root cause because WSL is clearly reading the global .wslconfig, but I am including it in case the fallback is sensitive to imported/relocated distributions.

This looks like the same 26200.x line behavior: Mirrored is selected in config/UI, but the runtime continues to start as NAT.

[baoyu0]

Same issue here. Windows 11 25H2 Build 26200.8457, WSL 2.7.3.0. Mirrored networking mode fails with the same error after a recent 25H2 update. Please fix this. 🙏

[rowleya]

I just went to try this in an attempt to solve the (still annoying) #12747, but this happened.

WSL version: 2.7.8.0
Kernel version: 6.18.33.1-1
WSLg version: 1.0.73.2
MSRDC version: 1.2.6676
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26200.8457