Skip to content
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

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

Closed
songjunjian opened this issue Sep 11, 2020 · 35 comments
Closed

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

songjunjian opened this issue Sep 11, 2020 · 35 comments

Comments

@songjunjian
Copy link

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,

@therealkenc
Copy link
Collaborator

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.

@therealkenc therealkenc 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 Sep 11, 2020
@zhenjun115
Copy link

same. can not start wsl

@sd9cf
Copy link

sd9cf commented Sep 11, 2020

same problem

@oska874
Copy link

oska874 commented Sep 11, 2020

same problem.

@davelowper
Copy link

davelowper commented Sep 11, 2020

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 : 

@oska874
Copy link

oska874 commented Sep 11, 2020

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...

@haosmos
Copy link

haosmos commented Sep 11, 2020

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.

@Fuzl
Copy link

Fuzl commented Sep 11, 2020

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.

@banyh
Copy link

banyh commented Sep 11, 2020

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

@xiaoqidun
Copy link

xiaoqidun_2020-09-12_01-04-40

same problem

@barrettg
Copy link

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

@mkontani
Copy link

mkontani commented Sep 11, 2020

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

@CJYLab
Copy link

CJYLab commented Sep 12, 2020

same +1

@zhenjun115
Copy link

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

@walkthetalk
Copy link

same +1

@QtacierP
Copy link

Same +1.

@phoenixjyb
Copy link

phoenixjyb commented Sep 12, 2020

same issue here

Further details to add:
Windows version: 20211 prerelease, 200904-1619.

Major Minor Build Revision


10 0 20211 0

WSL2 is enabled:

PS C:\WINDOWS\system32> wsl --list --verbose
NAME STATE VERSION

  • Debian Stopped 2
    Ubuntu-18.04 Stopped 2
    Ubuntu-20.04 Installing 2

When the error for remote procedure call pops out, the system event viewer logs an error for lxss manager.

@Pagliacii
Copy link

Same problem.

Windows version: Microsoft Windows [Version 10.0.20211.1000]
Distribution version:

~
❯ wsl -l -v
  NAME            STATE           VERSION
* Ubuntu-18.04    Stopped         1
  ArchLinux       Stopped         1

When I try to start via wsl or wsl -d xxx, it always claims The remote procedure call failed..

And I can see the error message like below in the event viewer:

Faulting application name: svchost.exe_LxssManager, version: 10.0.20211.1000, time stamp: 0xb0e7c44f
Faulting module name: ucrtbase.dll, version: 10.0.20211.1000, time stamp: 0xb4267ab9
Exception code: 0xc0000409
Fault offset: 0x000000000007c99e
Faulting process id: 0xd60
Faulting application start time: 0x01d688d74192e9d1
Faulting application path: C:\WINDOWS\system32\svchost.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 91956537-19c2-4d4b-bf01-476d58f2ad53
Faulting package full name: 
Faulting package-relative application ID: 

@Pagliacii
Copy link

BTW, I found that if I start the virtual machine in VirtualBox, it will cause a green screen of death. Hopefully, this can help for debugging.

@Mengkzhaoyun
Copy link

same +1

@lawsonsli
Copy link

lawsonsli commented Sep 12, 2020

same +1 .
How to roll back to build 20206?

@sashizaki
Copy link

sashizaki commented Sep 12, 2020

same +1
.wslconfig do not work...

@shakthifuture
Copy link

Same issue

1 similar comment
@zyazhb
Copy link

zyazhb commented Sep 13, 2020

Same issue

@shakthifuture
Copy link

I resolved the issue using https://askubuntu.com/questions/234856/unable-to-do-remote-desktop-using-xrdp

@CarbonPool
Copy link

CarbonPool commented Sep 13, 2020

BTW, I found that if I start the virtual machine in VirtualBox, it will cause a green screen of death. Hopefully, this can help for debugging.

The same problem, some of my Android emulators cannot be started, which will cause my computer to restart

@zergvszerg
Copy link

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

@gskm
Copy link

gskm commented Sep 14, 2020

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).

@xyjnradio
Copy link

same +1

1 similar comment
@phpdev-m
Copy link

same +1

@joesdu
Copy link

joesdu commented Sep 16, 2020

same +1

@ghost
Copy link

ghost commented Sep 16, 2020

same + 1

@benhillis
Copy link
Member

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

@microsoft microsoft locked as spam and limited conversation to collaborators Sep 16, 2020
@benhillis
Copy link
Member

Locking to cut down on +1 spam.

@therealkenc
Copy link
Collaborator

/fixed 20226

@ghost ghost closed this as completed Nov 11, 2020
@ghost ghost added fixedininsiderbuilds and removed fixinbound labels Nov 11, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests