Blue
Blue
Thank you for reporting this @SailorMax. That could be caused by AV / custom security software. Do you have anything that could intercept / affect the connection from WSL ?...
Thank you for reporting this @milkshakeuk. This is most likely caused by a regression in 2.5.7. This will be fixed in the next release. See #12999
Fixed in [2.5.8](https://github.com/microsoft/WSL/releases/tag/2.5.8)
Thank you for reporting this @tanmay-veer. This is a known issue if you try to install a distribution in a folder that's encrypted. Is the `C:\Users\\AppData\Local\Microsoft\WindowsApps` folder encrypted on your...
Thank you @crramirez. I created #13080 to fix this issue. Tagging @DHowett so he can fix this from the Terminal side.
Fixed in [2.6.0](https://github.com/microsoft/WSL/releases/tag/2.6.0)
What's the default users configured in your distro ? If that user doesn't have access to the mount point, that can explain this error.
@cowwoc: This is unfortunately a known issue, because the 'Windows' part of wsl.exe outputs unicode bytes by default. If you want to read utf8 from WSL, you can do: ```...
@cowwoc: That's how wsl.exe originally worked, so other programs (like docker, vscode, ...) have a taken a dependency on it, which is why we can't easily change it. `WSL_UTF8` is...
Thank you for reporting this @W1M0R. WSL doesn't set `noexec` on that mount, so I wonder if this is caused by something else. Do you see the same issue if...