-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command to uninstall WSL failed 0x80073CFA #11676
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
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 View similar issuesPlease 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! Open similar issues:
Closed similar issues:
|
________________________________
发件人: github-actions[bot] ***@***.***>
发送时间: 2024年6月10日 19:36
收件人: microsoft/WSL ***@***.***>
抄送: 多bug的啸天犬 ***@***.***>; Author ***@***.***>
主题: Re: [microsoft/WSL] Command to uninstall WSL failed 0x80073CFA (Issue #11676)
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 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<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 ***@***.******@***.***> 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!
Open similar issues:
* WslRegisterDistribution failed with error: 0x80070002 Error: 0x80070002 (#10099)<#10099>, similarity score: 0.72
Closed similar issues:
* WSL uninstall error (#7256)<#7256>, similarity score: 0.75
* Installing Windows Subsystem for Linux Error (#11430)<#11430>, similarity score: 0.75
* WSL 2 update error 0x80070643, WSL 2 cannot be deleted (#7287)<#7287>, similarity score: 0.75
* 0x800701bc错误 (#7949)<#7949>, similarity score: 0.73
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
―
Reply to this email directly, view it on GitHub<#11676 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A46364G5H4ZEY2UH3UAMJ7LZGWFT3AVCNFSM6AAAAABJCDXVVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJYGEYDIOBRGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Diagnostic information
|
/emailed-logs
…________________________________
发件人: github-actions[bot] ***@***.***>
发送时间: 2024年6月11日 21:37
收件人: microsoft/WSL ***@***.***>
抄送: 多bug的啸天犬 ***@***.***>; Author ***@***.***>
主题: Re: [microsoft/WSL] Command to uninstall WSL failed 0x80073CFA (Issue #11676)
Diagnostic information
Found '/question', adding tag 'question'
Found '/feature', adding tag 'feature'
Found '/emailed-logs', adding tag 'emailed-logs'
―
Reply to this email directly, view it on GitHub<#11676 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A46364EXAIGNBDB4MHFISWLZG34TDAVCNFSM6AAAAABJCDXVVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRQG44TCNJQGE>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Diagnostic information
|
|
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
|
This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue. Thank you! |
Windows Version
Windows 11 Pro for Workstations 24H2 26100.712
WSL Version
2.15.0
Are you using WSL 1 or WSL 2?
Kernel Version
Unable to install kernel
Distro Version
Unable to install distribution
Other Software
No response
Repro Steps
————————————————————————————————————————
I tried the msixbundle package installation because of the catastrophic failure of the wsl installation error report.
but reported an error The application installation failed with the error message: Deployment of package MicrosoftCorporationII.WindowsSubsystemForLinux_2.1.5.0_x64__8wekyb3d8bbwe has been prevented because the supplied package has the same identifier as the installed package, but not the same content. Please increase the version number of the package to be installed, or remove the old package for each user on the system and install this package again. (0x80073cfb)
So, I tried to turn off “Windows subsystems for linux” in the “Enable or disable windows features” panel, and it still wouldn't install, with the same error as above.
I tried uninstalling again from the command line and got the error 0x80073CFA.
Expected Behavior
Uninstalled successfully
Actual Behavior
Error “0x80073CFA”.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: