-
Notifications
You must be signed in to change notification settings - Fork 816
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
WSL2-Error: A connection attempt failed on Windows 19555.1001 #4860
Comments
Same problem here. All the WSL1 instances are working. |
i got this bug, i am using ubuntu 18.04 distro and i cant seem to start wsl2 instance |
Hi, +1, VSCode can't established connection.
|
Hi, For me, uninstalled / re-install openssh-server on the linux host fix the connection issue. cf. https://docs.microsoft.com/fr-fr/windows/wsl/troubleshooting |
Thanks, we are debugging this internally - trying to figure out why only some users are hitting this. |
i was hitting the same issue with my v2 distro then i successfully converted it back to v1. I can now access the distro. Took about an hour to convert down but at least it's a viable workaround until the issue is resolved. PS C:\Users\brian> wsl --list -v
|
Sorry, but this is absolutely no workaround. There are obvious reasons why we use v2 and not v1. |
I'm not sure why the down vote on my comment. I should made myself clear in that post I'm speaking for myself and not in any official capacity from Microsoft. I was trying to be helpful to the community to folks who need to have their wsl distros up and functional. v2 is vastly better than v1. We all love v2 but if it's a matter between up but limping along versus being down then I'll take being up while the issue is being worked on. |
There's really some strategic solution needed here regarding Windows 10 Updates and especially WSL. What I mean is, yes, we opted for the Fast Ring and we know what risks we are taking as Beta-Testers. But WSL2 has become a crucial part of our work environment. So please, for the sake of our work and time, can you guys at MS be more careful with such updates. We really love WSL, and are looking forward to all the new features you're going to provide us with. And most importantly, we are truly thankful for that.🤘 |
Since the title already says "WSL2-Error..." there's really no need to suggest a workaround for converting to v1. It's not about which one is better. There are features that v1 can do but v2 can't, and vice versa. Depending on these features and based on our needs, we have distros running as v1 or v2, simultaneously. |
For folks who can get into their WSL 2 shell on 19555, but are experiencing the "VS Code Remote - WSL" problem mentioned above (looks like screencap), you can work-around by using "VS Code Remote SSH". |
quick questions: I know the team is debugging, but I got some time this error when playing around with the kernel 🤔 |
I've already reverted Windows back to the previous version. It's the official WSL-Ubuntu downloaded from the Ubuntu-Website, nothing custom and also no custom kernel here. |
@kobenauf - The roll back feature works very well and is actually quite quick. |
We were able to debug what the issue is here and are pushing the fix. This issue triggers if you have a somewhat a long %PATH%, so one potential workaround (until a new build comes out with the fix) would be to do some "spring cleaning" on your %PATH% variable to make it shorter. |
By %PATH% variable you mean the user defined one within Windows? |
@ad-on-is - Correct. |
@benhillis thanks for saying that about rolling back. I've never actually done that on Win10 and was afraid it would corrupt my system. (That happened to many, many, ... many years ago.) And you're right, it was pretty quick and it fixed the problem. Thanks! |
same issue on 19555.1001 |
Is the new build going to come out in next few days or is it going to be a week+? Just want to figure out whether to roll back or just wait |
reduced my windows $PATH length to 458 characters, WSL2 path length 637 and wsl2 started but vscode cant connect to server. same error as others #4860 (comment) adding startup output below as text. [2020-02-01 12:06:06.597] Resolving wsl+Ubuntu, resolveAttempt: 1
[2020-02-01 12:06:06.648] Starting VS Code Server inside WSL (Ubuntu)
[2020-02-01 12:06:06.648] Extension version: 0.41.7, Windows build: 19555. Multi distro support: available. WSL path support: enabled
[2020-02-01 12:06:06.795] Probing if server is already installed: C:\WINDOWS\System32\wsl.exe -d Ubuntu -e sh -c "[ -d ~/.vscode-server/bin/26076a4de974ead31f97692a0d32f90d735645c0 ] && printf found || ([ -f /etc/alpine-release ] && printf alpine-; uname -m)"
[2020-02-01 12:06:16.880] Unable to detect if server is already installed: Error: Command failed: C:\WINDOWS\System32\wsl.exe -d Ubuntu -e sh -c "[ -d ~/.vscode-server/bin/26076a4de974ead31f97692a0d32f90d735645c0 ] && printf found || ([ -f /etc/alpine-release ] && printf alpine-; uname -m)"
[2020-02-01 12:06:16.880] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
[2020-02-01 12:06:16.880] Launching C:\WINDOWS\System32\wsl.exe -d Ubuntu sh -c '"$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" 26076a4de974ead31f97692a0d32f90d735645c0 stable .vscode-server 0 ' in c:\Users\USER\.vscode\extensions\ms-vscode-remote.remote-wsl-0.41.7
[2020-02-01 12:06:26.953] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
[2020-02-01 12:06:26.953] VS Code Server for WSL closed unexpectedly.
[2020-02-01 12:06:26.953] For help with startup problems, go to
[2020-02-01 12:06:26.953] https://code.visualstudio.com/docs/remote/troubleshooting#_wsl-tips
[2020-02-01 12:06:26.965] WSL Daemon exited with code 0 |
Did NOT fix for me, was working fine until I shutdown WSL2 and tried to restart it for other things, I'm running build 19569. |
On Build 19559.1000 and WSL2 complained to start, but upgrading to 19577.1000 fixed that :-) |
No Problem anymore with WSL2 since 19582 |
Same issue on build 19564: I'm running build 19564 and the following commands work for me. |
Having this issue with Arch, Windows ver 19624. |
How can I make WSL automatically shut down if the error pops up again? |
@arakno nice catch! Some strange behavior occurs when a vs code instance with a remoted connected project from wsl was opened. After @arakno 's hint of opening a new "clean" window from vs code with no open remote connection, suddenly the Maybe the WSL and VS Code Team can investigate this strange behavior, somewhat blocks it. @benhillis |
I also had the issue that one ubunut 20.04 distro would not start. I just executed
|
I can confirm that this solution worked for me too thanks!!! |
this worked for me wsl -d Debian |
Yeah guys, after installing VSCode daemon in WSL (by running
helped |
Ubuntu 20.04 in WSL2 on Windows 10 Pro for Workstations V20H2
|
Unfortunately none of these worked for me. I got this issue right after using diskpart to compact / reduce file disk since I was running out of disk space and my wsl Debian installation had a 10GB useless file so I deleted it and closed wsl but that didn't help, so I ran diskpart. The disk was successfully compacted after attaching in read-only mode, then I detached and tried to run wsl and got this. I've tried wsl --shutdown, it didn't help. I also tried reattaching drive with diskpart, but then running wsl gave me an error that the disk was already being used by a different application :/ |
Hi, checking in because I do not see any resolution and the linked issue has been locked. Are there any known solutions to restarting/reconnecting at this time? |
I fixed mine by moving windows app then searched for ubuntu |
wsl --shutdown
wsl worked for me |
For me this issue is resolved by starting LxssManager service :--
Now, open windows powershell as administrator and type below commands If you find state as "Stopped" for your linux distro (ie; ubuntu-18.04, ubuntu 20.04, etc) then type below command PS C:\WINDOWS\system32> wsl -d For example: This will help to start your linux distro. Please reach out me if facing any issue on below mail id |
After an VSC update in WSL2 Ubuntu 22.04 distro, WSL2 started to fail and showed me this error. I coudn't be able to fix it. So I unistalled and reinstalled Ubuntu 22.04 in WSL2. It worked again, but I lost all my configuration. |
wsl --shutdown |
I am able to reproduce this error with WSL2 and Ubuntu 20.04: |
Same problem using IntelliJ+Git on projects inside WSL2. (also running: ssh-agent, Docker) Happens around once or twice a week. workaround: restart WSL2: |
After figuring out what is happen I got the solution as follows
|
After updating to Windows 19555 I get the following error, when starting WSL:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Update
I wanted to try this workaround on a fresh Alpine, #4371 (comment) but neither
/bin
nor/sbin
were symlinks.The text was updated successfully, but these errors were encountered: