search

microsoft / WSL

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

WSL Install Ubuntu 0x80070003 #11019

Closed smallprogram closed 1 week ago

smallprogram commented 7 months ago

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

flowchart TD 
01[Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux]
02[Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform]
03[Restart Windows]
04[Download Ubuntu from Microsoft Store]
05[Download Ubuntu 22.04.3 LTS from Microsoft Store]
06[Download Ubuntu 22.04.6 LTS from Microsoft Store]
07[Install Ubuntu]
08[Install Ubuntu 22.04.3 LTS]
09[Install Ubuntu 22.04.6 LTS]
10[Report 0x80070003]

    01 --> 02
    02 --> 03
    03 --> 04
    03 --> 05
    03 --> 06
    04 --> 07
    05 --> 08
    06 --> 09
    07 --> 10
    08 --> 10
    09 --> 10

Expected Behavior

I hope this can be fixed and allow me to use WSL normally

Actual Behavior

image

I tried the following solutions, none of which worked:

  1. run wsl --update ，The command is executed normally, but the problem is not solved ❌
  2. Set the windows default storage path to C:\. After checking, the default path is originally C:\. Didn't solve the problem ❌
  3. I tried windows update, but it said there was no update.❌
  4. Modify the registry, HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\kernel\obcaseinsensitive, to 1, useless❌
  5. Delete the %USERPROFILE%.wslconfig file, but there is no .wslconfig file in the %USERPROFILE% directory on my computer. Useless❌
  6. Confirm whether the CPU virtualization function is enabled in the BIOS and confirm that it is enabled, but the problem is still not solved.❌
  7. Use chkdsk /f to detect the disk without any problems❌
  8. Use netsh winsock reset to reset the network, useless❌
  9. Use 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

github-actions[bot] commented 7 months 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!

Open similar issues:

Closed similar issues:

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

ghost commented 7 months ago

/logs please

smallprogram commented 7 months ago

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

smallprogram commented 7 months ago

/logs please

Wsl log is update

LaysonShen commented 4 months ago

Have you solved yet? I ran into the same problem and worse more I cannot start my docker

smallprogram commented 4 months ago

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.

LaysonShen commented 4 months ago

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: @.***>

BinaryErrol commented 3 months ago

LOL

How is this not solved yet this is ridiculous

LaysonShen commented 3 months ago

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: @.***>

smallprogram commented 2 months ago

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.

OneBlue commented 1 week ago

Closing since the issue is resolved.