microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.26k stars 812 forks source link

The WSL can't start after reset #12059

Open sakurayz opened 1 day ago

sakurayz commented 1 day ago

Windows Version

Windows 10.0.19044.4894

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

Kernel Version

5.15.153.1-2

Distro Version

Kali Linux 1.13.1.0

Other Software

No response

Repro Steps

open Windows Settings -> Apps -> select WSL -> Advanced options -> Reset

Expected Behavior

The first time start, the system will initialize and create a new user.

Actual Behavior

The WSL can't start after reset, and display the following error: Processing fstab with mount -a failed. Failed to mount C:\, see dmesg for more details. Failed to mount D:\, see dmesg for more details.

<3>WSL (7) ERROR: CreateProcessEntryCommon:334: getpwuid(0) failed 2 <3>WSL (7) ERROR: CreateProcessEntryCommon:505: execvpe /bin/sh failed 2 <3>WSL (7) ERROR: CreateProcessEntryCommon:508: Create process not expected to return ### Diagnostic Logs _No response_
github-actions[bot] commented 1 day ago

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs Download and execute [collect-wsl-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-wsl-logs.ps1) in an **administrative powershell prompt**: ``` Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1 ``` The script will output the path of the log file once done. If this is a networking issue, please use [collect-networking-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

sakurayz commented 2 hours ago

I'm not using the wsl --install command to install a Linux distro because the network is throttled. I installed offline using powershell. Add-AppxProvisionedPackage -Online -PackagePath KaliLinux_1.13.1.0.AppxBundle -SkipLicense

I found a compromise solution. wsl --unregister, then start wsl