-
Notifications
You must be signed in to change notification settings - Fork 838
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
WSL error without UAC mode #10757
Comments
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:
You can give me feedback by thumbs upping or thumbs downing this comment. |
/logs |
WslLogs-2023-11-15_21-07-39.zip Executed commands:
|
Same here. Windows asked to reboot for update yesterday at evening, today vscode and Docker Desktop failed to connect to WSL. Versions are the same with @Zetanova:
Other WSL commands also does not work:
This is what Docker Desktop says: Here are the logs, i tried to open Windows Terminal with Ubuntu profile WslLogs-2023-11-16_09-59-00.zip Hope it will be fixed ASAP becauase it blocks my work. BTW, is there any safe way to backup distro data, reinstall wsl and restore the distro without using WSL's |
Exactly the same here. Windows update, reboot and |
@quallrum open a console in UAC mode and use wsl and open docker desktop in UAC mode "Run as Administror" this solves the problem with the work pause for now. Distros need only the vhdx disk files and can be imported in place with the |
@Zetanova @radoslawkoziol thanks a lot, running as admin worked for both WSL and Docker Desktop. VS Code also managed to connect to WSL and open the project when running as admin. Regarding updates: i found that these three updates have been installed yesterday (15.11.2023):
Maybe the issue is caused by them, but i was unable to check that. "Delete" option does not appear by right click on Servicing Stack, and both KB updates are installed back after deleting and rebooting. Deleting them without rebooting doesn't help, the error remains. |
@quallrum wsl 2.0.9 got installed over win updates. |
In case anyone needs this - seem like the bug is fixed in WSL 2.0.11 - https://github.com/microsoft/WSL/releases/tag/2.0.11 P.S. I've installed that version using msi installer from the link above. In my case |
Indeed this issue if fixed with 2.0.11. Closing. |
Windows Version
Windows version: 10.0.19045.3693
WSL Version
2.0.9.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
No response
Other Software
Docker Desktop 4.25.1
Repro Steps
execute some cli comman
wsl --status
orwsl
in no administrative privileges (no UAC)Expected Behavior
execution like before the windows update to 2.0.9
Actual Behavior
wsl terminates install with:
Element not found.
Error code: Wsl/ERROR_NOT_FOUND
Diagnostic Logs
none, can't see any differences between UAC mode and none UAC mode in procmon
No windows events logs or
collect-wsl-logs.ps1
wsl is working in UAC mode without issues.
Docker-desktop does only start in UAC mode.
The text was updated successfully, but these errors were encountered: