WSL: WSL2 distro can't start: the remote procedure call failed (build 20211)
First of all, I’ve seen other issues similar to this one but none mentioned the error I get.
Environment
Windows build number: 20211
Your Distribution version: Ubuntu 20.04
Whether the issue is on WSL 2 and/or WSL 1: WSL2
wsl --status:
Default Distribution: Ubuntu
Default Version: 2
Windows Subsystem for Linux was last updated on 04/09/2020
WSL automatic updates are on.
Kernel version: 4.19.128
wsl -l -v:
NAME STATE VERSION
* Ubuntu Stopped 2
Alpine Stopped 2
Steps to reproduce
- Open
cmd - Run
wslorwsl -d <Distribution>(bothUbuntuandAlpinefail)
WSL logs: https://aka.ms/AA9l9ap
Expected behavior
The distribution should start.
Actual behavior
The wsl command fails with the error The remote procedure call failed.. Windows Terminal additionally reports process exited with code 4294967295 (0xffffffff, -1).
Also I don’t know if it’s connected, but pings wouldn’t work from inside WSL2 before this started happening, though dns resolution worked correctly Fixed this part using the first part of this solution.
More information
Things I’ve checked from other issues:
- I don’t have
KB4571756installed. - Services
LxssManagerandLxssManagerUser_871e1were stopped. After starting them and runningwsl, the same error happens and they go back to being stopped. - Stopping the Hyper-V service from Hyper-V Manager didn’t fix it, and neither did restarting it.
- Stopping the SharedAccess service only made it start again.
- Disabling and enabling WSL didn’t fix it either.
- Running powershell as admin and starting
wslfrom there got me the same error.
I haven’t tried:
- Rolling back to 20206, but I don’t want to if at all possible. Plus, if there’s an issue with 20211, I want to have it so that a fix can be tested in my machine.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 70
- Comments: 58 (3 by maintainers)
Fixed has been submitted and is on the way to Insider builds.
You can +1 the initial post, commenting +1 only introduces noise.
same problem with build 20215
This issue is fixed with build 20226 for WSL 2 + Ubuntu 20.04 distro. Thanks for the effort.
Thanks! Checked this. But it only allows rolling back to the previous installed build. In my case 20215. After this, the Get started button is disabled.
So the only way I see is a clean install, but I need my wsl files(
If anyone stumbles upon this page years later and has the same issue, simply kill all processes that start with “wsl” and try again.
Hope MS can fix it. I won’t losing my files. 20221,recovery can’t get started.
Not fixed in 20221 build
And also, WSL 2 AND 1 are broken, not only WSL 2 …
Ok, I got my files back from wsl, but it’s not the perfect solution. Just took the ext4.vhdx file here c:\Users<username>\AppData\Local\Packages\CanonicalGroupLimited.UbuntuonWindows_<junk>\LocalState
Stopped wsl on target pc. And then moved the file to that pc with ok build, found similar folder there and replaced original vhdx with the desired one. Wsl started normally. I have same ubuntu versions on both pc. Not sure if it is a required condition.
I can confirm that the fix will be available within the next couple of weeks. The fix is checked in and it needs to go through the regular process to head out to Windows Insiders. Thank you!
Can you tell me when the next build with this fix will be released? My previous build was accidentally deleted, can’t rollback 😢
Same here, using Ubuntu 20.04 LTS.
@efim-a-efim, tell me, please, do you have build 20211 (x64) and wsl 2?
Did you save the vmsynthnic.dll file that was used in the build 20206 and then register it in the build 20211?
And everything works?
Same here, solved by following this instructions
No. That update KB4571756 is a problem for people in build 19041 or 19042. This thread is for users that are running latest Windows 10 Insider Dev build which is build 20211 and has nothing to do with KB4571756.
What if I have
C:\Windows\System32\VmSynthNic.dllwith 389KB andC:\Windows.old\WINDOWS\System32\VmSynthNic.dllwith 398KB. Not missing, but changed.Microsoft has acknowledged that this is an error in KB4571756. See workaround on this thread in response by @alexpaluzzi. If you aren’t OCD like me and don’t clean up your disk every five hours you shodul be able to find an older copy of the file. Luckily I had one on another laptop,
@chdenat It won’t let you keep files. All you can do is a clean install. Already tried that 😕
the only workaround is to rollback 😦
@ThreshHNS . yesterday, I’ve asked to @craigloewen-msft , the WSL master @MSFT. Fix will be available in a new flight in a couple of week.
You should have the option Go back to the previous version of Windows 10 available: