WSL icon indicating copy to clipboard operation
WSL copied to clipboard
verified publisher icon microsoft

WSL install misconfigured? "Failed to create network endpoint with address: '172.28.17.6', assigned new address: '172.25.223.252'." Hyper-V Extensible Virtual Switch is disabled on all my adapters.

Open futuremotiondev opened this issue 6 months ago • 3 comments

Windows Version

Microsoft Windows [Version 10.0.19045.5965]

WSL Version

2.5.9.0

Are you using WSL 1 or WSL 2?

  • [x] WSL 2
  • [ ] WSL 1

Kernel Version

6.6.87.2-1

Distro Version

Ubuntu-24.04 (When I run lsb_release -r I get No LSB modules are available.

Other Software

No response

Repro Steps

  1. I performed the following commands:
2025-06-17 18:09 C:\Users\username\Desktop> wsl --update
Installing: Windows Subsystem for Linux
Windows Subsystem for Linux has been installed.
2025-06-17 18:10 C:\Users\username\Desktop> wsl --set-default-version 2
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
The operation completed successfully.
2025-06-17 18:10 C:\Users\username\Desktop> wsl --install Ubuntu-24.04
Downloading: Ubuntu 24.04 LTS
Installing: Ubuntu 24.04 LTS
wsl: Failed to create network endpoint with address: '172.28.17.6', assigned new address: '172.25.223.252'
Distribution successfully installed. It can be launched via 'wsl.exe -d Ubuntu-24.04'
Launching Ubuntu-24.04...
Provisioning the new WSL instance Ubuntu-24.04
This might take a while...
Create a default Unix user account:...

After I created my account Ubuntu seems to be working fine and network access is working in WSL. But the following line makes me worry:

wsl: Failed to create network endpoint with address: '172.28.17.6', assigned new address: '172.25.223.252'

What are these endpoint IP addresses? Why is it assigning a new address?

Also, in my network adapter properties, I have three adapters now:

  1. My Wi-Fi Adapter from my motherboard
  2. vEthernet (Default Switch) (Hyper-V Virtual Ethernet Adapter)
  3. vEthernet (WSL) (Hyper-V Virtual Ethernet Adapter)

Image

I am concerned because in all three adapters the Hyper-V Extensible Virtual Switch is disabled, and I cannot enable it.

Image

If I enable the checkbox and then click OK, I get this dialog:

Image

Is my WSL2 installation misconfigured? From what I understand the Hyper-V Extensible Virtual Switch is important to proper functioning of WSL.

I've tried:

  1. Completely uninstalling WSL2, Removing all network adapters and reinstalling my network drivers.
  2. Reinstalling WSL2 after this.
  3. Unchecking Hyper-V, Virtual Machine Platform, and Windows Subsystem for Linux in Windows Features, and then running wsl --uninstall.
  4. Then restarting my computer and re-enabling all of these features again. And then restarting the computer again.
  5. Running wsl --update, and then wsl --set-default-version 2.

Again, distros install fine now and I have connectivity in WSL. So I'm not sure if this is a non-issue or something to be concerned about.

Can someone shed some more light on this?

Expected Behavior

  1. I expected WSL to not assign a new network endpoint IP.
  2. What are these IP endpoints anyway?
  3. I expect to be able to enable the Hyper-V Extensible Virtual Switch for my network adapters.
  4. Should I be concerned?

Actual Behavior

  1. Relevant Terminal Output:
2025-06-17 18:10 C:\Users\username\Desktop> wsl --install Ubuntu-24.04
Downloading: Ubuntu 24.04 LTS
Installing: Ubuntu 24.04 LTS
wsl: Failed to create network endpoint with address: '172.28.17.6', assigned new address: '172.25.223.252'
  1. Hyper-V Extensible Virtual Switch is disabled on all my network adapters:
1. My Wi-Fi Adapter from my motherboard
2. vEthernet (Default Switch) (Hyper-V Virtual Ethernet Adapter)
3. vEthernet (WSL) (Hyper-V Virtual Ethernet Adapter)

Diagnostic Logs

There was an error with the collect-wsl-logs.ps1 script when I ran it with Windows Powershell:

(base) PS C:\Users\futur\Desktop\DL\Blender> .\collect-wsl-logs.ps1
Log collection failed to start (exit code: -984076287), trying to reset it.
Log collection is running. Please reproduce the problem and once done press any key to save the logs.                   Saving logs...                                                                                                          Logs saved in: C:\Users\futur\Desktop\DL\Blender\WslLogs-2025-06-17_18-56-57.zip. Please attach that file to the GitHub issue.

Here is the zip of the logs:

WslLogs-2025-06-17_18-56-57.zip

futuremotiondev avatar Jun 18 '25 00:06 futuremotiondev

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information 
.wslconfig found
Detected appx version: 2.5.9.0
Found no WSL traces in the logs

github-actions[bot] avatar Jun 18 '25 00:06 github-actions[bot]

What are these endpoint IP addresses? Why is it assigning a new address?

This is usually a sign that "something" else is using that address range. If you have connectivity working in WSL, and you're only seeing this warning once, I wouldn't worry too much about it.

OneBlue avatar Jun 18 '25 01:06 OneBlue

What are these endpoint IP addresses? Why is it assigning a new address?

This is usually a sign that "something" else is using that address range. If you have connectivity working in WSL, and you're only seeing this warning once, I wouldn't worry too much about it.

Good to know - that puts my mind at ease. Do you happen to know anything about the importance of the Hyper-V Virtual Ethernet Adapter? Should this be enabled on my adapters?

futuremotiondev avatar Jun 18 '25 01:06 futuremotiondev

I don't, but if everything works as expected, I wouldn't enable it.

OneBlue avatar Jun 18 '25 18:06 OneBlue