Error 0x80070003 unsolved after trying all solutions

[LaysonShen]

Windows Version

Microsoft Windows [版本 10.0.22631.3374]

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.146.1-2

Distro Version

Ubuntu

Other Software

No response

Repro Steps

1. wsl -l -o
2. wsl --install Ubuntu

Expected Behavior

Steps to set username and passwd

Actual Behavior

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070003
Error: 0x80070003 ???????????

Press any key to continue...

Diagnostic Logs

WslLogs-2024-04-03_14-21-45.zip
attached is the log

[github-actions]

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:

• WslRegisterDistribution failed with error: 0x80070002 (#10660), similarity score: 0.86
• Failed to install Ubuntu - WslRegisterDistribution failed with error: 0x80040307 Error: 0x80040307 (null) (#8561), similarity score: 0.83
• WSL not installing Linux distro and giving error code > 0x80070003 (#8780), similarity score: 0.82
• Error: 0x80070057 The parameter is incorrect (#10287), similarity score: 0.81
• WSL error 0x8007023e (#9784), similarity score: 0.81

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

Diagnostic information

Detected appx version: 2.1.5.0

[LaysonShen]

I have tried every means to solve it, but just like what he met mentioned in #11019 ,it didnt work!

[LaysonShen]

According to #11019 , he solved this issue by reinstalling windows. But how to solve this issue without reinstalling?

[OneBlue]

@LaysonShen: Looking at the logs it might be because the ubuntu app is in a weird state. Does repairing / reinstalling the app help ?

[LaysonShen]

Thank you for your reply. I have reinstalled Ubuntu for several times, but it still didnt work. Moreover, other linux subsystem apps couldnt work neither. 在 2024-04-05 07:21:10，Blue ***@***.***> 写道： @LaysonShen: Looking at the logs it might be because the ubuntu app is in a weird state. Does repairing / reinstalling the app help ? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[OneBlue]

Thank you @LaysonShen.

Let's try something else. Can you capture a TDD trace of ubuntu.exe ?
You can find instructions on how to do that in section 12)

[LaysonShen]

Thanks @OneBlue ! I have followed the instructions. However, I have to admit my failure while recording wslservice.exe and the warning info has been shown above.
Then I turned to record ubuntu.exe and this time I successfully record everything helpful.
ubuntu01.zip

[github-actions]

Failed to parse logs. Unexpected file: ubuntu01.run
The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Found no WSL traces in the logs

[OneBlue]

Thank you @LaysonShen. Did you capture ubuntu.exe's state from its startup ? Looking at the TDD trace, the trace starts when ubuntu.exe is already exiting so unfortunately it doesn't contain the repro information.

[divisa-developer]

I also have ran into this problem, I opened my own issue but haven't received response #11553 if there is anything that could be provided to help solve this I would like to contribute since I can't reinstall OS at the moment or something like that

[LaysonShen]

I tried what Blue has told me to capture the log of the subsystem but in vain when filtering sessions. I have to give it up LOL 在 2024-05-06 22:34:04，divisa-developer ***@***.***> 写道： I also have ran into this problem, I opened my own issue but haven't received response #11553 if there is anything that could be provided to help solve this I would like to contribute since I can't reinstall OS at the moment or something like that — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[divisa-developer]

I tried what Blue has told me to capture the log of the subsystem but in vain when filtering sessions. I have to give it up LOL 在 2024-05-06 22:34:04，divisa-developer @.> 写道： I also have ran into this problem, I opened my own issue but haven't received response #11553 if there is anything that could be provided to help solve this I would like to contribute since I can't reinstall OS at the moment or something like that — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

I'm sorry to hear that. If it's worth anything I managed to pin down my problem to a permission issue on the installation of drivers for the Hyper-V devices used by the Virtual Machine Platform, a company wide policy suddenly dissalowed installation of drivers and this messed the Hyper-V devices, after asking the sys admin to modify the policy I could boot up distributions again without issue. I noticed this beacuse in my device manager I found 3 Unkown Devices under the category Other Devices, when I tried to update their drivers it gave a message pointing to the permission issue.

I noticed your error message is a bit different than mine but it's worth a try.

[LaysonShen]

I ran into this error while using my own PC. Wish you good luck. 在 2024-05-06 23:13:37，divisa-developer ***@***.***> 写道： I tried what Blue has told me to capture the log of the subsystem but in vain when filtering sessions. I have to give it up LOL 在 2024-05-06 22:34:04，divisa-developer @.> 写道： I also have ran into this problem, I opened my own issue but haven't received response #11553 if there is anything that could be provided to help solve this I would like to contribute since I can't reinstall OS at the moment or something like that — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.> I'm sorry to hear that. If it's worth anything I managed to pin down my problem to a permission issue in the installation of drivers for the Hyper-V devices used by the Virtual Machine Platform, a company wide policy suddenly dissalowed installation of drivers and this messed the Hyper-V devices, after asking the sys admin to modify the policy I could boot up distributions again without issue. I noticed this beacuse in my device manager I found 3 Unkown Devices under the category others, when I tried to update their drivers it gave a message pointing to the permission issue. I noticed your error message is a bit different than mine but it's worth a try. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>