WSL: "An existing connection was forcibly closed by the remote host." error is presented when launching any WSL 2 distro

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

  • What you’re doing and what’s happening: Trying to launch wsl.exe or bash throws an error message that states An existing connection was forcibly closed by the remote host.

    Microsoft Windows [Version 10.0.18917.1000]
    (c) 2019 Microsoft Corporation. All rights reserved.
    
    C:\Users\Steven>bash
    An existing connection was forcibly closed by the remote host.
    
    C:\Users\Steven>wsl
    An existing connection was forcibly closed by the remote host.
    
    C:\Users\Steven>

I’ve tried this with my converted Debian distro, as well as ArchWSL. I also tried to install Ubuntu but during setup after choosing my UNIX username the same error gets thrown.

  • What’s wrong / what should be happening instead: The distro should be launching normally and I should be presented with a bash shell.

Log files: logs.zip

Edit (9/26/19): It appears that the number of entries in a modified hosts.txt is what is causing this issue at the moment. More information here: https://github.com/microsoft/WSL/issues/4105#issuecomment-531385551

About this issue

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

Most upvoted comments

Thanks for filing. From the trace it looks like your instance is being terminated during creation. Does the following command work? If so can you give me the output? When you’re in this state, can you look in task manager and see if there is a vmmem process running?

wsl.exe -u root -e dmesg

Thanks!

Sorry to read that !

What I did before :

I deleted a lot of « unused » entries (more than 5000 😉 ) in /etc/hosts on windows side. All these entries were added by a lot of AV apps I used before switching to Kaspersky.

Then I’ve rebooted.

Here’s my /etc/wsl.conf :

[automount]
enabled = true
root = /mnt/
options = “metadata,umask=0,fmask=111”
mountFsTab = true

If it works for me after a lot of tests, there is no reason that it is not the case for others… I think that it is just a matter of configuration, not software. May be some old specific configs that block the launch of WSL2

De : Hugh notifications@github.com Envoyé : mardi 10 septembre 2019 12:50 À : microsoft/WSL WSL@noreply.github.com Cc : Christian Denat christian.denat@orange.fr; Comment comment@noreply.github.com Objet : Re: [microsoft/WSL] “An existing connection was forcibly closed by the remote host.” error is presented when launching any WSL 2 distro (#4105)

@Chris <Christian.bos@gmail.com mailto:Christian.bos@gmail.com > Glad, it worked for you. Alas but not for me…Neither Ubuntu nor openSUSE runs, even after a fresh install. I tried openSUSE for the first time but received the same slap in the face (more actually, openSUSE keeps retrying!)

On Tue, Sep 10, 2019 at 12:38 AM Christian Denat <notifications@github.com mailto:notifications@github.com > wrote:

Good news… It’s working 😉…

I’ve deployed 18975 but not really sure it’s the reason 😉 because I first tried first to set version 2 to one of my existing distro wsl --set-version DistroName 2 but got same error …

What I did then is to re enable WSL using Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux then re enable the VM Platform Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform

then restarted my computer …

And now it’s working !!! Ubuntu has been set to v2… So Nice !!! See shots attached ! [image: 2019-09-10 08_24_58-Window] https://user-images.githubusercontent.com/9724885/64589635-e2d22c00-d3a5-11e9-90aa-844e428f200c.png [image: 2019-09-10 08_10_01-Window] https://user-images.githubusercontent.com/9724885/64589636-e2d22c00-d3a5-11e9-9125-2d10b5bcce95.png [image: 2019-09-10 08_34_42-Window] https://user-images.githubusercontent.com/9724885/64589634-e2d22c00-d3a5-11e9-8d68-5ea42d5ed58b.png

PS : do not forget to export first your existing distro to be enable to import it later in case of crash …

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/microsoft/WSL/issues/4105?email_source=notifications https://github.com/microsoft/WSL/issues/4105?email_source=notifications&email_token=AAHE7PWOFRJ5UBADFPA2XJDQI46HTA5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6KAFBI#issuecomment-529793669 &email_token=AAHE7PWOFRJ5UBADFPA2XJDQI46HTA5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6KAFBI#issuecomment-529793669>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHE7PSAGCENZBS23YJ5NKTQI46HTANCNFSM4HXVMHEQ .

— You are receiving this because you commented. Reply to this email directly, https://github.com/microsoft/WSL/issues/4105?email_source=notifications&email_token=ACKGHVLZK7WZ6RE66RZUCLTQI53VBA5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6KVNLI#issuecomment-529880749 view it on GitHub, or https://github.com/notifications/unsubscribe-auth/ACKGHVONJCB23LL2EVGHEK3QI53VBANCNFSM4HXVMHEQ mute the thread. https://github.com/notifications/beacon/ACKGHVMQXCFFWBVB2EETIN3QI53VBA5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6KVNLI.gif

@andreluizgit - Unfortunately there are no WSL2 changes in 18932.

TNX for information hosts is the causion! DELETE hosts fix this.

I can confirm @benhillis that using the default HOSTS file as of %WinDir%\System32\drivers\etc (https://support.microsoft.com/en-us/help/972034/how-to-reset-the-hosts-file-back-to-the-default) has got WSL2 working for me.

Seems this is supported by others below too.

Background info: _My hosts file was an older version of https://raw.githubusercontent.com/EnergizedProtection/block/master/extensions/porn-lite/formats/hosts-ipv6.txt._

I guess one of the following is what kills WSL2:

127.0.0.1 localhost
127.0.0.1 localhost.localdomain
127.0.0.1 local
255.255.255.255 broadcasthost
::1 localhost
::1 ip6-localhost
::1 ip6-loopback
fe80::1%lo0 localhost
ff00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
0.0.0.0 0.0.0.0

Thanks @Skye19 and @chdenat for the idea. @steven-peralta since this is your issue, you might wanna take a look here.

Thanks for the information. I’ve since dropped out of receiving Insider builds and have reinstalled Windows 10 on my PC, but I believe I did have a custom hosts.txt file for ad-blocking before I did all of that.

I can confirm @benhillis that using the default HOSTS file as of %WinDir%\System32\drivers\etc (https://support.microsoft.com/en-us/help/972034/how-to-reset-the-hosts-file-back-to-the-default) has got WSL2 working for me.

Seems this is supported by others below too.

Background info: _My hosts file was an older version of https://raw.githubusercontent.com/EnergizedProtection/block/master/extensions/porn-lite/formats/hosts-ipv6.txt._

I guess one of the following is what kills WSL2:

127.0.0.1 localhost
127.0.0.1 localhost.localdomain
127.0.0.1 local
255.255.255.255 broadcasthost
::1 localhost
::1 ip6-localhost
::1 ip6-loopback
fe80::1%lo0 localhost
ff00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
0.0.0.0 0.0.0.0

Thanks @Skye19 and @chdenat for the idea. @steven-peralta since this is your issue, you might wanna take a look here.

I believe I have identified the issue! Fix will be in an upcoming insider build.

Awesome, I have a repro. I’ll get this fixed. Thanks to everybody for the help.

@laster https://github.com/laster—I, the grumpy, skeptical user that I am, can likewise confirm that restoring hosts to essentially empty works like a charm! I followed the directions that you linked to and a voila working Ubuntu!!! YAY double+ to you or whomever ☺👍👍

On Fri, Sep 13, 2019 at 2:47 PM Laster K. notifications@github.com wrote:

I can confirm @benhillis https://github.com/benhillis that using the default HOSTS file as of C:\windows\system32\drivers\etc\hosts ( https://support.microsoft.com/en-us/help/972034/how-to-reset-the-hosts-file-back-to-the-default) has got WSL2 working for me.

Background info: My hosts file was an older version of https://raw.githubusercontent.com/EnergizedProtection/block/master/extensions/porn-lite/formats/hosts-ipv6.txt https://raw.githubusercontent.com/EnergizedProtection/block/master/extensions/porn-lite/formats/hosts-ipv6.txt.

I guess one of the following is what kills WSL2:

127.0.0.1 localhost 127.0.0.1 localhost.localdomain 127.0.0.1 local 255.255.255.255 broadcasthost ::1 localhost ::1 ip6-localhost ::1 ip6-loopback fe80::1%lo0 localhost ff00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts 0.0.0.0 0.0.0.0

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/microsoft/WSL/issues/4105?email_source=notifications&email_token=AAHE7PSW3VOEA4XPOHFAQ43QJP34RA5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6WEZTY#issuecomment-531385551, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHE7PQDVCN2HO3PF4YWZXTQJP34RANCNFSM4HXVMHEQ .

Fixed in 18995.

So is it to say someone may be never able to use WSL 2?

The impression I got was that there was a fix, but it was a ways away. 18936 is at least the second update since then. If you are holding your breath, time to stop and rest for a while. I don’t think there are enough of us with broken *wsl *to force the issue so it is just a “wait and see situation”…

On Fri, Jul 12, 2019 at 10:05 PM Yu Shengnan notifications@github.com wrote:

Anyone knows when this issue will be fixed?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/microsoft/WSL/issues/4105?email_source=notifications&email_token=AAHE7PQWZMSWUUKCWHREM5LP7FIADA5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ3I37I#issuecomment-511086077, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHE7PTJ2AONY54RCH4HC4DP7FIADANCNFSM4HXVMHEQ .

Since it looks like a fix will be released in the near future, I will go ahead and close this issue.

@andreluizgit Unfortunately not.

I wonder if we are all “guilty” of messing with Hyper-V? I did when I attempted to go GUI with WSL. I was partially successful with Xming/XLaunch—eyeballs moving and one or two editors working. Failed when attempting more complicated apps. That said, I left it alone and didn’t think about it further. If this or something like this is a common factor that could be a major clue…

On Mon, Jun 17, 2019 at 7:15 PM Omri Gabay notifications@github.com wrote:

@OmriSama https://github.com/OmriSama - Thanks for the information. I’m still digging into this, likely something unique about your configuration that is not being handled correctly.

Is anybody internal to Microsoft hitting this issue? I have a private binary I can share with more instrumentation that should help me track this down.

Of course.

Do you know how we can configure Utility VMs/VMs launched through Virtual Machine Platform? Is it through Hyper-V manager or somewhere else?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/microsoft/WSL/issues/4105?email_source=notifications&email_token=AAHE7PXW5KHE5WM6BDXKZXTP3AZMRA5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX44BCQ#issuecomment-502907018, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHE7PXVPACJBTGXQUCLMQDP3AZMRANCNFSM4HXVMHEQ .

Would it be possible for somebody hitting the “An existing connection was forcibly closed by the remote host” issue to export your distribution and share the tar file? This will contain your entire root file system so if there is private information please send it to secure@microsoft.com.

  1. wsl.exe --export DistroName FileName.tar
  2. Zip FileName.tar
  3. Email to secure@microsoft.com, say it’s for benhill, or upload and send me a link.

Me too. Same build 18917 and Debian, I converted it to Wsl version 2 but the Appx can’t run after this convertion… Then I returned to Wsl version 1.

The issue can be the ext4.vhdx disk image that can’t be open from Appx (Debian or Ubuntu) with Wsl2, before the linux files could be open via explorer with Wsl1.

Windows Insider forum : https://answers.microsoft.com/en-us/insider/forum/all/an-existing-connection-was-forcibly-closed-by-the-remote-host

I dont know why, it seems restart solves everything 😆

Glad to have open the door 😉

inspired by someone else’s comment, I moved my current hosts file (over 800k in size) and replaced it with one that was empty. with no other changes, ubuntu is working fine now.

  • Gary.

Despite the hype about WSL 18980 is equally dead on arrival. While I will continue to check, I no longer believe that *any *fix is in the works. My thought is that it is much easier to make vague promises than actual fixes. Shame really, but without incentive (i.e. numbers) why would they bother to fix an obscure bug. While it is clear that they have broken a few machines it is not at all clear that anyone gives a damn. Pretty much the traditional Microsoft approach…

On Tue, Sep 10, 2019 at 11:23 AM Christian Denat notifications@github.com wrote:

Sorry to read that !

What I did before :

I deleted a lot of « unused » entries (more than 5000 😉 ) in /etc/hosts on windows side. All these entries were added by a lot of AV apps I used before switching to Kaspersky.

Then I’ve rebooted.

Here’s my /etc/wsl.conf :

[automount] enabled = true root = /mnt/ options = “metadata,umask=0,fmask=111” mountFsTab = true

If it works for me after a lot of tests, there is no reason that it is not the case for others… I think that it is just a matter of configuration, not software. May be some old specific configs that block the launch of WSL2

De : Hugh notifications@github.com Envoyé : mardi 10 septembre 2019 12:50 À : microsoft/WSL WSL@noreply.github.com Cc : Christian Denat christian.denat@orange.fr; Comment < comment@noreply.github.com> Objet : Re: [microsoft/WSL] “An existing connection was forcibly closed by the remote host.” error is presented when launching any WSL 2 distro (#4105)

@Chris <Christian.bos@gmail.com mailto:Christian.bos@gmail.com > Glad, it worked for you. Alas but not for me…Neither Ubuntu nor openSUSE runs, even after a fresh install. I tried openSUSE for the first time but received the same slap in the face (more actually, openSUSE keeps retrying!)

On Tue, Sep 10, 2019 at 12:38 AM Christian Denat <notifications@github.com mailto:notifications@github.com > wrote:

Good news… It’s working 😉…

I’ve deployed 18975 but not really sure it’s the reason 😉 because I first tried first to set version 2 to one of my existing distro wsl --set-version DistroName 2 but got same error …

What I did then is to re enable WSL using Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux then re enable the VM Platform Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform

then restarted my computer …

And now it’s working !!! Ubuntu has been set to v2… So Nice !!! See shots attached ! [image: 2019-09-10 08_24_58-Window] < https://user-images.githubusercontent.com/9724885/64589635-e2d22c00-d3a5-11e9-90aa-844e428f200c.png

[image: 2019-09-10 08_10_01-Window] < https://user-images.githubusercontent.com/9724885/64589636-e2d22c00-d3a5-11e9-9125-2d10b5bcce95.png

[image: 2019-09-10 08_34_42-Window] < https://user-images.githubusercontent.com/9724885/64589634-e2d22c00-d3a5-11e9-8d68-5ea42d5ed58b.png

PS : do not forget to export first your existing distro to be enable to import it later in case of crash …

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/microsoft/WSL/issues/4105?email_source=notifications < https://github.com/microsoft/WSL/issues/4105?email_source=notifications&email_token=AAHE7PWOFRJ5UBADFPA2XJDQI46HTA5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6KAFBI#issuecomment-529793669> &email_token=AAHE7PWOFRJ5UBADFPA2XJDQI46HTA5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6KAFBI#issuecomment-529793669>, or mute the thread < https://github.com/notifications/unsubscribe-auth/AAHE7PSAGCENZBS23YJ5NKTQI46HTANCNFSM4HXVMHEQ

.

— You are receiving this because you commented. Reply to this email directly, < https://github.com/microsoft/WSL/issues/4105?email_source=notifications&email_token=ACKGHVLZK7WZ6RE66RZUCLTQI53VBA5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6KVNLI#issuecomment-529880749> view it on GitHub, or < https://github.com/notifications/unsubscribe-auth/ACKGHVONJCB23LL2EVGHEK3QI53VBANCNFSM4HXVMHEQ> mute the thread. < https://github.com/notifications/beacon/ACKGHVMQXCFFWBVB2EETIN3QI53VBA5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6KVNLI.gif>

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/microsoft/WSL/issues/4105?email_source=notifications&email_token=AAHE7PWEULXDPQUG6KZQZR3QI7J23A5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6L3XZQ#issuecomment-530037734, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHE7PQLWUHO3V3G3BATY7LQI7J23ANCNFSM4HXVMHEQ .

Good news… It’s working 😉…

I’ve deployed 18975 but not really sure it’s the reason 😉 because I first tried first to set version 2 to one of my existing distro wsl --set-version DistroName 2 but got same error …

What I did then is to re enable WSL using Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux then re enable the VM Platform Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform

then restarted my computer …

And now it’s working !!! Ubuntu has been set to v2… So Nice !!! See shots attached ! 2019-09-10 08_24_58-Window 2019-09-10 08_10_01-Window 2019-09-10 08_34_42-Window

PS : do not forget to export first your existing distro to be enable to import it later in case of crash …

C:>systeminfo

Host Name: BIGIRON OS Name: Microsoft Windows 10 Pro Insider Preview OS Version: 10.0.18970 N/A Build 18970 OS Manufacturer: Microsoft Corporation OS Configuration: Standalone Workstation OS Build Type: Multiprocessor Free Registered Owner: hsmyers Registered Organization: Product ID: 00330-80000-00000-AA040 Original Install Date: 30.08.19, 07:59:10 System Boot Time: 30.08.19, 07:37:28 System Manufacturer: To be filled by O.E.M. System Model: To be filled by O.E.M. System Type: x64-based PC Processor(s): 1 Processor(s) Installed. [01]: AMD64 Family 21 Model 2 Stepping 0 AuthenticAMD ~3500 Mhz BIOS Version: American Megatrends Inc. 2601, 24.03.15 Windows Directory: C:\WINDOWS System Directory: C:\WINDOWS\system32 Boot Device: \Device\HarddiskVolume2 System Locale: en-us;English (United States) Input Locale: en-us;English (United States) Time Zone: (UTC-07:00) Mountain Time (US & Canada) Total Physical Memory: 32,668 MB Available Physical Memory: 22,108 MB Virtual Memory: Max Size: 65,436 MB Virtual Memory: Available: 49,446 MB Virtual Memory: In Use: 15,990 MB Page File Location(s): C:\pagefile.sys Domain: WORKGROUP Logon Server: \BIGIRON Hotfix(s): 3 Hotfix(s) Installed. [01]: KB4518975 [02]: KB4518978 [03]: KB4518974 Network Card(s): 3 NIC(s) Installed. [01]: ExpressVPN Tap Adapter Connection Name: Ethernet Status: Media disconnected [02]: Realtek PCIe GbE Family Controller Connection Name: Local Area Connection DHCP Enabled: Yes DHCP Server: 192.168.0.1 IP address(es) [01]: 192.168.0.3 [03]: Hyper-V Virtual Ethernet Adapter Connection Name: vEthernet (WSL) DHCP Enabled: No IP address(es) [01]: 172.20.128.1 [02]: fe80::38e7:738a:ce93:88f5 Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.

On Fri, Aug 30, 2019 at 3:17 PM onomatopellan notifications@github.com wrote:

@hsmyers https://github.com/hsmyers What’s your CPU model?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/microsoft/WSL/issues/4105?email_source=notifications&email_token=AAHE7PQGEZXZ65KRN3JDX6TQHGE6XA5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5SZ2KA#issuecomment-526753064, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHE7PRP3Z3AMTSQGMMVJHDQHGE6XANCNFSM4HXVMHEQ .

Between Admin and Operational, only Admin reports anything and they are all information bullets.

On Fri, Aug 30, 2019 at 12:40 PM onomatopellan notifications@github.com wrote:

But you have enabled “Virtual machine Platform” (which uses Hyper-V) feature. Otherwise WSL2 wouldn’t work.

Open Event Viewer and look for some error inside Applications and Services -> Microsoft -> Windows -> Hyper-V Worker

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/microsoft/WSL/issues/4105?email_source=notifications&email_token=AAHE7PWTYBZPUWEOM5CPNDTQHFSSLA5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5SOOTY#issuecomment-526706511, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHE7PXMHZPEKT2QFJK6KLTQHFSSLANCNFSM4HXVMHEQ .

Preview attachment lxcore_kernel.etl https://mail.google.com/mail/u/0?ui=2&ik=0b5ae2e802&attid=0.1&permmsgid=msg-a:r-2320754889435339887&th=16ce3867b99818e9&view=att&disp=safe&realattid=f_jzydo5yc0 https://mail.google.com/mail/u/0?ui=2&ik=0b5ae2e802&attid=0.1&permmsgid=msg-a:r-2320754889435339887&th=16ce3867b99818e9&view=att&disp=safe&realattid=f_jzydo5yc0 https://mail.google.com/mail/u/0?ui=2&ik=0b5ae2e802&attid=0.1&permmsgid=msg-a:r-2320754889435339887&th=16ce3867b99818e9&view=att&disp=safe&realattid=f_jzydo5yc0 https://mail.google.com/mail/u/0?ui=2&ik=0b5ae2e802&attid=0.1&permmsgid=msg-a:r-2320754889435339887&th=16ce3867b99818e9&view=att&disp=safe&realattid=f_jzydo5yc0Preview attachment lxcore_user.etl https://mail.google.com/mail/u/0?ui=2&ik=0b5ae2e802&attid=0.2&permmsgid=msg-a:r-2320754889435339887&th=16ce3867b99818e9&view=att&disp=safe&realattid=f_jzydo5zo2Preview attachment lxcore_service.etl https://mail.google.com/mail/u/0?ui=2&ik=0b5ae2e802&attid=0.3&permmsgid=msg-a:r-2320754889435339887&th=16ce3867b99818e9&view=att&disp=safe&realattid=f_jzydo5zm1 https://mail.google.com/mail/u/0?ui=2&ik=0b5ae2e802&attid=0.1&permmsgid=msg-a:r-2320754889435339887&th=16ce3867b99818e9&view=att&disp=safe&realattid=f_jzydo5yc0 lxcore_service.etl 40 KB https://mail.google.com/mail/u/0?ui=2&ik=0b5ae2e802&attid=0.3&permmsgid=msg-a:r-2320754889435339887&th=16ce3867b99818e9&view=att&disp=safe&realattid=f_jzydo5zm1 https://mail.google.com/mail/u/0?ui=2&ik=0b5ae2e802&attid=0.1&permmsgid=msg-a:r-2320754889435339887&th=16ce3867b99818e9&view=att&disp=safe&realattid=f_jzydo5yc0 lxcore_user.etl 16 KB https://mail.google.com/mail/u/0?ui=2&ik=0b5ae2e802&attid=0.2&permmsgid=msg-a:r-2320754889435339887&th=16ce3867b99818e9&view=att&disp=safe&realattid=f_jzydo5zo2 lxcore_kernel.etl 8 KB https://mail.google.com/mail/u/0?ui=2&ik=0b5ae2e802&attid=0.1&permmsgid=msg-a:r-2320754889435339887&th=16ce3867b99818e9&view=att&disp=safe&realattid=f_jzydo5yc0 note that my reply to Microsoft/wsl has three attachments I will forward same to ALL

On Fri, Aug 30, 2019 at 11:28 AM onomatopellan notifications@github.com wrote:

@hsmyers https://github.com/hsmyers drag and drop https://github.blog/2015-09-25-attach-files-to-comments/ the files in a browser.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/microsoft/WSL/issues/4105?email_source=notifications&email_token=AAHE7PRYHOHTDNE3VLTW4RLQHFKFHA5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5SI4SI#issuecomment-526683721, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHE7PRLH6LODHOPZJHNYKLQHFKFHANCNFSM4HXVMHEQ .

Here you go then

On Fri, Aug 30, 2019 at 11:12 AM Ben Hillis notifications@github.com wrote:

You can just post them here, there is not any private information in them.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/microsoft/WSL/issues/4105?email_source=notifications&email_token=AAHE7PTVR5SNAKELGHUPVE3QHFIJNA5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5SHVYQ#issuecomment-526678754, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHE7PRGLNRYKFJNJJEBHKTQHFIJNANCNFSM4HXVMHEQ .

18970 doesn’t work as well, I’m beginning to think there is no correction in the works…

On Mon, Aug 26, 2019 at 6:45 AM Jimmy Gaussen notifications@github.com wrote:

Still no movement with 18965

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/microsoft/WSL/issues/4105?email_source=notifications&email_token=AAHE7PQFB6BVQJNSAE6YW33QGPF7NA5CNFSM4HXVMHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5EIHAY#issuecomment-524845955, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHE7PVQBPNEW5CX3NCSXCTQGPF7NANCNFSM4HXVMHEQ .

Still no movement with 18965

@andreluizgit as …

I promise that I will stop posting off-topic issue … you guys from github are excellent, there’s no way Microsoft’s feedback-hub to become like github (there we have no feedback)? Thanks for answering.

@andreluizgit as @onomatopellan said we communicate that issues are being worked on with the ‘fixinbound’ tag. If more users post issues about the same problem we will mark them as duplicate and close them. Thank you for your feedback, I’d like to request that we keep the discussion on this thread just to the issue at hand.

@onomatopellan , you didn’understand … even with this Tag the users post the same problem/issue that is already fixed But it will release after new OS build

@andreluizgit That’s exactly what the “fixinbound” tag means. The issue in this thread is fixed and you will need to wait for the “fixedininsiderbuilds” tag. (normally 3-4 weeks)

That sounds great! Thanks. 😃 Any word on what was the problem? What is the root cause?

@OmriSama - Out of curiosity, if you can’t launch WSL2, how are you getting the dmesg output?

I can’t email my distro tarball because it’s 600+MB Also why can’t we see the VM in Hyper-V Manager?

Use mega.nz or something similar.

It’s not a traditional VM and it’s using a different platform (Virtual Machine Platform) which is the third? platform for Hyper-V virtualisation in Windows as you can see in Control Panel > Programs > Manage Optional Features. The other two are default Hyper-V (the one you see in the manager) and Hypervisor Platform (Android emulator uses this but doesn’t appear in manager too).

The problem is that the Appx (Ubuntu or Debian) can’t open this new VM (image disk ext4.vhdx) because the App was built to execute the root files with NT filesystem

more users with similar issues : https://github.com/microsoft/WSL/issues maybe would be good to suspend the release of wsl2 for this moment

I can’t email my distro tarball because it’s 600+MB

Also why can’t we see the VM in Hyper-V Manager?

Use mega.nz or something similar.

It’s not a traditional VM and it’s using a different platform (Virtual Machine Platform) which is the third? platform for Hyper-V virtualisation in Windows as you can see in Control Panel > Programs > Manage Optional Features. The other two are default Hyper-V (the one you see in the manager) and Hypervisor Platform (Android emulator uses this but doesn’t appear in manager too).

wsl --export creates a tar regardless if the distro is WSL1 or WSL2. What I suspect is there’s something in the root file system that /init does not like. The VM looks like it’s being created and the distro is able to be converted, but launching the distro fails.

He wants it in WSL2 format.

Then only the ext4.Vhdx image converted (after change to WSL2) would be need

Idk about you, but I’m experiencing it on a plain clean downloaded Ubuntu and Debian (and Kali) WSL instance so I’m not sure why it’s needed at all.

Would it be possible for somebody hitting the “An existing connection was forcibly closed by the remote host” issue to export your distribution"

Can be with WSL 1 actived or must be only wsl2 ? I can run “wsl.exe --export DistroName FileName.tar” with my Debian in WSL1 ? and Then send to you

I think he wants it in WSL2 format.

Thanks for filing. From the trace it looks like your instance is being terminated during creation. Does the following command work? If so can you give me the output? When you’re in this state, can you look in task manager and see if there is a vmmem process running?

wsl.exe -u root -e dmesg

Thanks!

Microsoft Windows [Version 10.0.18917.1000]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\Steven>wsl.exe -u root -e dmesg
An existing connection was forcibly closed by the remote host.

C:\Users\Steven>

This is what I see in task manager shortly after running that command image

The the first running vmmem process will stick around for a bit before disappearing, while the second one stays in its suspended state indefinitely

Thanks for filing. From the trace it looks like your instance is being terminated during creation. Does the following command work? If so can you give me the output? When you’re in this state, can you look in task manager and see if there is a vmmem process running?

wsl.exe -u root -e dmesg

Thanks!

That command doesn’t work; I’m still getting the original An existing connection was forcibly closed by the remote host. message, but there is heightened Vmmem activity when I call this for sure (I tried calling it repeatedly and noticed the spike).