wsl: Failed to configure network (networkingMode Mirrored), falling back to networkingMode None.

[ikifar2012]

Windows Version

Microsoft Windows [Version 10.0.26100.5074]

WSL Version

2.5.7.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.1

Distro Version

Ubuntu 24.04

Other Software

No response

Repro Steps

Start WSL using wsl command and the following WSL config

[wsl2]
networkingMode=mirrored

Expected Behavior

WSL should start fine and networking should work in mirrored mode

Actual Behavior

wsl: An internal error occurred.
Error code: CreateInstance/CreateVm/ConfigureNetworking/0x8007054f
wsl: Failed to configure network (networkingMode Mirrored), falling back to networkingMode None.

Occasionally it is resolved with a reboot, but even running wsl --shutdown and restarting just WSL results in the same error then requires a system reboot

Diagnostic Logs

I was unable to get logs at the time of this failing but I was able to capture this screenshot

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://github.com/ghraw/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[benhillis]

Could you please update your version of WSL? In newer versions we fall back to other networking modes.

[brett19]

I've also been encountering this regularly. I've updated Windows, WSL and Ubuntu to the latest versions and continue to encounter it. I've attached the log collection file which I created by running log collection with my WSL environment shut down (by wsl --shutdown), then starting a WSL environment which prints what I've included below, then finished the log collection.

wsl: An internal error occurred.
Error code: CreateInstance/CreateVm/ConfigureNetworking/0x8007054f
wsl: Failed to configure network (networkingMode Mirrored), falling back to networkingMode None.

WslLogs-2025-09-12_17-53-00.zip

[hechz]

WslLogs-2025-09-15_15-02-05.zip

I've been having this issue repeatedly over the last weeks. The only workaround I have found is to disable and re-enable all WSL and Hyper-V Features completely

Get-WindowsOptionalFeature -Online |? FeatureName -match 'Microsoft-Windows-Subsystem-Linux|Hyper.*' |? State -eq Enabled | Disable-WindowsOptionalFeature -Online -NoRestart
Restart-Computer -Force -Confirm:$false

#after reboot
Get-WindowsOptionalFeature -Online |? FeatureName -match 'Microsoft-Windows-Subsystem-Linux|Hyper.*' |? State -eq Disabled | Enable-WindowsOptionalFeature -Online -NoRestart

[dkesik]

Having exact same problem.
As a workaround I reset the Windows 11 network stack and it works until next sleep/restart.

From PowerShell:

netsh winsock reset
netsh int ip reset

[ikifar2012]

Could you please update your version of WSL? In newer versions we fall back to other networking modes.

The issue appears to be gone for me, not sure if it was a Windows update or WSL update... I don't see any WSL update in my Microsoft Store update history like I usually see

[dhtzs]

Getting the same error.

[jeremyenos]

Same error. (on all guests)

I have uninstalled docker desktop, hyper-v, but they've been there for years w/o issue.
I have uninstalled/reinstalled Virtual Machine Platform and Windows Hypervisor Platform as others have suggested and it still makes no difference.

Nat mode works, VirtioProxy mode works but is horribly slow. Mirrored mode, which I've been using for years, just suddenly stopped working and I don't know why.

jenos@ammo:~> wsl.exe --version
WSL version: 2.6.1.0
Kernel version: 6.6.87.2-1
WSLg version: 1.0.66
MSRDC version: 1.2.6353
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26100.6725
jenos@ammo:~> cat /etc/*release
NAME="openSUSE Leap"
VERSION="15.6"
ID="opensuse-leap"
ID_LIKE="suse opensuse"
VERSION_ID="15.6"
PRETTY_NAME="openSUSE Leap 15.6"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.6"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Leap"
LOGO="distributor-logo-Leap"
jenos@ammo:~>

[zed76r]

Disabled http proxy in system before start WSL is worked for me.
Strangely, if I re-enable the HTTP proxy after successfully starting WSL, it can still start normally even after running wsl --shutdown .

[jeremyenos]

Disabled http proxy in system before start WSL is worked for me. Strangely, if I re-enable the HTTP proxy after successfully starting WSL, it can still start normally even after running wsl --shutdown .

Interesting- thanks for posting. I don't have a proxy enabled in my case unfortunately, so it must be something different.

[dhtzs]

@jeremyenos have you tried executing ipconfig /flushdns to see if it makes any difference?