There are no more endpoints available from the endpoint mapper

[byhc2]

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?

lsxx.zip

[Drakota]

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]

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]

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.

I have tried debian from the store. As long as I choose to install as version 2, it fails.

[byhc2]

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.

If I install the linux as wsl1, everything goes OK. The problem occurs when I try to set the distribution as version 2.

[Gu0Yu]

Hello, I also encountered this problem, the difference is that I installed Ubuntu, can you solve it?

[HZ89]

In my windows evaluation copy build 18980.vb_release.190907-1301 also have this problem, how can i fix it?

PS C:\WINDOWS\system32> wsl -l --all -v
  NAME            STATE           VERSION
* Ubuntu-18.04    Running         1
PS C:\WINDOWS\system32> wsl --set-version Ubuntu-18.04 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
There are no more endpoints available from the endpoint mapper.
PS C:\WINDOWS\system32>

[craigloewen-msft]

@HZ89 can you send us networking logs for the problem? There are instructions on how to collect them here.

[HZ89]

@HZ89 can you send us networking logs for the problem? There are instructions on how to collect them here.

ok, already submitted

[benhillis]

@hz89 do you have a link handy?

[ghost]

This issue has been automatically marked as stale because it has marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment. Thank you for your contributions to WSL!

[mcwilbur]

I got the same issue while upgrading Ubuntu to WSL2. Console output :

PS C:\Users\Jonathan> wsl --set-version Ubuntu 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2\n
There are no more endpoints available from the endpoint mapper.

I recorded the issue and submitted it to the Feedback Hub under https://aka.ms/AA6tptp

[okhowang]

my group disable ics service for security reason, can wsl 2 do not depend ics service?

[krwu]

my group disable ics service for security reason, can wsl 2 do not depend ics service?

I'm in the same situation. Will WSL 2 work without ICS in the future?

[kashan91]

I don't think ICS has anything to do with it. I have it ON and still have the same issue. Any suggestions

[jcimoch]

I have the same issue, any update on this?

[jcimoch]

https://aka.ms/AA8y16o, attached network logs

[jcimoch]

[Daltz333]

I also have this issue.

[LOuroboros]

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?

lsxx.zip

I don't think ICS is causing this problem. I'm also getting the exact same issue ("There are no more endpoints available from the endpoint mapper"), but enabling and starting that service, reopening CMD and using wsl --set-version <distro> 2 didn't solve it on my end.

EDIT: Sorry, it was dumb of me not to provide more information. I have Ubuntu 18.04 installed on my WSL 1. To use WSL2, what I did was essentially following the steps listed in this Microsoft Docs page.

So I enabled the Virtual Machine Platform by using dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart. Then I proceeded to install the Linux Kernel update package which I downloaded from here. After that, I opened the Windows command prompt as Administrator, used wsl --set-version Ubuntu-18.04 2, and the result was:

Conversion in progress, this may take a few minutes... For information on key differences with WSL 2 please visit https://aka.ms/wsl2 There are no more endpoints available from the endpoint mapper.

I got a different error prior, but it was caused by me having the Hyper-V related services disabled. I enabled them again and that solved it.

EDIT2 As mentioned by @kashan91 right here, I disabled WSL and the Virtual Machine Platform, restarted my PC, enabled them again, restarted yet again, used wsl --set-default-version 2 and tried to install a clean copy of Ubuntu 18.04, but sadly, I got the exact same error.

[gurnec]

I disabled WSL and the Virtual Machine Platform, restarted my PC, enabled them again, restarted yet again, ... I got the exact same error.

@LOuroboros FWIW, I also have Hyper-V installed, and although the above did not work for me, removing those two along with all other Hyper-V components, rebooting and reinstalling, did work for me. (I only needed to reinstall the components, not the Ubuntu instance/store app.)

I'd guess this would include Guarded Host, Microsoft Defender Application Guard, Windows Hypervisor Platform, Windows Sandbox, and maybe Containers too, if any of them are installed.

Of course, proceed at your own risk if you are actively using any of these features lest you lose any config/VMs/containers.

_{also pinging @xiaods from the other issue in case it helps}

[LOuroboros]

I tried the process written at Microsoft Docs again, but sadly, the result hasn't changed in the past almost 3 months since my post above.

Is there any chance I may have a critical Windows service required by WSL2 disabled or something like that? WSL1 does work just fine, but WSL2's Linux-like performance is too juicy not to care about it.

EDIT: I tried the process described at https://github.com/microsoft/WSL/issues/5912#issuecomment-694922191 but that didn't work either.

[xiaods]

I also have this issue.

[xiaods]

I have the same issue, any update on this?

[VPraharsha03]

@LOuroboros

I don't think ICS is causing this problem. I'm also getting the exact same issue

But in my case, this problem started after i deleted ICS along with this issue (https://github.com/microsoft/WSL/issues/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]

I also have this issue. Windows 1903 with Ubuntu 20.04.

[therealkenc]

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]

Agreed, I haven't seen this error anymore. I think something was fixed in the networking stack.

[RobRoseKnows]

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]

For me it works again when enabling Windows Defender Firewall on Windows services

[LOuroboros]

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]

@LOuroboros Which steps did you followed? can you paste the link here? Thanks!

[LOuroboros]

@LOuroboros Which steps did you followed? can you paste the link here? Thanks!

https://learn.microsoft.com/en-us/windows/wsl/install-manual

[theoparis]

@LOuroboros Which steps did you followed? can you paste the link here? Thanks!

https://learn.microsoft.com/en-us/windows/wsl/install-manual

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]

After struggling with this off and on for months on different machines, I found that the following sequence seems to work for me:

wsl --set-default-version 1
wsl --install DISTRIBUTION
Enter userid and desired password when asked

Then in a new shell after that's done:

wsl --set-default-version 2

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]

This issue should be fixed on the latest Windows 10/11. Feel free to reopen if that's not the case though

[theoparis]

@LOuroboros Which steps did you followed? can you paste the link here? Thanks!

https://learn.microsoft.com/en-us/windows/wsl/install-manual

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

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.