Closed smallprogram closed 1 week ago
Hi I'm an AI powered bot that finds similar issues based off the issue title.
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. Thank you!
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
/logs please
Hello! Could you please provide more logs to help us better diagnose your issue?
To collect WSL logs, download and execute 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 scipt will output the path of the log file once done.
Once completed please upload the output files to this Github issue.
Click here for more info on logging
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.
Thank you!
Hello! Could you please provide more logs to help us better diagnose your issue?
To collect WSL logs, download and execute 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 scipt will output the path of the log file once done.
Once completed please upload the output files to this Github issue.
Click here for more info on logging
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.
Thank you!
WSL Log updated
/logs please
Wsl log is update
Have you solved yet? I ran into the same problem and worse more I cannot start my docker
Have you solved yet? I ran into the same problem and worse more I cannot start my docker
I solved the problem by reinstalling Windows 11, but this problem also occurs on newly installed Windows 11. I don't know how to solve the problem without reinstalling the system.
Nope.If the only solution is to reinstall windows, I have to give up wsl LOL
在 2024-04-03 16:23:55,zhusir @.***> 写道:
Have you solved yet? I ran into the same problem and worse more I cannot start my docker I solved the problem by reinstalling Windows 11, but this problem also occurs on newly installed Windows 11. I don't know how to solve the problem without reinstalling the system. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>
LOL
How is this not solved yet this is ridiculous
Yep, and the only solution for me is to install an Ubuntu somewhere on my SSD XD
在 2024-05-26 11:29:43,Ronewa @.***> 写道:
LOL How is this not solved yet this is ridiculous — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>
After many tests, I finally found that the problem was with my computer hardware, which was a CPU failure. The Intel 13900ks I bought last year ran unstable this year, which caused WSL to report an error. I changed to a new CPU via Intel and the problem was solved. However, this does not rule out the possibility of operating system errors. At present, the problem has been solved by replacing the CPU and reinstalling the system.
Closing since the issue is resolved.
Windows Version
Microsoft Windows [Version 10.0.22631.3007]
WSL Version
2.0.9.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
Ubuntu,Ubuntu22.04.3 LTS,Ubuntu22.04.6 LTS
Other Software
Visual Studio 2022 17.8.3 Visual Studio code 1.85.1
Repro Steps
Expected Behavior
I hope this can be fixed and allow me to use WSL normally
Actual Behavior
I tried the following solutions, none of which worked:
wsl --update
,The command is executed normally, but the problem is not solved ❌C:\
. After checking, the default path is originallyC:\
. Didn't solve the problem ❌chkdsk /f
to detect the disk without any problems❌netsh winsock reset
to reset the network, useless❌SFC /scannow
to check system integrity. No problems were found and the problem was not solved.❌Diagnostic Logs
WslLogs-2024-01-17_16-56-32.zip