-
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
Warning during installation via .msi installer #10692
Comments
Thank you for reporting this @adokitkat. Can you try to collect the MSI logs of an installation with this warnings ? You can do that via:
You might need to remove WSL for the warnings to show up again during installation. |
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-open it. Thank you! |
I'm experiencing this. WSL got bricked on its own and I can't even remove it from my system! |
What do you mean by you "can't remove it" ? What exact error do you see ? |
Idk, even uninstalling it and disabling the optional feature would still not work. Even if I uninstalled it, it would still seem like it was still installed. A chad in the comments for a similar issue advised to manually delete a registry key (i think it was wslService?) and after that it got fixed. |
I also uninstalled WSL and it is still there. Us telling you these things are what helps you guys and gals create the best product. That no one could ever beat. If you would quit avoiding actual problems. No one is perfect, don't have to act so sour. |
Windows Version
Microsoft Windows [Version 10.0.22621.2428]
WSL Version
2.0.6.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
No response
Other Software
No response
Repro Steps
Try to install latest pre-release version (2.0.6) via x64 .msi installer.
Expected Behavior
To not get any warning or error.
Actual Behavior
Get this warning message:
However it seems version 2.0.6 did install anyway.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: