search

microsoft / WSL

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

Error when trying to run the Ubuntu command prompt #12210

Open Analich opened 2 hours ago

Analich commented 2 hours ago

Windows Version

Microsoft Windows [Version 10.0.26100.2033]

WSL Version

2.3.24.0

Are you using WSL 1 or WSL 2?

Kernel Version

PS C:\Users\Chita > cat /proc/ cat version : It doesn't seem like that's the case. "C:\proc\version", since it doesn't work. line:1 sign:1 + cat /proc/version + ~~~~~ + Information about the category : the object was not found: (C:\proc\version:String) [Get-Content], ItemNotFoundException + Fully qualified error ID : Path not found,Microsoft.PowerShell.Teams.The GetContentCommand command

Distro Version

-

Other Software

No response

Repro Steps

C:\Users\Chita>wsl -l -v The Windows subsystem for Linux does not contain installed distributions.

Use 'wsl.exe --list --online' to view the list of available distributions. and 'wsl.exe --install ' to install.

Distributions can also be installed by visiting the Microsoft Store: https://aka.ms/wslstore Error code: Wsl/WSL_E_DEFAULT_DISTRO_NOT_FOUND

so I suggest you stock up on Ubuntu compatibility to plunge into the world of cybersecurity: Installation may take several minutes... WslRegisterDistribution fails with error: 0xc03a0014 Error: 0xc03a0014 ?? ?????? ????????? ????????? ???????????? ????? ??? ?????????? ?????.

Press any key to continue...

Expected Behavior

Stable operation of the Ubuntu command line

Actual Behavior

Image

Diagnostic Logs

No response

github-actions[bot] commented 2 hours 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.