microsoft
wsl: Failed to configure network (networkingMode Mirrored), falling back to networkingMode None.
Windows Version
Microsoft Windows [Version 10.0.26100.5074]
WSL Version
2.5.7.0
Are you using WSL 1 or WSL 2?
- [x] 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
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://raw.githubusercontent.com/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 [email protected] 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'.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Could you please update your version of WSL? In newer versions we fall back to other networking modes.
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
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
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
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
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:~>
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 .
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.
@jeremyenos have you tried executing ipconfig /flushdns to see if it makes any difference?
Yep. That was a step in a different series of solutions I attempted. No difference. I have PIA client installed, Cisco Anyconnect client installed- but have had for years w/o issue. I still remain suspect that maybe an update to one of those is playing a role. Haven't tried full removal of those yet.
it's hit or miss now I sometimes experience it on and off, even when not running VPN software
It's also intermittent for me, and unfortuantely is occuring on my work laptop now too.
Same, has been an issue for several weeks with Windows 11 stable channel update.
This works for me as @zed76r mentioned:
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 .
Same for me. WSL version: 2.6.1.0
Sometimes restarting wsl works, most of the time I have to restart windows. But it will happen again after a few hours.
got the exact same issue, fixed with batch script (after looking into other issues and combining answers) :
create file fix.bat with the following content :
@echo off
echo WSL FIX
echo [1/3] Winsock Reset
netsh winsock reset
echo.
echo [2/3] TCP/IP Reset
netsh int ip reset
echo.
echo [3/3] Restarting WSL Service
net stop wslservice
net start wslservice
echo.
echo Launching WSL
start cmd.exe /k wsl
timeout /t 5 > nul
exit
you should run this script as admin, i recommend to create a shortcut then right click, properties, (you should already be on 'shortcut' tab if not click on shortcut tab) then click on advanced button and check run as admin
@R-3MY Thanks for sharing that. As a data-point, it looks like that can 'repair' the WSL network stack only sometimes. I've had my system running for a few days and went to use WSL today and encountered this dreaded 'falling back' error again. I attempted to use this script to get it working but it wouldn't work (even after multiple attempts... just in case). I ended up restarting and for the first time encountered this error very soon after a new boot, but this time the script was able to fix it. It seems likely that there must be a number of different factors that lead to the failure to set up networking.
@R-3MY - yes, thank you for sharing. I didn't try your script yet, but I think when I was testing, all of the steps in your script were part of some things I tried, and it persists for me. (there is no time after a reboot where it works at all for me that I've been able to observe) Update: I got time to try your script just to be extra thorough. Still fails. (this is right after a fresh reboot too)
wsl: An internal error occurred.
Error code: CreateInstance/CreateVm/ConfigureNetworking/0x8007054f
wsl: Failed to configure network (networkingMode Mirrored), falling back to networkingMode None.
Got the same error. Hotfix was:
I'm guessing it's adminstrator permissions
Same problem for me as well. We cannot use the netsh suggestions, we do not have admin access on the laptops. Solution must require non-admin rights. Like others, I can try to wsl.exe --shutdown. But it does not work every time. Only thing that works every time, is just to reboot the whole PC. I found that whenever any new Windows updates are installed and I need to update, after that update mirror mode might fail still. Need to reboot again after windows update restarts. After the second restart wsl mirror mode works again. I agree this seems to have happened since a Windows update was applied earlier this year.
UPDATE: When working from home through the VPN a reboot does not help. A work around is the following:
- Power on
- Start WSL
- If the error appears, disconnect from the network (I use an ethernet cable). Literally disconnect the cable.
-
wsl --shutdown - Start WSL again. mirror mode works.
- Reconnect to the network
Am wondering if this is related to the Palo Alto Global Protect VPN client?
UPDATE2: The problem seems to happen when I am in the office or remote. GlobalProtect is set up to run no matter what and wont give internet access until it is able to connect back to the home base. So maybe thats related?
Also make sure you disconnect all network interfaces. Wired and Wireless. For instance when I disconnect the Ethernet cable, my PC will automatically connect to wireless, need to turn that off too. Then try to start WSL. I also found that even if you reboot, and disconnect all networking, the same failure will happen the first time you start wsl. So run wsl --shutdown and try running wsl again, should work the second time. Then connect all your networking again.
Thanks @davehouser1 This actually worked for me as well. But I only disabled the network adapter instead of unplugging.
Subscribing to this. Same symptoms, but none of the networking stack fixes mentioned above work for me.
So not a fix but a workaround some people might be able to use for now.
Depending on what you’re using mirrored mode for, you may be able to switch to virtioproxy mode instead. In my case, I needed my Cisco AnyConnect VPN to route WSL traffic so I could SSH into my systems. Most guides recommend me to just set it to mirrored mode for this, but I found that virtio-proxy works for this scenario and doesn’t crash.
I’m sure there are differences between the two modes, and this won’t cover every use case, but if your needs are simple like mine, this might be a viable alternative.
@AMDHome - life saver. This has me back up and running. Didn't even know about this mode. Thank you!
@AMDHome I had also employed that workaround with some success, but I found virtioproxy made things so god awful slow it was hard to work with. @davehouser1 I also installed GlobalProtect recently- I am almost certain I had the issue before that or I'd have suspected it earlier, but seeing you mention it makes me inclined to test removal just to make sure.
@jeremyenos were you able to uninstall, did it help? I would try, but we dont have admin priv on our systems to do so.