Search results
9 maj 2019 · I've set up WSL (Windows Subsystem for Linux) on my Windows 10 to utilize Bash. I've created a Linux user, installed the latest updates and upgrades, and I know how to access the Windows files through /mnt/c/Users etc. When I try to create a new file on my desktop, it denies permission: rupert@DESKTOP-GT4APR9:/mnt/c/Users/zolta/OneDrive/Desktop
17 maj 2018 · You can't modify the permissions of files on Windows's filesystem using chmod on Bash on Ubuntu on Windows. You'll have to copy the private key to your WSL home directory (~) and do it there. Some discussion here: https://github.com/Microsoft/WSL/issues/81
28 gru 2021 · This page details how Linux file permissions are interpreted across the Windows Subsystem for Linux, especially when accessing resources inside of Windows on the NT file system. This documentation assumes a basic understanding of the Linux file system permissions structure and the umask command.
10 mar 2022 · Yesterday I was able to copy files from Windows to my WSL machine using \\WSL$\home\user\proj. I could also open new files (all from my Windows Explorer). Today, however, I was trying to do same but I got error about needing permission, "Access Denied", and I can't find the reason for this.
24 mar 2019 · The fix has two pieces: fixing how WSL mounts Windows drives and then fixing the permissions for newly created files. Fixing WSL Mount Permissions. The short version is to add this section to your WSL instance’s /etc/wsl.conf (the file probably does not exist, just create it): [automount] enabled = true options = "metadata,umask=22,fmask=11"
21 sie 2020 · I am using a WSL, ubuntu on windows 10 and I want to set permissions like below but I am receiving an error. Why? How do I fix it? ubuntu-user@LAPTOP:~$ chmod 400 .ssh/MyKey.pem chmod: changing permissions of '.ssh/MyKey.pem': Operation not permitted
16 maj 2020 · Try running the shell as a standard user (don't use "run as administrator", ensure that "administrator" is not in the window name). There's an open bug report for this with several workarounds (including the above): https://github.com/microsoft/WSL/issues/4920
