Repository navigation
There are no more endpoints available from the endpoint mapper #4403
Description
Command line fail when I try to upgrade to wsl2.
-
Windows build number: 10.0.18956.1000
-
What you're doing and what's happening:
wsl --set-version Arch 2 -
What's wrong / what should be happening instead:
There are no more endpoints available from the endpoint mapper
NOTE: The arch is from https://github.com/yuk7/ArchWSL And I think the failure is about the ICS service with my computer. The service was disabled by the admin and I can't start it.
If this issue is due to ICS, is there another way to upgrade to wsl2 without starting ICS?
Reacted by Gu0Yu and Neo
Activity
Drakota commentedon Aug 12, 2019
The distribution you're using is not compatible with version 2 of WSL or atleast has issues discussed in the thread.
Check this issue #89.
Biswa96 commentedon Aug 12, 2019
There is no "compatibility" criteria for WSL2. If you have a simple shell and it's dependent libraries (libc) you can run it also. Think WSL as a chroot.
I've tried many Linux distributions. I have a method to use Arch Linux. Try this https://github.com/Biswa96/WSLInstall/blob/master/docs/Install_Distributions.md.
byhc2 commentedon Aug 13, 2019
I have tried debian from the store. As long as I choose to install as version 2, it fails.
byhc2 commentedon Aug 13, 2019
If I install the linux as wsl1, everything goes OK. The problem occurs when I try to set the distribution as version 2.
Gu0Yu commentedon Aug 22, 2019
Hello, I also encountered this problem, the difference is that I installed Ubuntu, can you solve it?
HZ89 commentedon Sep 26, 2019
In my windows evaluation copy build 18980.vb_release.190907-1301 also have this problem, how can i fix it?
craigloewen-msft commentedon Sep 26, 2019
HarrisonZhu (@HZ89) can you send us networking logs for the problem? There are instructions on how to collect them here.
HZ89 commentedon Sep 27, 2019
ok, already submitted
benhillis commentedon Sep 27, 2019
HarrisonZhu (@HZ89) do you have a link handy?
18 remaining items
xiaods commentedon Feb 7, 2021
I have the same issue, any update on this?
VPraharsha03 commentedon Apr 9, 2021
LOuroboros
But in my case, this problem started after i deleted ICS along with this issue (#5821)
Even restoring the service couldn't resolve the issue. I even re-installed WSL and VMP
My DNS server is listening on port 53, so to keep the ICS disabled i tried deleting the triggers for HNS and this was the first time i'd encountered this and could resolve by restoring those triggers. Now the problem isn't being resolved.
slaadvak commentedon May 4, 2021
I also have this issue. Windows 1903 with Ubuntu 20.04.
therealkenc commentedon May 5, 2021
Anyone still experiencing this problem please post the output of
cmd.exe /c ver. It is unclear if this was #5821, which is better in 20231+.benhillis commentedon May 5, 2021
Agreed, I haven't seen this error anymore. I think something was fixed in the networking stack.
RobRoseKnows commentedon Jun 2, 2021
I'm getting this on a previous working WSL2 instance once my machine updated to insider build 21387. I was previously having network issues with that build, but unplugging and replugging my wifi dongle seemed to fix them. I'm wondering if that's related?
cjatoba commentedon Jul 10, 2021
For me it works again when enabling Windows Defender Firewall on Windows services
LOuroboros commentedon Aug 12, 2021
After about a year since I first installed Windows 10, I decided to format my PC today.
Miraculously, I got WSL2 working normally after following the steps written in the article at Microsoft Docs.
livein21st commentedon Nov 22, 2022
LOuroboros Which steps did you followed? can you paste the link here? Thanks!
LOuroboros commentedon Nov 22, 2022
https://learn.microsoft.com/en-us/windows/wsl/install-manual
theoparis commentedon Dec 27, 2023
I am having the exact same error with windows 11 with those steps ;(
Until WSL decides to work I have no other option but to use a Linux machine remotely
eoffermann commentedon Feb 21, 2024
After struggling with this off and on for months on different machines, I found that the following sequence seems to work for me:
Then in a new shell after that's done:
Basically, installs seem to fail frequently in wsl 2 but if you switch back to default version 1, install, then switch to version 2 it seems to work.
OneBlue commentedon May 14, 2024
This issue should be fixed on the latest Windows 10/11. Feel free to reopen if that's not the case though
theoparis commentedon Oct 26, 2024
It turns out a powershell script I ran to "debloat" windows had disabled the Windows Defender Firewall. I had to generate a new script to revert this option. I do wish the error message said that it needed the firewall service instead though.