WSL: Can't start WSL1 or 2 instances since 18970 - Remote Procedure Call Failed
-
Your Windows build number: (Type
verat a Windows Command Prompt) 10.0.18970.1005 -
What you’re doing and what’s happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)
Can’t start existing WSL - new WSL shows same error upon trying to create a new user - regardless of DISTRO.
C:\Users\jbari>wsl --list
Windows Subsystem for Linux Distributions:
Ubuntu-18.04 (Default)
Ubuntu1804_v1
C:\>wsl
The remote procedure call failed.
C:\>wsl -d Ubuntu1804_v1 -u root
The remote procedure call failed.
C:\>bash
The remote procedure call failed.
- What’s wrong / what should be happening instead:
Should start up! Been using my v1 (because I had vmware workstation installed) since WSL was a thing.
- Strace of the failing command, if applicable: (If
some_commandis failing, then runstrace -o some_command.strace -f some_command some_args, and link the contents ofsome_command.stracein a gist here).
Can’t do an strace if I can’t get into the distro 😃
- For WSL launch issues, please collect detailed logs.
All 3 logs stay empty 😦
Reverting to an earlier build worked - but the update happened again overnight since I forgot to pause. Now it won’t back down again 😦 So now I can’t use WSL at all.
I’ve tried removing everything, removing the feature, adding it back in, and even removed VMWare workstation and ALL VPNs except my Fortinet client (need that one right now) so that WSL can do v2 if it wants - Hyper-V machines can run fine with full network, so no issues there.
Event logs show:
Faulting application name: svchost.exe_LxssManager, version: 10.0.18970.1001, time stamp: 0x992e0685
Faulting module name: ucrtbase.dll, version: 10.0.18970.1001, time stamp: 0xafa25d02
Exception code: 0xc0000409
Fault offset: 0x00000000000714ae
Faulting process id: 0x5fc8
Faulting application start time: 0x01d564e01a2d28c7
Faulting application path: C:\WINDOWS\system32\svchost.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 2494190c-fadc-4d38-ae5c-59b3df5f838c
Faulting package full name:
Faulting package-relative application ID:
each time the WSL or BASH command is run…so there is a crash with svchost. sfc /scannow is clean dism check also clean.
really stuck here - help!?! I really need WSL back 😃
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 36 (8 by maintainers)
hi my wsl is broken Microsoft Windows [Version 10.0.19042.508]
Installing, this may take a few minutes… WslRegisterDistribution failed with error: 0x800706be Error: 0x800706be The remote procedure call failed.
Press any key to continue…
I m try to uninstall linux wsl and reinstall. try start e stop wuauserv and crpto… not works
I was in a hurry, I had to reinstall windows 10 pro.
@benhillis The fix is partially effective. Now WSL will run which is great. But DNS is broken. The “dreaded” Temporary failure in name resolution. error is back.
It seems that the symlink /etc/resolv.conf–>…/run/systemd/resolve/stub-resolv.conf is no longer appropriate. Deleted the symlink and created manually /etc/resolv.conf with single line:
nameserver 8.8.8.8
line and DNS works again.
Essentially a fast fail coming safe buffer copy library and a variable length struct. The code was fine but the library was being overprotective. Fix is inbound.
Sure i’ll add svchost.exe to the regkeys and try and capture…hang on