WSL 2 will not start after installing KB4571756

[sean-physna]

Environment

Windows build number: 10.0.19042.0
Your Distribution version: Ubuntu 18.04
Whether the issue is on WSL 2 and/or WSL 1: WSL 2

Steps to reproduce

I don't have a full picture if this is something specific to my machine, but here goes...

1. Install KB4571756 via Windows updates
2. Reboot (per Windows Update instructions)
3. Attempt to start WSL
4. Receive the message "The remote procedure call failed." with no further information.

I uninstalled KB4571756 and I was able to start WSL as expected. To verify reproduction, I re-installed the update, and the issue reproduced easily.

WSL logs:
Feedback Hub Issue: https://aka.ms/AA9n435

It appears there's a failure in trying to talk to the LxssManager service. When run with strace via Git Bash:

$ strace wsl -d Ubuntu
The remote procedure call failed.
--- Process 16028 created
--- Process 16028 loaded C:\Windows\System32\ntdll.dll at 00007ffc1b450000
--- Process 16028 loaded C:\Windows\System32\kernel32.dll at 00007ffc19e60000
--- Process 16028 loaded C:\Windows\System32\KernelBase.dll at 00007ffc18e00000
--- Process 16028 loaded C:\Windows\System32\ucrtbase.dll at 00007ffc19250000
--- Process 16028 thread 16068 created
--- Process 16028 loaded C:\Windows\System32\SHCore.dll at 00007ffc1b2c0000
--- Process 16028 loaded C:\Windows\System32\msvcrt.dll at 00007ffc1b370000
--- Process 16028 loaded C:\Windows\System32\combase.dll at 00007ffc19b00000
--- Process 16028 loaded C:\Windows\System32\rpcrt4.dll at 00007ffc1aaf0000
--- Process 16028 thread 16188 created
--- Process 16028 thread 12708 created
--- Process 16028 loaded C:\Windows\System32\ws2_32.dll at 00007ffc1acd0000
--- Process 16028 loaded C:\Windows\System32\kernel.appcore.dll at 00007ffc17440000
--- Process 16028 loaded C:\Windows\System32\bcryptprimitives.dll at 00007ffc19120000
--- Process 16028 loaded C:\Windows\System32\sechost.dll at 00007ffc1ada0000
--- Process 16028 loaded C:\Windows\System32\clbcatq.dll at 00007ffc1a8f0000
--- Process 16028 thread 1176 created
--- Process 16028 thread 9708 created
--- Process 16028 thread 11952 created
--- Process 16028 loaded C:\Windows\System32\lxss\LxssManagerProxyStub.dll at 00007ffbf5110000
--- Process 16028, exception e06d7363 at 00007ffc18e23e49
--- Process 16028 unloaded DLL at 00007ffbf5110000
--- Process 16028, exception e06d7363 at 00007ffc18e23e49
--- Process 16028 thread 9708 exited with status 0xffffffff
--- Process 16028 thread 11952 exited with status 0xffffffff
--- Process 16028 thread 16188 exited with status 0xffffffff
--- Process 16028 thread 12708 exited with status 0xffffffff
--- Process 16028 thread 1176 exited with status 0xffffffff
--- Process 16028 thread 16068 exited with status 0xffffffff
--- Process 16028 exited with status 0xffffffff

In the Application Event Log, this event is emitted while starting WSL:

Faulting application name: vmwp.exe, version: 10.0.19041.488, time stamp: 0xfc760123
Faulting module name: KERNELBASE.dll, version: 10.0.19041.488, time stamp: 0x5b4a3325
Exception code: 0xc0000409
Fault offset: 0x000000000010b3cc
Faulting process id: 0x242c
Faulting application start time: 0x01d686e6dac064f6
Faulting application path: C:\Windows\System32\vmwp.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: c5dd148a-69bd-4ce1-8ef8-ff91167eb314
Faulting package full name: 
Faulting package-relative application ID: 

Expected behavior

WSL starts up, and my shell is launched.

Actual behavior

Only shown a The remote procedure call failed. message, and WSL cannot continue.

[therealkenc]

Please collect WSL logs and post the backlink to the feedback item here.

[geoffwellman]

Getting the same issue here after KB4571756 update.

[cpbotha]

Same issue on my setup, which obviously also breaks Docker Desktop with the WSL2 backend.

Uninstalling KB4571756.

I'm happy this has already been reported!

[corehello]

Same issue here with 10.0.19402.487, and after uninstall KB4571756, it back to work.

[AboveBill]

Same issue here. And unistalling KB4571756 didn't correct the issue for me

[divanikus]

Same issue here. Both Debian and Docker aren't starting anymore.

[ManzDev]

Same issue here. Uninstall KB4571756 fix problem and works again.

[zjsyj]

Same issue here Uninstall KB571756 fix problme and works again
windows version: 10.0.19402.487

[sean-physna]

Please collect WSL logs and post the backlink to the feedback item here.

Ah, forgot the link. Sorry, @therealkenc. It's here: https://aka.ms/AA9n435

[coldKingdom]

Same here, but in 20211: https://aka.ms/AA9n5a4

[Brian-Perkins]

@coldKingdom on that build you may be running into #5768.

[coldKingdom]

@coldKingdom on that build you may be running into #5768.

Thanks! But not at the moment, but maybe in the future ;)

[cpbotha]

@alexpaluzzi's work-around in #5880 (comment) has been fixing the post-update WSL2 breakage, without having to uninstall the update, for a growing number of users.

[stevefan1999-personal]

0xC0000409

STATUS_STACK_BUFFER_OVERRUN

The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

My speculation is that the Windows 10 stack protection is triggered

[SolomonCM]

I was receiving a "no more endpoints available from the endpoint mapper" error from wsl2 after KB4571756 was installed. But, I found a solution to getting WSL2 back up and running again. WITH the update still installed. Maybe this fix will work for you as well. just run windows setup to perform a repair install (in-place upgrade) and make sure the dynamic updates option remains enabled. windows setup will install the update during setup, and WSL2 should work afterwards, assuming there are no other issues. just running windows setup and doing a repair install without installing any updates does not seem to be enough, as the issues will return once KB4571756 gets installed.

[cperrin88]

I have a smiliar Problem but I only get the message "Fehler: 0xffffffff"

https://aka.ms/AA9pfko

[rosalinadev]

I'm also getting The remote procedure call failed. here.
Logs

[craigloewen-msft]

A fix for this has been put in with KB4577063, which released today to users on the Release Preview channel on 20H2.

Can any folks from here please try installing this KB and verifying that it resolved this issue for them?

[PGScully]

Installed this morning, and WSL2 works again :-)

[frankdavidcorona]

Please update the system: https://blogs.windows.com/windows-insider/2020/09/22/announcing-windows-10-insider-preview-build-19042-541-20h2/

[rosalinadev]

I can confirm that build 20226 on the Dev Channel fixed this issue for me.

[andressltz]

To fix, install this update KB4577063 (Windows 10 Build 19041.546) launched 10/01/2020, this issue has fixed in this update.

[sean-physna]

Confirmed - after installing that update on the Release Preview Channel, I could once again spin up WSL. Thanks for the hard work and fix!