Guys help, I've contacted ms support multiple times and none of the agents have been able to solve the issue.
so, I have Windows Subsystem for Linux (WSL) with Ubuntu installed. yesterday, i tried to install docker, and it was kind of a mess, so i just uninstalled it in every way possible and cleaned all its leftovers, but i also noticed something weird, since yesterday (i dont know if the issue appeared before that, i only noticed it yesterday), the "wsl" command doesnt work!
proman@----:~$ wsl
Command 'wsl' not found, but can be installed with:
sudo apt install wsl
heres my latest attempt
Currently, my WSL/ubuntu shell doesn't even work because of a troubleshooting step that an agent did, where they opened a folder named "CanonicalGroupLimited" (at the path %userprofile%\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu_79rhkp1fndgsc) with some stuff after it and set the read-only checkbox (i dont remember if they did this to the whole folder or to a subfolder) to true (it was true for only some subfolders, but they made it completely true). Which probably means we need to manually change every single folder's readonly settings or recreate the folder somehow.
Here's what it currently says if i open wsl from the ubuntu app:
Error code: Wsl/Service/CreateInstance/E_ACCESSDENIED
Access is denied.
Error code: Wsl/Service/CreateInstance/E_ACCESSDENIED
Access is denied.
Error code: Wsl/Service/CreateInstance/E_ACCESSDENIED
Press any key to continue...
And here's what it says when I open it from the Windows Subsystem for Linux app:
Access is denied.
Error code: Wsl/Service/CreateInstance/E_ACCESSDENIED
Press any key to continue...
Both are the same message, except that the ubuntu app repeats it.
If you need any more details please let me know, otherwise, please help as now I'm completely unable to use WSL
Note: I've been so frustrated that i reinstalled wsl and ubuntu (just as a last try) before posting this question, and it now runs normally, but now we're back at square one: the 'wsl' command is not found
This does help though as now we know that my installation of docker wasn't the problem, does anyone know how i can fix it?