WSL: WSL won't start after Windows Update 18950

  • Your Windows build number: Microsoft Windows [Version 10.0.18950.1000]

  • What you’re doing and what’s happening:

  • I try to start WSL2 via wsl ~ -d DistroName
  • I get 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.
  • I shutdown WSL using wsl --shutdown
  • I try to start the distro again using wsl ~ -d DistroName
  • I still get 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.
  • I shutdown WSL again
  • I install a fresh copy via wsl --import DistroName2 <install-location> <rootfs.tar.gz> --version 2
  • I try to start WSL in the new install via wsl -d DistroName2
  • Again, I get 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.

This happened after Windows Updated to 18950, (from 18945)

Also, the processes vmwp.exe and vmmem show up in the task manager and do not go away till wsl --shutdown is executed.

  • What’s wrong / what should be happening instead: WSL console should appear.

  • For WSL launch issues, please collect detailed logs.

wsl-logs.zip

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 7
  • Comments: 49 (6 by maintainers)

Commits related to this issue

Most upvoted comments

Workaround that ended up working for me (use at your own risk, but no issues so far):

  • start from a wsl 1 container (change version if needed with wsl --set-version $yourdistro 1)
  • wsl -d $yourdistro -u root
  • from inside the distro:
    • cd /
    • ls -Alh: take a look at bin and sbin
    • if bin is a symlink, remove it: rm bin. Same for sbin
  • get out of the distro and convert it to v2 (wsl --set-version $yourdistro 2)
  • wsl -d $yourdistro -u root -e /usr/bin/bash
  • from inside the distro:
    • cd /
    • if /bin was a symlink:
      • mv bin/wslpath usr/bin/
      • rmdir bin
      • mv usr/bin bin
      • ln -s /bin usr/bin
    • if /sbin was a symlink:
      • mv sbin/mount.drvfs usr/sbin/
      • rmdir sbin
      • mv usr/sbin sbin
      • ln -s /sbin usr/sbin
  • get out of the distro
  • make sure it works:
    • wsl -t $yourdistro
    • wsl -d $yourdistro: hopefully this should work
    • get out of the distro, run wsl -l -v and make sure the version is indeed 2 for your distro
    • open explorer.exe and go to \\wsl$ to make sure the network mount point is there

Hope this will be useful to others 😃

This has been fixed and will be in an Insider build soon.

I just updated to 19555.1001 and am getting this with a WSL 2 Debian 10 installation:

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.

Prior to the update the WSL 2 environment worked fine. I have tried the suggestions in this issue to no effect.

Now that the problem has been identified, is it possible to share a workaround. This build is completely unusable with this. I’ve downgraded, but Windows update keeps trying to reupgrade me. I was hoping that it would get fixed in this week’s patch, but since it sounds like that won’t be happening, do you have any suggestions?

Hi, any idea when the Insider build will be released please ?

Alright, I just figured this one out… init fails to create “/bin” because it already exists as a sym-link to “/usr/bin”!!!

So this issue only occurs with a rootfs that is /usr-merged… which includes Kali-linux in the Microsoft Store. Not really sure why init is trying to create a /bin directory anyways, but this is going to need to be fixed by someone at Microsoft since init is closed-source code.

still not fixed for me on 18970

Is there a way to get any visibility as to what the WSL VM is doing? When errors like this happen you can’t see any of the console log or anything, you just see the equivalent of “It didn’t work /shrug”

“This has been fixed and will be in an Insider build soon.” As of 18956.1000 which I just installed, this is still not fixed… edition error

Same here on build 18956.

Can confirm fixed in 18970.

The time from us checking in the bug fix to the change being available inside of an Insiders build can vary, and is dependent on many different factors. In general, it’s around 3 to 6 weeks.

It looks like this issue is back in 19555 released today. I have opened a feedback ticket with some telemetry if you need it here: https://aka.ms/AA75u9m

Two releases ago localhost didn’t work, the previous release fixed that and seemed to work just fine.