![]() But in new register I get new error, its like 'no permission' (don't remember exactly). After it's deleted, you should have access to wsl in PowerShell and cmd and be able to reinstall the distro you deleted.įor me, it's only thing worked. If you can't delete it because it says it is open in System, restart and you should be able to delete it. Then I had located ext4.vhdx and deleted the folders in AppData that contained this file (Mine was Docker). Run wsl -list -verbose to get a list of distros.Type control userpasswords2 and click OK. Here’s how you can set your account to admin: Press Win + R to open Run. If you are able to run wsl -help and get information back, you should be able to do the following: Set Your Account to Administrator In most cases, the Access Denied errors can be fixed by making your user account the computer’s administrator. In a command prompt I was getting Access Denied when trying to run wsl, but was still able to run wsl -help. A new archive will appear on your desktop. When the progress bar gets to the end click 'Finish'. PowerShell would either return that I didn't have permission (when run outside Administrator) or Access Denied (when run as Administrator. It may be assumed that the active user is always logged-in as standard, local user (not as an administrator) on Windows 10 and that write access is specifically denied to that user, using NTFS' security features. Save this tool on each PC, then right click on the downloaded file and from the menu choose 'Run as Administrator': 2. I experienced this issue when Docker stopped unexpectedly. "Access denied" when trying to execute "wsl"ĭoes anyone have any other ideas I could try out? So all good and well, but STILL the PowerShell outputs Bitdefender reserves the right to refuse, suspend or terminate any of the. and last but not least I've checked that the permissions in the registry to the nodeĬomputer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Lxss You may not use the services to gain unauthorized access, to upload, transmit.vhdx file type / for the file that resides in C:\Users\AppData\Local\Docker\wsl\data granting my user & administrator the full permissions to the WindowsApps folder.I then followed various suggestions like: Then I've shut down wsl via wsl -shutdown as advised in the Microsoft documentation:Īfter a reboot I can no longer start wsl from the Powershell - neither with normal user nor administrator. past Bitdefender Antivirus Free Edition for the top spot. (I also created the above temp folder and granted permission to access them for my user and administrator) 3307 Fax Business Hours Order Desk/Customer Service 6:00am -3:00pm PST May 29. Processors=4 # Makes the WSL 2 VM use N virtual processors wslconfig file in my windows user home folder: After wondering about the extreme high amount of RAM consumption I've followed the advice from here ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |