Error code: CreateInstance/CreateVm/ConfigureNetworking/0x8007054f

[DeaneChen]

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

[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://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 here

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

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• Get a Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0xffffffff when restart the WSL after shutdown (#11549), similarity score: 0.78
• Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0xffffffff (#11597), similarity score: 0.76
• wsl 启动报错 (#10213), similarity score: 0.76
• Windows 11: WSL2 cannot able to start, Error: 0x80041002 (#8657), similarity score: 0.76
• How to solve WSL2 error 0x803b0017? (#10150), similarity score: 0.76

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[DeaneChen]

/emailed-logs

[github-actions]

Diagnostic information

Found '/emailed-logs', adding tag 'emailed-logs'

[DeaneChen]

Alright, I need to correct my previous description. Today, when I encountered this issue again, I tried changing autoProxy=true to false in the .wslconfig file and restarted WSL to fix it, but this time it didn't work. I had to restart the entire Windows system. (I've had instances where just restarting Clash resolved the issue, but they only worked once.)

[benhillis]

Is your system fully patched with Windows updates? There was a regression in Windows that has been fixed in a recent KB.

[DeaneChen]

Is your system fully patched with Windows updates? There was a regression in Windows that has been fixed in a recent KB.

I checked Windows Update, and it just notified me that I am using the latest version. However, I noticed that there is a manually installable patch, KB5046732. I will download it and continue to monitor whether the issue reoccurs.

[DeaneChen]

Is your system fully patched with Windows updates? There was a regression in Windows that has been fixed in a recent KB.

It still occurred, the latest KB patch didn't work.

[reflyable]

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

[DeaneChen]

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

我怀疑过端口问题，但我不确定是哪个冲突的端口。我刚刚检查了，没有在系统上找到使用53端口的进程。