WSL: Error code: CreateInstance/CreateVm/ConfigureNetworking/0x8007054f

Windows Version

Microsoft Windows [Version 10.0.22631.4460]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Ubuntu 22.04

Other Software

None

Repro Steps

Running wsl terminal first while wsl is stop.

Expected Behavior

wsl can start normally without any errors.

Actual Behavior

After Windows has been running for a certain period (during which WSL is usually inactive), there is a chance that the next time you attempt to start WSL, the following error may occur:

wsl: 出现了内部错误。
错误代码: CreateInstance/CreateVm/ConfigureNetworking/0x8007054f
wsl: 无法配置 networkingMode Mirrored) (网络,回退到 networkingMode None。

or maybe like this in english:

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

LOG:I’m not sure where the log will appear, and the error message doesn’t provide a log path.

I suspect this error code 0x8007054f is primarily caused by Windows, and the error code likely originates from the Windows system. Although WSL is functioning properly, there seems to be no internet connectivity.

And this error code always disappears after a Windows restart. Or I change autoProxy=true to false in the .wslconfig file. Of course, I just tested it, and even if I change the autoProxy configuration back to true and only restart WSL, it still works fine.

Diagnostic Logs

No response

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Reactions: 5
  • Comments: 20 (1 by maintainers)

Most upvoted comments

same for me. wsl --version:

WSL version: 2.3.24.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26100.2605

.wslconfig:

[wsl2]
dnsTunneling=true
firewall=true
autoProxy=true
networkingMode=mirrored

This worked for me: Enable “Windows Hypervisor Platform” (Windows 虚拟机监控程序平台) in Turn Windows features on or off. Source: https://stackoverflow.com/a/78092729

My configuration was silently disabled by an Android virtualization software without any notification. After re-enabling it, the WSL network started working properly again.

可以先关闭占用53端口的系统进程,然后在进程重启之前快速打开wsl

same

wsl --version

WSL 版本: 2.5.7.0
内核版本: 6.6.87.1-1
WSLg 版本: 1.0.66
MSRDC 版本: 1.2.6074
Direct3D 版本: 1.611.1-81528511
DXCore 版本: 10.0.26100.1-240331-1435.ge-release
Windows: 10.0.26100.4652
.wslconfig

[wsl2]
firewall=false
networkingMode=Mirrored

same question too

WSL 版本: 2.4.11.0
Kernel 版本: 5.15.167.4-1
WSLg 版本: 1.0.65
MSRDC 版本: 1.2.5716
Direct3D 版本: 1.611.1-81528511
DXCore 版本: 10.0.26100.1-240331-1435.ge-release
Windows 版本: 10.0.26100.3194

.wslconfig

[experimental]
autoMemoryReclaim=gradual  
networkingMode=mirrored
dnsTunneling=true
firewall=true
autoProxy=true

I’ve noticed that on my machine, after a reboot and then starting WSL, this issue temporarily disappears. However, after running for several days, the problem reappears. I don’t know if it’s possible that some other program is causing these issues, I haven’t installed anything new that would obviously cause this. Hopefully the above information helps