-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Can't start WSL1 or 2 instances since 18970 - Remote Procedure Call Failed #4474
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Are there any Windows Error Reporting Service dumps? |
Hmm - where would I find that? edit: |
|
Sure i'll add svchost.exe to the regkeys and try and capture....hang on |
Can't get a crashdump to save my life with the regkeys set.... |
I did some digging and found where Waston crashes end up. I'm looking at some dumps now. Thanks! |
Awesome - let me know if you need anything else....I'll be watching this closely! |
Confirmed problem still there in 18975 :( |
I have resolved this issue, it is due to some bad assumptions about network state. Best course of action is to revert to the previous build if you are experiencing this issue. Fix is on the way. |
As stated before I can't back out anymore and 18980 didn't fix. If there is a complex method to fix please post it! Or - if it isn't possible to fix short of a nuke from orbit, I'll find time to do just that on my laptop. |
Would be nice to get an estimate of when this fix will go live. I got a big update the other day from MSFT but did not include fix for this issue. E:>ver Microsoft Windows [Version 10.0.18980.1] E:>wsl This is really a problem since I can't revert the Window update without basically nuking all the machines I have. |
@transmitterdan - Hard to give an exact date, but I hope next week. |
Last few days my WSL is broken too
|
Would love some insight as to the exact issue here. Its a black box for me. Thank you to whoever is working on fixing this! |
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. |
Those who facing this issue can you guys able to open hyper-v manager i think hyper-v is not working in the background |
Can able to run Hyper-v but no luck in running wsl2 |
Fixed in 18995. |
@benhillis 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. |
I'd like to chime in on this issue as well. Same failure mode as O.P. Cannot manually set LxssManager to start - will fail right out. Full text of failure: Windows build version: Microsoft Windows [Version 10.0.19030.1] WSL was working fine until this latest update on my system. |
same as @mmcgirr
I am on build 19541, version 2004. |
@Project-Magenta - Sounds like a different bug, could you please open a new issue? |
hi my wsl is broken Installing, this may take a few minutes... Press any key to continue... I m try to uninstall linux wsl and reinstall. I was in a hurry, I had to reinstall windows 10 pro. |
I also got problem with this after an update 2020-09-10. I uninstalled update KB4571756 and it started working for me again. |
It seems that KB4571756 mixed up with Windows 10 Insider Preview 20211.1000 (rs_prerelease)... |
I went into Windows Update -> View update history -> uninstall updates and then select the KB4571756 and uninstall it. Hope it helps. I'm not running Windows Insider Preview. Version 10.0.19041 Build 19041 |
Same problem with you guys, but i can't find KB4571756 update to uninstall. |
Maybe we need rollback to previous version? or just wait for another update~ |
Follow this solution, it worked for me after i installed the update: |
Oh, BTW, I'm running 20211 on Insider. |
It's another issue. Element Missing~re-register dll. |
Same issue on insider 20221 |
After I update to 10.0.19041.208,My wsl cannot start with error message: The remote RPC server was cancelled. I try to uninstall KB4571756,and install KB4577063, but still not work. At last,I revert to previous build and pause windows update.now wsl can work. |
Try to see if lxssmanager is running and if not then try to manually turn it on and change the service to start automatically. If it says access denied then run the following command in an elevated cmd promt: sc config LxssManager start=auto This fixed the issue for me. |
Uh oh!
There was an error while loading. Please reload this page.
Your Windows build number: (Type
ver
at 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.
Should start up! Been using my v1 (because I had vmware workstation installed) since WSL was a thing.
some_command
is failing, then runstrace -o some_command.strace -f some_command some_args
, and link the contents ofsome_command.strace
in a gist here).Can't do an strace if I can't get into the distro :)
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:
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 :)
The text was updated successfully, but these errors were encountered: