search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.41k stars 822 forks source link

There are no more endpoints available from the endpoint mapper #5152

Closed kashan91 closed 4 years ago

kashan91 commented 4 years ago

Command line fail when I try to upgrade to wsl2. There was no problem with WSL1. I tried to remove Ubuntu and reinstall it, no difference. Virtual Machine Platform is active.

Windows build number: 19041.208

What you're doing and what's happening: wsl --set-version Ubuntu 2

The output:

PS C:\WINDOWS\system32> 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
There are no more endpoints available from the endpoint mapper.

I tried to remove the ubuntu and run the following command first:

wsl --set-default-version 2

after installing ubuntu again it keeps stuck on:

Installing, this may take a few minutes...

when I CTRL+C and relaunch it again it gives me this error:

WslRegisterDistribution failed with error: 0x8000000d An illegal state change was requested.

I don't know what to do now.

kashan91 commented 4 years ago

Fixed it .. uninstalled Windows Subsystem for Linux and Virtual Hypervisor Platform restart then reinstall them then restart .. it worked after

vj-abishek commented 4 years ago

I tried to uninstall wsl and virtual platform and reinstall again. Still, it seems not working. In the command line I'm just seeing this

For information on key differences with WSL 2 please visit https://aka.ms/wsl2

I don't know what to do.

Windows build number: 19041.208

kashan91 commented 4 years ago

I had the same issues many times .. you just need to wait and wait until it works ..

jcimoch commented 4 years ago

I'm having exact the same issue on windows 10 home, any ideas?

Fixed it .. uninstalled Windows Subsystem for Linux and Virtual Hypervisor Platform restart then reinstall them then restart .. it worked after

this doesn't fix it for me

xiaods commented 4 years ago

Fixed it .. uninstalled Windows Subsystem for Linux and Virtual Hypervisor Platform restart then reinstall them then restart .. it worked after

it doesn't works.

vj-abishek commented 4 years ago

@xiaods I also had the same issue. I installed latest Ubuntu distro from Microsoft store. Now it works. But cannot upgrade old Ubuntu distro from wsl1 to wsl2. You try to uninstall your distro and reinstall it.

xiaods commented 4 years ago

@vj-abishek sad news. i have reinstall the Ubuntu 20.04 LTS. it can't works. also report no more endpoints.

olmerg commented 4 years ago

I have the same problem when I try to open wsl2 with ubuntu 20.04. I resintall ubuntu 20.04 and does not work

nabeelmoeen commented 3 years ago

I started getting this error after the latest Windows fast ring build got installed overnight.

Build 20262.fe_release.201113-1436

EDIT: Another reboot seems to have fixed it.

xiaods commented 3 years ago

I started getting this error after the latest Windows fast ring build got installed overnight.

Build 20262.fe_release.201113-1436

EDIT: Another reboot seems to have fixed it.

what way to fixed it? please clear it.

Koesters commented 3 years ago

I started getting this error after the latest Windows fast ring build got installed overnight.

Build 20262.fe_release.201113-1436

EDIT: Another reboot seems to have fixed it. Same build but error was also on previous build

I have: reboot works. then can't cleanly reboot dmp file shows. DRIVER STATE FAILURE. raspppoe.sys. Then the broken reboot after BSOD it works again and so on.

Basically when I can cleanly reboot this error comes and when the reboot shutdown doesn't work and it's a hard reset with BSOD WSL2 works.

Windows Memory Test no errors

PS C:\WINDOWS\system32> sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations.

WISM no errors ..

Check disk on C no errors

In windows terminal I get:

There are no more endpoints available from the endpoint mapper. [process exited with code 4294967295]

No docker as here https://github.com/microsoft/WSL/issues/4904

"Power State failure dump

Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\xxx\Desktop\112220-16578-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 20262 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 20262.1.amd64fre.fe_release.201113-1436 Machine Name: Kernel base = 0xfffff8037aa00000 PsLoadedModuleList = 0xfffff8037b633c30 Debug session time: Sun Nov 22 02:56:45.725 2020 (UTC + 0:00) System Uptime: 0 days 0:24:41.404 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ....... Loading User Symbols Loading unloaded module list ............. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff8037ae16340 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff803783157d0=000000000000009f 0: kd> !analyze -v ERROR: FindPlugIns 8007007b

DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time. Arguments: Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem. Arg2: 000000000000012c, Timeout in seconds. Arg3: ffff9985703dc040, The thread currently holding on to the Pnp lock. Arg4: fffff80378315800, nt!TRIAGE_9F_PNP on Win7 and higher

Debugging Details:

Implicit thread is now ffff9985`703dc040 *** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 4077

Key  : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-C7EMGBP

Key  : Analysis.DebugData
Value: CreateObject

Key  : Analysis.DebugModel
Value: CreateObject

Key  : Analysis.Elapsed.mSec
Value: 16939

Key  : Analysis.Memory.CommitPeak.Mb
Value: 102

Key  : Analysis.System
Value: CreateObject

Key  : WER.OS.Branch
Value: fe_release

Key  : WER.OS.Timestamp
Value: 2020-11-13T14:36:00Z

Key  : WER.OS.Version
Value: 10.0.20262.1

ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 BUGCHECK_CODE: 9f BUGCHECK_P1: 4 BUGCHECK_P2: 12c BUGCHECK_P3: ffff9985703dc040 BUGCHECK_P4: fffff80378315800 DRVPOWERSTATE_SUBCODE: 4 FAULTING_THREAD: ffff9985703dc040 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System

LOCK_ADDRESS: fffff8037b650560 -- (!locks fffff8037b650560) 1 total locks

PNP_TRIAGE_DATA: Lock address : 0xfffff8037b650560 Thread Count : 1 Thread address: 0xffff9985703dc040 Thread wait : 0x12759

BAD_STACK_POINTER: fffff803783157c8

STACK_TEXT:
ffff828247298dc0 fffff8037ad03ebd : 0000000000000000 ffff9985703dc040 0000000000000103 fffff8037b706540 : nt!KiSwapContext+0x76 ffff828247298f00 fffff8037ad05624 : ffff9985703dc040 0000000000000000 ffff998500000000 ffff9985703dc100 : nt!KiSwapThread+0x34d ffff828247299000 fffff8037ad05d76 : 0000000000000000 ffff998500000000 0000000000000000 0000000000000000 : nt!KiCommitThreadWait+0x1d4 ffff8282472990a0 fffff8037f487a0c : ffff99857970d418 fffff80300000000 ffff99857970c000 fffff80300000000 : nt!KeWaitForSingleObject+0x236 ffff828247299190 fffff8037f480244 : 0000000000000008 ffff828247299230 0000000000000004 0000000000000000 : ndis!KWaitEventBase<wistd::integral_constant<enum _EVENT_TYPE,0> >::Wait+0x28 ffff8282472991d0 fffff8037f4ab09d : ffffce089fd245d0 fffff8037f4ab080 ffffce089fafce28 fffff8037f468050 : ndis!Ndis::BindEngine::ApplyBindChanges+0xb4 ffff828247299220 fffff8037f48f4d0 : ffffce089fd24610 fffff8037f4ab080 ffffce089fafce28 ffff99857970c000 : ndis!::+0x1d ffff828247299250 fffff8037f48f415 : 0000000000000000 fffff8037f44f168 0000000000000000 ffffce089fafce20 : ndis!NDIS_BIND_DRIVER_BASE::ForEachLink+0xa4 ffff8282472992a0 fffff8037f48f3b3 : 0000000000000000 ffff99857fe35e58 0000000000000010 fffff8037f3982dd : ndis!NDIS_BIND_DRIVER_BASE::SetRunningDriverIsReady+0x41 ffff8282472992d0 fffff8037f4c4764 : ffff99857fe35ae0 ffff8282472993e8 ffff8282472993e8 ffff99857fe35b28 : ndis!NDIS_BIND_PROTOCOL_DRIVER::SetRunningDriver+0x63 ffff828247299320 fffff8037f418c46 : ffff99857fe35ae0 fffff8037f468050 fffff8037f468050 fffff8037f44eec0 : ndis!NdisDeregisterProtocol+0xd4 ffff828247299390 fffff8039403111a : fffff80394039000 fffff80300000000 ffff99857fdd7ab0 00000000000000de : ndis!NdisDeregisterProtocolDriver+0x66 ffff8282472993e0 fffff8039403c494 : 00000000000000de ffff828247299468 0000000000000008 0000000000000000 : raspppoe!RasPppoeCleanup+0x66 ffff828247299410 fffff8037f49f283 : ffff99857fdd7ab0 ffff99857fdd7ab0 fffff8037f468050 ffff99857fd1ae10 : raspppoe!MpUnload+0x44 ffff828247299440 fffff8037f3db244 : ffff99857fd1ae10 0000000000000000 ffff99857fd1ae10 ffff99857fd1ae10 : ndis!ndisMInvokeDriverUnload+0x67 ffff828247299480 fffff8037b21d88c : ffff99857fd1ae10 000000000000000a ffff828247299640 ffffce08b9b68bd0 : ndis!ndisMUnloadEx+0x94 ffff8282472994e0 fffff8037b1027a6 : ffff99857fd1af60 0000000000000000 fffff8037b22ec01 ffff99857fd1ae10 : nt!IopUnloadDriver+0x224 ffff828247299610 fffff8037ac8a00b : ffff99857fe86c30 0000348339d17aa0 0000000000000200 000000000000000a : nt!PnpUnloadAttachedDriver+0xa6 ffff828247299660 fffff8037b102672 : ffff99857fe86c30 ffffffff00000000 0000000000000000 fffff8037b6504e0 : nt!PnpRemoveLockedDeviceNode+0x247 ffff8282472996c0 fffff8037b1023d4 : ffff99857fe86c30 ffff828247299740 ffff99857eb19e00 0000000000000000 : nt!PnpDeleteLockedDeviceNode+0x52 ffff828247299700 fffff8037b1c8e41 : ffff99857f930e00 0000000000000002 ffff9985841d3910 0000000000000000 : nt!PnpDeleteLockedDeviceNodes+0xc8 ffff828247299780 fffff8037b1c8d69 : 0000000000000000 ffff828247299810 ffff99857f930e00 0000000000000000 : nt!PipRemoveDevicesInRelationList+0x8d ffff8282472997d0 fffff8037b1c8bbc : ffff9985841d3910 ffff99857f930e00 0000000000000001 0000000000000007 : nt!PnpDelayedRemoveWorker+0x119 ffff828247299820 fffff8037ad7a915 : 0000000000000007 0000000000000000 0000000000000000 ffffce08b812d700 : nt!PnpChainDereferenceComplete+0xf4 ffff828247299850 fffff8037b10121d : ffff99858e3c9820 ffff828247299929 0000000000000003 0000000000000001 : nt!PnpIsChainDereferenced+0xad ffff8282472998b0 fffff8037b0836f9 : ffff8282472999f0 ffff99857f0ea500 ffff828247299a00 ffffce0800000008 : nt!PnpProcessQueryRemoveAndEject+0x2b1 ffff828247299990 fffff8037b0886a6 : ffffce08ab8d6bb0 ffffce08b6aad1f0 fffff8037b088300 0000000000000000 : nt!PnpProcessTargetDeviceEvent+0x109 ffff8282472999c0 fffff8037acda38a : ffff9985700b9490 ffff9985700b9490 fffff8037b0883d0 ffff9985703dc040 : nt!PnpDeviceEventWorker+0x2d6 ffff828247299a40 fffff8037ac7be75 : ffff9985703dc040 ffff9985700b6040 ffff9985703dc040 0000000000000000 : nt!ExpWorkerThread+0x1ba ffff828247299bf0 fffff8037ae1a3a8 : fffff8037821e180 ffff9985703dc040 fffff8037ac7be20 0000000000000000 : nt!PspSystemThreadStartup+0x55 ffff828247299c40 0000000000000000 : ffff82824729a000 ffff828247294000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28 STACK_COMMAND: .thread 0xffff9985703dc040 ; kb SYMBOL_NAME: raspppoe!RasPppoeCleanup+66 MODULE_NAME: raspppoe IMAGE_NAME: ### raspppoe.sys IMAGE_VERSION: 10.0.20262.1000 BUCKET_ID_FUNC_OFFSET: 66 FAILURE_BUCKET_ID: 0x9F_4_STACKPTR_ERROR_raspppoe!RasPppoeCleanup OS_VERSION: 10.0.20262.1 BUILDLAB_STR: fe_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {e8a0a9d6-853d-87f9-e9c5-bfbb7a1b79a9} Followup: MachineOwner"

Koesters commented 3 years ago

I started getting this error after the latest Windows fast ring build got installed overnight. Build 20262.fe_release.201113-1436 EDIT: Another reboot seems to have fixed it.

what way to fixed it? please clear it.

For me the reboot fixes it only once, then I can't cleanly reboot or shutdown. After the BSOD dump collection reboot it works again and so on.

salahtobok commented 3 years ago

Try this fix : https://windowsreport.com/no-more-endpoints-available-from-endpoint-mapper-windows-10/

xiaods commented 3 years ago

Try this fix : https://windowsreport.com/no-more-endpoints-available-from-endpoint-mapper-windows-10/

your sharing link doesn't useful. it seems relative to ICS service.

cjatoba commented 3 years ago

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

mojodevops commented 3 years ago

Env: 版本 Windows 10 企业版 版本号 21H1 安装日期 ‎2021/‎6/‎26 操作系统内部版本 19043.1083 体验 Windows Feature Experience Pack 120.2212.3530.0

Problem: 终结点映射器中没有更多的终结点可用。 There are no more endpoints available from the endpoint mapper.

When use WSL 2, i got this error, and found it was related to windows ICS service which displayed as Internet Connection Sharing(ICS) and named SharedAccess in services.msc. Recently, my machine installed KB5004945 and rebooted, the service was disappeared. Before that, i had the ICS service. Another PC of mine has the service and WSL 2 works well.

xiaods commented 3 years ago

Env: 版本 Windows 10 企业版 版本号 21H1 安装日期 ‎2021/‎6/‎26 操作系统内部版本 19043.1083 体验 Windows Feature Experience Pack 120.2212.3530.0

Problem: 终结点映射器中没有更多的终结点可用。 There are no more endpoints available from the endpoint mapper.

When use WSL 2, i got this error, and found it was related to windows ICS service which displayed as Internet Connection Sharing(ICS) and named SharedAccess in services.msc. On my machine, the service was disappeared. Recently, installed KB5004945.

安装了KB5004945，就能解决显示SharedAccess吗？我这也没有这个服务

mojodevops commented 3 years ago

Env: 版本 Windows 10 企业版 版本号 21H1 安装日期 ‎2021/‎6/‎26 操作系统内部版本 19043.1083 体验 Windows Feature Experience Pack 120.2212.3530.0 Problem: 终结点映射器中没有更多的终结点可用。 There are no more endpoints available from the endpoint mapper. When use WSL 2, i got this error, and found it was related to windows ICS service which displayed as Internet Connection Sharing(ICS) and named SharedAccess in services.msc. On my machine, the service was disappeared. Recently, installed KB5004945.

安装了KB5004945，就能解决显示SharedAccess吗？我这也没有这个服务

Recently, my machine installed KB5004945 and rebooted, the service was disappeared. Before that, i had the ICS service. Another PC of mine has the service and WSL 2 works well.

最近安装过补丁并重启后，ICS消失了，WSL 2也挂了，之前有，WSL 2也正常工作。不确定是否是补丁导致的。 WSL 1不受影响。

blueegg commented 1 year ago

I have fixed this problem by install docker desktop first.

SkippityPaps commented 5 months ago

Fixed it .. uninstalled Windows Subsystem for Linux and Virtual Hypervisor Platform restart then reinstall them then restart .. it worked after

doesnt work

RobertDiebels commented 2 months ago

Same issue here. Upgraded to Windows 11 then everything got bricked.

kemege commented 1 month ago

Windows 11 here, I've been using Windows 11 with Docker Desktop, and after KB5042353, KB5015447, and KB5041592 were automatically installed, Docker Desktop no longer works, and running wsl -d docker-desktop gives the error as in the title of this issue.

It turns out that the HNS service on my machine is set as "Disabled", re-enabling and starting that service resolves the problem.