Skip to content

can not start ubuntu-18.04 using wsl after update to 20211 #5902

Closed

Description

@songjunjian

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Your Distribution version: [On Debian or Ubuntu run `lsb_release -r` in WSL]
Whether the issue is on WSL 2 and/or WSL 1: [run `cat /proc/version` in WSL]

Steps to reproduce

WSL logs:

Expected behavior

Actual behavior

update the windows to Windows 10 Insider Preview 20211.1000 (rs_prerelease),
using window terminal , start ubuntu 18.04, failed, exit code : 4294967295,

Activity

  1. therealkenc commented on Sep 11, 2020

    @therealkenc

    Please collect WSL logs and post the backlink to the feedback item here. Also please identify any third-party networking software that has been installed on Windows.

  2. changed the title [-]can not start ubuntu-18.04 using wsl after update[/-] [+]can not start ubuntu-18.04 using wsl after update to 20211[/+] on Sep 11, 2020
  3. zhenjun115 commented on Sep 11, 2020

    @zhenjun115

    same. can not start wsl

  4. sd9cf commented on Sep 11, 2020

    @sd9cf

    same problem

  5. oska874 commented on Sep 11, 2020

    @oska874

    same problem.

  6. davelowper commented on Sep 11, 2020

    @davelowper

    same here (using debian 10)

    Nom de l’application défaillante svchost.exe_LxssManager, version : 10.0.20211.1000, horodatage : 0xb0e7c44f
    Nom du module défaillant : ucrtbase.dll, version : 10.0.20211.1000, horodatage : 0xb4267ab9
    Code d’exception : 0xc0000409
    Décalage d’erreur : 0x000000000007c99e
    ID du processus défaillant : 0x5290
    Heure de début de l’application défaillante : 0x01d6883718569d19
    Chemin d’accès de l’application défaillante : C:\WINDOWS\system32\svchost.exe
    Chemin d’accès du module défaillant: C:\WINDOWS\System32\ucrtbase.dll
    ID de rapport : 2f3503bb-9595-4416-80a1-ee6e4f883b1b
    Nom complet du package défaillant : 
    ID de l’application relative au package défaillant : 
    
  7. oska874 commented on Sep 11, 2020

    @oska874

    Can not install new linux too.

    When I try to install a new alpine,it shows:

    Temporary directory: C:\Users\leile\AppData\Local\Temp\wsl_Alpine_setup
    Downloading   : http://dl-cdn.alpinelinux.org/alpine/v3.11/releases/x86_64/alpine-minirootfs-3.11.4-x86_64.tar.gz
    To local file : install.tar.gz
    The current working directory is: C:\Users\leile\AppData\Local\Temp\wsl_Alpine_setup
    File successfully deleted
    Mime type available
    Begin download
    Cache filename available
    100% [====================]
    End download
    Downloaded OK
    Hash of file install.tar.gz is: 47210239fcdd9a1dca72238f13912187cbcf0898fda2d12d4b583781279791e0
    
    Verifying Hash: OK
    Installing, this may take a few minutes...
    WslRegisterDistribution failed with error: 0x80070005
    WslRegisterDistribution failed
    Error: 0x80070005 ?????
    
    Press any key to continue...
    
  8. haosmos commented on Sep 11, 2020

    @haosmos

    same problem (ubuntu-20.04, windows build 20211 x64):

    After starting wsl, the following message is displayed in the console:

    process exited with code 4294967295

    I tried the following solutions:

    ❯ netsh winsock reset
    
    Sucessfully reset the Winsock Catalog.
    You must restart the computer in order to complete the reset.
    

    After restarting the computer the problem was not solved - after starting wsl the same error is shown:

    process exited with code 4294967295

    DISM /online /disable-feature /featurename:VirtualMachinePlatform /norestart
    DISM /online /disable-feature /featurename:Microsoft-Windows-Subsystem-Linux /norestart
    

    Reboot, and then:

    DISM /online /enable-feature /featurename:VirtualMachinePlatform /norestart
    DISM /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /norestart
    

    After starting wsl, the same error is shown:

    process exited with code 4294967295

    Removed the Linux kernel (wsl_update_x64.msi) and reinstalled it. After starting wsl the same error is shown:

    process exited with code 4294967295

    When rolling back to the previous version of the build (20206) — wsl works as expected.

  9. Fuzl commented on Sep 11, 2020

    @Fuzl

    Hi, same problem here.
    Just to mention I don't have a checkpoint at build 20206 so I'm stuck and must leave the fast ring.

  10. banyh commented on Sep 11, 2020

    @banyh

    Same problem.
    Revert to build 20206 and Ubuntu 20.04 works again.

  11. xiaoqidun commented on Sep 11, 2020

    @xiaoqidun

    xiaoqidun_2020-09-12_01-04-40

    same problem
  12. barrettg commented on Sep 11, 2020

    @barrettg

    I had a similar problem in 20206 and fixed it by creating a .wslconfig file in my Windows user home directory and adding the following contents:

    [wsl2]
    swap=0
    
  13. mkontani commented on Sep 11, 2020

    @mkontani

    I got same problem, but after repeating signout/signin a few times, WSL (and Docker desktop) came to work as expected... 🤔

    PS C:\Users\mkontani> [System.Environment]::OSVersion.Version
    
    Major  Minor  Build  Revision
    -----  -----  -----  --------
    10     0      20211  0
    
    PS C:\Users\mkontani> wsl -l -v
      NAME                   STATE           VERSION
    * Ubuntu                 Running         2
      docker-desktop         Running         2
      docker-desktop-data    Running         2
    
    PS C:\Users\mkontani> wsl
    /mnt/c/Users/mkontani ᐅ cat /etc/os-release
    NAME="Ubuntu"
    VERSION="18.04.5 LTS (Bionic Beaver)"
    ID=ubuntu
    ID_LIKE=debian
    PRETTY_NAME="Ubuntu 18.04.5 LTS"
    VERSION_ID="18.04"
    HOME_URL="https://www.ubuntu.com/"
    SUPPORT_URL="https://help.ubuntu.com/"
    BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
    PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
    VERSION_CODENAME=bionic
    UBUNTU_CODENAME=bionic
    
  14. CJYLab commented on Sep 12, 2020

    @CJYLab

    same +1

  15. zhenjun115 commented on Sep 12, 2020

    @zhenjun115

    I had a similar problem in 20206 and fixed it by creating a .wslconfig file in my Windows user home directory and adding the following contents:

    [wsl2]
    swap=0
    

    not work

  16. 12 remaining items

  17. zergvszerg commented on Sep 14, 2020

    @zergvszerg

    Sathiamoorthy (@shakthifuture) Could you elaborate? Also, this thread is about wsl2 unable to launch, not about xrdp.

  18. gskm commented on Sep 14, 2020

    @gskm

    Same error, Ubuntu 18.04 (WSL1) after update Windows to build 20211 from 20206 won't start with error "remote procedure call failed", LxssManager service won't start with error 7034 (System Event).

  19. xyjnradio commented on Sep 16, 2020

    @xyjnradio

    same +1

  20. vesviet commented on Sep 16, 2020

    @vesviet

    same +1

  21. joesdu commented on Sep 16, 2020

    @joesdu

    same +1

  22. benhillis commented on Sep 16, 2020

    @benhillis
    Member

    If you are hitting this issue I suggest rolling back to the previous Insider build.

  23. locked as spam and limited conversation to collaborators on Sep 16, 2020
  24. benhillis commented on Sep 16, 2020

    @benhillis
    Member

    Locking to cut down on +1 spam.

  25. therealkenc commented on Nov 11, 2020

    @therealkenc

    /fixed 20226

  26. ghost closed this as completedon Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions