Failed to configure network (networkingMode Mirrored), falling back to networkingMode None. Error code: CreateInstance/CreateVm/ConfigureNetworking/0x8007054f
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
### 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](https://github.com/user-attachments/files/22858083/WslLogs-2025-10-10_17-15-55.zip)
[WslNetworkingLogs-2025-10-10_17-06-27.zip](https://github.com/user-attachments/files/22858082/WslNetworkingLogs-2025-10-10_17-06-27.zip)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the WSL launch path named in the error, CreateInstance/CreateVm/ConfigureNetworking, and inspect the attached WslLogs and WslNetworkingLogs archives. Reproduce startup with networkingMode Mirrored, compare failures with cases where restarting hns or rebooting helps, and consider the issue done when launches no longer fall back to networkingMode None.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100