-
Notifications
You must be signed in to change notification settings - Fork 859
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
Access is denied after doing wsl --update #8055
Comments
Hello! I think I know what is happening with this issue but could you please submit logs so I can confirm? This might be a session 0 issue which we want to add support for in Store WSL. /logs |
Hello! Could you please provide more logs to help us better diagnose your issue? You can find instructions on how to attach logs here, please make sure to post the link to the Feedback Hub item in this chat so we can see it. Thank you! |
@prajaybasu - can you share more specific repro steps? Running wsl.exe with zero arguments should never return an error about WslRegisterDistribution. |
My bad, edited the logs @owenschupp While regular WSL works fine. I realized now that it might be related to me changing some permissions of the |
Dear sir/madam, This thread problem has re-appeared again via the latest WSL. WSL version: 1.1.7.0 |
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Version
Microsoft Windows [Version 10.0.22543.1000]
WSL version: 0.51.3.0 (WSL Preview from Store)
WSL Version
Kernel Version
5.10.60.1
Distro Version
Ubuntu from store. Manually upgraded to 21.10 but it's not relevant since
wsl.exe
also fails.Other Software
No response
Repro Steps
wsl --update
or by installing it through StoreExpected Behavior
The wsl command and
ubuntu
command run as expectedActual Behavior
The
wsl
command andubuntu
commands fail with this error:I had to uninstall the Windows store version of WSL to get wsl running normally again. The issue doesn't happen until I restart after installing it.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: