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

[mdaniels5757]

Windows Version

Microsoft Windows [Version 10.0.26100.6584]

WSL Version

2.6.1.0

Are you using WSL 1 or WSL 2?

• [x] WSL 2
• [ ] WSL 1

Kernel Version

6.6.87.2-1

Distro Version

No response

Other Software

No response

Repro Steps

Occasionally, an error occurs when I try to start WSL. When it does occur, sometimes restarting hns fixes it, but more often I need to reboot. This can happen multiple times per day. Quite frustrating!

I always use the mirrored networking mode.

Note: I am aware of #12351, #12470, and #13454. Perhaps additional logs from me will help the team trace this down?

Expected Behavior

No error on launch.

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.

Diagnostic Logs

WslLogs-2025-10-10_17-15-55.zip WslNetworkingLogs-2025-10-10_17-06-27.zip

[github-actions[bot]]

Diagnostic information

Multiple log files found, using: https://github.com/user-attachments/files/22858083/WslLogs-2025-10-10_17-15-55.zip
.wslconfig found
Detected appx version: 2.6.1.0

[mdaniels5757]

I should note that when this occurs, it happens for all distros I have installed (Ubuntu, Debian, Arch, NixOS).

[dhtzs]

#13454

[OneBlue]

@CatalinFetoiu: Looks like this is caused by a failure to allocate a port range:

Microsoft.Windows.Lxss.Manager	Error	0	10-10-2025 14:16:22.620	"	"	"code: 	
failurecount: 	102
file: 	C:\__w\1\s\src\windows\service\exe\WslCoreGuestNetworkService.cpp
function: 	
hr: 	0x8007054F
linenumber: 	114
message: 	
threadid: 	17704
type: 	0"	C:\__w\1\s\src\windows\service\exe\WslCoreGuestNetworkService.cpp			6472	17704	2		00000000-0000-0000-0000-000000000000		

Do you know what could cause this ?

[ImViper]

mark

[xrh0905]

@CatalinFetoiu: Looks like this is caused by a failure to allocate a port range:

Microsoft.Windows.Lxss.Manager	Error	0	10-10-2025 14:16:22.620	"	"	"code: 	
failurecount: 	102
file: 	C:\__w\1\s\src\windows\service\exe\WslCoreGuestNetworkService.cpp
function: 	
hr: 	0x8007054F
linenumber: 	114
message: 	
threadid: 	17704
type: 	0"	C:\__w\1\s\src\windows\service\exe\WslCoreGuestNetworkService.cpp			6472	17704	2		00000000-0000-0000-0000-000000000000		

Do you know what could cause this ?

I also occured the same issues on my Windows 11 25H2. It seems like it has something to do with WinNAT/DynamicPortRange?

[rodrigo-a-moreno]

I realized the issue occurs on my laptop whenever it's connected to my docking station, which provides an Ethernet port while the laptop itself only has Wi‑Fi. If I disable the Ethernet connection and restart WSL, it launches without any problems. After that, I can re‑enable Ethernet and everything works normally.