Powershell wsl command not working

Powershell wsl command not working DEFAULT

Troubleshooting Windows Subsystem for Linux

We have covered some common troubleshooting scenarios associated with WSL below, but please consider searching the issues filed in the WSL product repo on GitHub as well.

File an issue, bug report, feature request

The WSL product repo issues enables you to:

  • Search existing issues to see if there are any associated with a problem that you are having. Note that in the search bar, you can remove "is:open" to include issues that have already been resolved in your search. Please consider commenting or giving a thumbs up to any open issues that you would like to express your interest in moving forward as a priority.
  • File a new issue. If you have found a problem with WSL and there does not appear to be an existing issue, you can select the green New issue button and then choose WSL - Bug Report. You will need to include a title for the issue, your Windows build number (run to see your current build #), whether you're running WSL 1 or 2, your current Linux Kernel version # (run or ), the version # of your distribution (run ), any other software versions involved, the repro steps, expected behavior, actual behavior, and diagnostic logs if available and appropriate. For more info, see contributing to WSL.
  • File a feature request by selecting the green New issue button and then select Feature request. You will need to address a few questions describing your request.

You can also:

Installation issues

  • Installation failed with error 0x80070003

    • The Windows Subsystem for Linux only runs on your system drive (usually this is your drive). Make sure that distributions are stored on your system drive:
    • Open Settings -> System --> Storage -> More Storage Settings: Change where new content is savedPicture of system settings to install apps on C: drive
  • WslRegisterDistribution failed with error 0x8007019e

    • The Windows Subsystem for Linux optional component is not enabled:
    • Open Control Panel -> Programs and Features -> Turn Windows Feature on or off -> Check Windows Subsystem for Linux or using the PowerShell cmdlet mentioned at the beginning of this article.
  • Installation failed with error 0x80070003 or error 0x80370102

    • Please make sure that virtualization is enabled inside of your computer's BIOS. The instructions on how to do this will vary from computer to computer, and will most likely be under CPU related options.
    • WSL2 requires that your CPU supports the Second Level Address Translation (SLAT) feature, which was introduced in Intel Nehalem processors (Intel Core 1st Generation) and AMD Opteron. Older CPUs (such as the Intel Core 2 Duo) will not be able to run WSL2, even if the Virtual Machine Platform is successfully installed.
  • Error when trying to upgrade:

    • Ensure that you have the Windows Subsystem for Linux enabled, and that you're using Windows Build version 18362 or higher. To enable WSL run this command in a PowerShell prompt with admin privileges: .
  • The requested operation could not be completed due to a virtual disk system limitation. Virtual hard disk files must be uncompressed and unencrypted and must not be sparse.

    • Deselect “Compress contents” (as well as “Encrypt contents” if that’s checked) by opening the profile folder for your Linux distribution. It should be located in a folder on your Windows file system, something like:
    • In this Linux distro profile, there should be a LocalState folder. Right-click this folder to display a menu of options. Select Properties > Advanced and then ensure that the “Compress contents to save disk space” and “Encrypt contents to secure data” checkboxes are unselected (not checked). If you are asked whether to apply this to just to the current folder or to all subfolders and files, select “just this folder” because you are only clearing the compress flag. After this, the command should work.

Screenshot of WSL distro property settings


In my case, the LocalState folder for my Ubuntu 18.04 distribution was located at C:\Users<my-user-name>\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgsc

Check WSL Docs GitHub thread #4103 where this issue is being tracked for updated information.

  • The term 'wsl' is not recognized as the name of a cmdlet, function, script file, or operable program.

  • Error: Windows Subsystem for Linux has no installed distributions.

    • If you receive this error after you have already installed WSL distributions:
    1. Run the distribution at least once before invoking it from the command line.
    2. Check whether you may be running separate user accounts. Running your primary user account with elevated permissions (in admin mode) should not result in this error, but you should ensure that you aren't accidentally running the built-in Administrator account that comes with Windows. This is a separate user account and will not show any installed WSL distributions by design. For more info, see Enable and Disable the Built-in Administrator Account.
    3. The WSL executable is only installed to the native system directory. When you’re running a 32-bit process on 64-bit Windows (or on ARM64, any non-native combination), the hosted non-native process actually sees a different System32 folder. (The one a 32-bit process sees on x64 Windows is stored on disk at \Windows\SysWOW64.) You can access the “native” system32 from a hosted process by looking in the virtual folder: . It won’t actually be present on disk, mind you, but the filesystem path resolver will find it.
  • Error: This update only applies to machines with the Windows Subsystem for Linux.

    • To install the Linux kernel update MSI package, WSL is required and should be enabled first. If it fails, it you will see the message: .
    • There are three possible reason you see this message:
    1. You are still in old version of Windows which doesn't support WSL 2. See step #2 for version requirements and links to update.

    2. WSL is not enabled. You will need to return to step #1 and ensure that the optional WSL feature is enabled on your machine.

    3. After you enabled WSL, a reboot is required for it to take effect, reboot your machine and try again.

  • Error: WSL 2 requires an update to its kernel component. For information please visit https://aka.ms/wsl2kernel .

    • If the Linux kernel package is missing in the %SystemRoot%\system32\lxss\tools folder, you will encounter this error. Resolve it by installing the Linux kernel update MSI package in step #4 of these installation instructions. You may need to uninstall the MSI from 'Add or Remove Programs', and install it again.

Common issues

I'm on Windows 10 version 1903 and I still do not see options for WSL 2

This is likely because your machine has not yet taken the backport for WSL 2. The simplest way to resolve this is by going to Windows Settings and clicking 'Check for Updates' to install the latest updates on your system. See the full instructions on taking the backport.

If you hit 'Check for Updates' and still do not receive the update you can install KB KB4566116 manually.

Error: 0x1bc when

This may happen when 'Display Language' or 'System Locale' setting is not English.

The actual error for is:

For more information, please refer to issue 5749

Cannot access WSL files from Windows

A 9p protocol file server provides the service on the Linux side to allow Windows to access the Linux file system. If you cannot access WSL using on Windows, it could be because 9P did not start correctly.

To check this, you can check the start up logs using: , and this will show you any errors. A successful output looks like the following:

Please see this Github thread for further discussion on this issue.

Can't start WSL 2 distribution and only see 'WSL 2' in output

If your display language is not English, then it is possible you are seeing a truncated version of an error text.

To resolve this issue, please visit and install the kernel manually by following the directions on that doc page.

when executing windows .exe in linux

Users can run Windows executables like notepad.exe directly from Linux. Sometimes, you may hit "command not found" like below:

If there are no win32 paths in your $PATH, interop isn't going to find the .exe. You can verify it by running in Linux. It's expected that you will see a win32 path (for example, /mnt/c/Windows) in the output. If you can't see any Windows paths then most likely your PATH is being overwritten by your Linux shell.

Here is a an example that /etc/profile on Debian contributed to the problem:

The correct way on Debian is to remove above lines. You may also append $PATH during the assignment like below, but this lead to some other problems with WSL and VSCode..

For more information, see issue 5296 and issue 5779.

"Error: 0x80370102 The virtual machine could not be started because a required feature is not installed."

Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.

  1. Check the Hyper-V system requirements

  2. If your machine is a VM, please enable nested virtualization manually. Launch powershell with admin, and run:

  3. Please follow guidelines from your PC's manufacturer on how to enable virtualization. In general, this can involve using the system BIOS to ensure that these features are enabled on your CPU. Instructions for this process can vary from machine to machine, please see this article from Bleeping Computer for an example.

  4. Restart your machine after enabling the optional component.

  5. Additionally, if you have 3rd party hypervisors installed (Such as VMware or VirtualBox) then please ensure you have these on the latest versions which can support HyperV (VMware 15.5.5+ and VirtualBox 6+) or are turned off.

Learn more about how to Configure Nested Virtualization when running Hyper-V in a Virtual Machine.

Bash loses network connectivity once connected to a VPN

If after connecting to a VPN on Windows, bash loses network connectivity, try this workaround from within bash. This workaround will allow you to manually override the DNS resolution through .

  1. Take a note of the DNS server of the VPN from doing
  2. Make a copy of the existing resolv.conf
  3. Unlink the current resolv.conf
  4. Open and
    a. Delete the first line from the file, which says "# This file was automatically generated by WSL. To stop automatic generation of this file, remove this line.".
    b. Add the DNS entry from (1) above as the very first entry in the list of DNS servers.
    c. Close the file.

Once you have disconnected the VPN, you will have to revert the changes to . To do this, do:

    Starting WSL or installing a distribution returns an error code

    Follow these instructions to collect detailed logs and file an issue on our GitHub.

    Updating WSL

    There are two components of Windows Subsystem for Linux that can require updating.

    1. To update the Windows Subsystem for Linux itself, use the command in PowerShell or CMD.

    2. To update the specific Linux distribution user binaries, use the command: in the Linux distribution that you are seeking to update.

    Apt-get upgrade errors

    Some packages use features that we haven't implemented yet. , for example, isn't supported yet and causes several errors.

    To fix issues related to , follow the following steps:

    1. Write the following to and save your changes.

    2. Add execute permissions to :

    3. Run the following commands:

    "Error: 0x80040306" on installation

    This has to do with the fact that we do not support legacy console. To turn off legacy console:

    1. Open cmd.exe
    2. Right click title bar -> Properties -> Uncheck Use legacy console
    3. Click OK

    "Error: 0x80040154" after Windows update

    The Windows Subsystem for Linux feature may be disabled during a Windows update. If this happens the Windows feature must be re-enabled. Instructions for enabling the Windows Subsystem for Linux can be found in the Manual Installation Guide.

    Changing the display language

    WSL install will try to automatically change the Ubuntu locale to match the locale of your Windows install. If you do not want this behavior you can run this command to change the Ubuntu locale after install completes. You will have to relaunch bash.exe for this change to take effect.

    The below example changes to locale to en-US:

    Installation issues after Windows system restore

    1. Delete the folder.
      Note: Do not do this if your optional feature is fully installed and working.
    2. Enable the WSL optional feature (if not already)
    3. Reboot
    4. lxrun /uninstall /full
    5. Install bash

    No internet access in WSL

    Some users have reported issues with specific firewall applications blocking internet access in WSL. The firewalls reported are:

    1. Kaspersky
    2. AVG
    3. Avast
    4. Symantec Endpoint Protection

    In some cases turning off the firewall allows for access. In some cases simply having the firewall installed looks to block access.

    If you are using Microsoft Defender Firewall, unchecking "Blocks all incoming connections, including those in the list of allowed apps." allows for access.

    Permission Denied error when using ping

    For Windows Anniversary Update, version 1607, administrator privileges in Windows are required to run ping in WSL. To run ping, run Bash on Ubuntu on Windows as an administrator, or run bash.exe from a CMD/PowerShell prompt with administrator privileges.

    For later versions of Windows, Build 14926+, administrator privileges are no longer required.

    Bash is hung

    If while working with bash, you find that bash is hung (or deadlocked) and not responding to inputs, help us diagnose the issue by collecting and reporting a memory dump. Note that these steps will crash your system. Do not do this if you are not comfortable with that or save your work prior to doing this.

    To collect a memory dump

    1. Change the memory dump type to "complete memory dump". While changing the dump type, take a note of your current type.

    2. Use the steps to configure crash using keyboard control.

    3. Repro the hang or deadlock.

    4. Crash the system using the key sequence from (2).

    5. The system will crash and collect the memory dump.

    6. Once the system reboots, report the memory.dmp to [email protected] The default location of the dump file is %SystemRoot%\memory.dmp or C:\Windows\memory.dmp if C: is the system drive. In the email, note that the dump is for the WSL or Bash on Windows team.

    7. Restore the memory dump type to the original setting.

    Check your build number

    To find your PC's architecture and Windows build number, open
    Settings > System > About

    Look for the OS Build and System Type fields.
    Screenshot of Build and System Type fields

    To find your Windows Server build number, run the following in PowerShell:

    Confirm WSL is enabled

    You can confirm that the Windows Subsystem for Linux is enabled by running the following in PowerShell:

    OpenSSH-Server connection issues

    Trying to connect your SSH server is failed with the following error: "Connection closed by port 22".

    1. Make sure your OpenSSH Server is running:

      and you've followed this tutorial: https://ubuntu.com/server/docs/service-openssh

    2. Stop the sshd service and start sshd in debug mode:

    3. Check the startup logs and make sure HostKeys are available and you don't see log messages such as:

    If you do see such messages and the keys are missing under , you will have to regenerate the keys or just purge&install openssh-server:

    "The referenced assembly could not be found." when enabling the WSL optional feature

    This error is related to being in a bad install state. Please complete the following steps to try and fix this issue:

    • If you are running the enable WSL feature command from PowerShell, try using the GUI instead by opening the start menu, searching for 'Turn Windows features on or off' and then in the list select 'Windows Subsystem for Linux' which will install the optional component.

    • Update your version of Windows by going to Settings, Updates, and clicking 'Check for Updates'

    • If both of those fail and you need to access WSL please consider upgrading in place by reinstalling Windows 10 using installation media and selecting 'Keep Everything' to ensure your apps and files are preserved. You can find instructions on how to do so at the Reinstall Windows 10 page.

    Correct (SSH related) permission errors

    If you're seeing this error:

    To fix this, append the following to the the file:

    Please note that adding this command will include metadata and modify the file permissions on the Windows files seen from WSL. Please see the File System Permissions for more information.

    Running Windows commands fails inside a distribution

    Some distributions available in Microsoft Store are yet not fully compatible to run Windows commands out of the box. If you get an error running or any other Windows command, you can resolve it following these steps:

    1. In your WSL distribution run .
      If it does not include: something is redefining the standard PATH variable.
    2. Check profile settings with .
      If it contains assignment of the PATH variable, edit the file to comment out PATH assignment block with a # character.
    3. Check if wsl.conf is present and make sure it does not contain , otherwise comment it out.
    4. Restart distribution by typing followed by distribution name or run either in cmd or PowerShell.

    Unable to boot after installing WSL 2

    We are aware of an issue affecting users where they are unable to boot after installing WSL 2. While we fully diagnose those issue, users have reported that changing the buffer size or installing the right drivers can help address this. Please view this Github issue to see the latest updates on this issue.

    WSL 2 errors when ICS is disabled

    Internet Connection Sharing (ICS) is a required component of WSL 2. The ICS service is used by the Host Network Service (HNS) to create the underlying virtual network which WSL 2 relies on for NAT, DNS, DHCP, and host connection sharing.

    Disabling the ICS service (SharedAccess) or disabling ICS through group policy will prevent the WSL HNS network from being created. This will result in failures when creating a new WSL version 2 image, and the following error when trying to convert a version 1 image to version 2.

    Systems that require WSL 2 should leave the ICS service (SharedAccess) in it's default start state, Manual (Trigger Start), and any policy that disables ICS should be overwritten or removed. While disabling the ICS service will break WSL 2, and we do not recommend disabling ICS, portions of ICS can be disabled using these instructionsng-application-guard-)

    Using older versions of Windows and WSL

    There are several differences to note if you're running an older version of Windows and WSL, like the Windows 10 Creators Update (Oct 2017, Build 16299) or Anniversary Update (Aug 2016, Build 14393). We recommend that you update to the latest Windows version, but if that's not possible, we have outlined some of the differences below.

    Interoperability command differences:

    • has been replaced with . Linux commands can be run from the Windows Command Prompt or from PowerShell, but for early Windows versions, you man need to use the command. For example: . The WSL commands passed into are forwarded to the WSL process without modification. File paths must be specified in the WSL format and care must be taken to escape relevant characters. For example: or .
    • To see what commands are available for a particular distribution, run . For example, with Ubuntu: .
    • Windows path is included in the WSL .
    • When calling a Windows tool from a WSL distribution in an earlier version of Windows 10, you will need to specify the directory path. For example, to call the Windows Notepad app from your WSL command line, enter:
    • To change the default user to use this command in PowerShell: and then run Bash.exe to log in: . Reset your password using the distributions password command: and then close the Linux command line: . From Windows command prompt or Powershell, reset your default user back to your normal Linux user account: .

    Uninstall legacy version of WSL

    If you originally installed WSL on a version of Windows 10 prior to Creators update (Oct 2017, Build 16299), we recommend that you migrate any necessary files, data, etc. from the older Linux distribution you installed, to a newer distribution installed via the Microsoft Store. To remove the legacy distribution from your machine, run the following from a Command Line or PowerShell instance: . You also have the option to manually remove the older legacy distribution by deleting the folder (and all it's sub-contents) using Windows File Explorer or with PowerShell: .

    Sours: https://docs.microsoft.com/en-us/windows/wsl/troubleshooting

    wsl' is not recognized as an internal or external command

    The most common reason why a command which runs an executable program works on the command line, but not in a batch script, is that, in the script, prior to the line containing the problem command, the user has created a variable %path%. It might seem a handy name for a variable that holds, well, a path. The problem is that this variable name is used by Windows to hold a semicolon-separated list of folders which are searched when an executable is called. It is a system variable. If you have redefined it, then all executables (e.g. .exe, .bat, .vbs, etc) that Windows uses, will not be found, and the script will fail with exactly this message, where xxx is the program or file that is expected:

    This can be confusing because commands which are internal to the cmd environment (dir, cls, set, copy, move, etc) (list here) still continue to work in this situation.

    You can debug a script where this is suspected by inserting the command immediately before a problem line. The Windows path variable starts with these folders, and may be extended as programs are installed:

    Sours: https://superuser.com/questions/1501478/wsl-is-not-recognized-as-an-internal-or-external-command/1501560
    1. Rad bike water bottle holder
    2. Song i got my mama
    3. Desktop winter scenes free
    4. 1967 chevy impala red
    5. Car pencil case

    WSL Bash doesn't start

    I have been using Windows 10's Windows Subsystem for Linux (Ubuntu via Microsoft Store) in the last few weeks, no problem, awesome feature, couldn't be happier.

    But today it suddenly stopped working. Typing just does nothing on the command line ( and PowerShell), as if it would be waiting for something. It doesn't crash or output an error message, but just keeps showing a blinking cursor.

    enter image description here

    (Cursor not visible on screenshot, it is a blinking on the next line after )

    Task manager shows both command lines at 0% CPU with a "Microsoft Bash Launcher" process also at 0% CPU:

    enter image description here

    Any idea how to debug and fix this?

    Update: After a few manual restarts and one "crash" (I think stopped, and didn't really come back after killing the process after a prompt) it now works again for now.
    I had the problem a few weeks before (where I fixed it be reinstalling WSL), so I assume it will reappear sooner or later.

    Sours: https://superuser.com/questions/1275505/wsl-bash-doesnt-start
    Windows Terminal and WSL 2 tips

    How to install WSL on Windows 10

    Updated: 08/31/2020 by Computer Hope

    WSL bash illustration

    WSL, the Windows Subsystem for Linux, is a free, optional feature of Windows 10 that allows Linux programs to run on Windows. It provides you with a Windows version of the bash shell and a compatibility layer that permits many Linux programs to run natively on your Windows machine.

    System requirements

    Before installing WSL, make sure your computer meets the minimum system requirements to run WSL:

    • You must be running Windows 10 version 1607 (the Anniversary update) or above.
    • WSL only runs on 64-bit versions of Windows 10. 32-bit versions are not supported.

    To check that the computer meet the requirements, follow these steps:

    1. Open your Settings. You can do this by clicking the gear icon on the Start menu, or by opening the Power User Tasks menu and choosing Settings.
    2. In the Settings window, choose System.
    3. On the left side of the System window, choose About.
    4. On the right side of the window, system information is displayed. Make sure the Version is at least 1607, and the System type is a 64-bit operating system.

    Windows settings, system, about

    If the Version number is less than 1607, you need to perform a Windows Update before installing WSL.

    If the System type is not a 64-bit operating system, you cannot run WSL.

    Installing WSL

    To install WSL, follow these steps.


    Versions of Windows previous to the Fall Creators Update required slightly different instructions. The instructions on this page are current as of May 2019.

    1. Open a new PowerShell window as Administrator. To do this, open your Start menu, scroll down to W, and expand the Windows PowerShell folder. Right-click Windows PowerShell, choose More, then Run as administrator.
    1. At the PowerShell prompt, run the following command:
    Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
    1. Some necessary software downloads, and the WSL subsystem will be enabled after you reboot. Linux itself is not installed yet, however (until you choose a Linux distribution, in step 5.)
    1. When the download is complete, PowerShell ask if you're ready to reboot the computer. Before rebooting, make sure any documents are saved, and any open applications are closed. Type Y, or if you're going to reboot later, type N instead.
    1. After your computer reboots, log in to Windows and open a new Command prompt (or PowerShell). At the prompt, run:
    1. Bash will inform you that no distribution is installed, and give you a URL for downloading one from the Windows Store:
    Windows Subsystem for Linux has no installed distributions. Distributions can be installed by visiting the Windows Store: https://aka.ms/wslstore Press any key to continue...
    1. In a web browser, navigate to the URL https://aka.ms/wslstore to download a WSL-integrated Linux distribution. As of this writing, choices are Ubuntu, OpenSUSE, SUSE Enterprise Server, Debian, and Kali. If you're not sure what to pick, we recommend Ubuntu.

    In the Microsoft Store, choose Ubuntu.

    1. Click the distribution of your choice, then click Get.

    To download Ubuntu from the Microsoft Store, click Get.

    1. When the installation is complete, click Launch. You will see this message:
    Installing, this may take a few minutes...

    It may silently wait for you to press a key after it's done, so you might want to press every 15 seconds or so, to check if it's finished.


    You may receive this error:

    Installing, this may take a few minutes... Installation failed! Error: 0x8000000d Press any key to continue...

    This error is a known bug that occurs in some versions of Windows 10. If you get this error, you can fix it by repeating steps 1 and 2. Then, continue to step 10.

    1. Ubuntu is now installed, and WSL is enabled. You can open the WSL Ubuntu command prompt by clicking the Launch button in the Windows Store or in the Start menu by choosing Ubuntu. You can also open a command prompt (or PowerShell) and run bash.

    Getting started with your Linux subsystem

    The first time you run your WSL distribution, you will be asked to create a user account. It can be different than your Windows username. You will be asked to set a password.

    Creating a user in WSL.

    Congratulations! Linux is running. You're now at the bash prompt, and you can run Linux commands and programs.

    Update your Linux software

    Now is a great time to perform a software update. Follow the instructions below to update your software with the apt command.

    Like Ubuntu, WSL uses the APT (advanced packaging tool) to manage software packages. The apt command allows you to search for, download, and install software, all from the command line. It automatically manages your software dependencies for you. That way, if one program depends on a certain version of another program, both will be installed, and kept up-to-date.

    Any apt commands that make changes to your system must run as root. If you're logged in as your regular user (as you usually should be), run a program as root by prefixing it with sudo ("superuser do"). It requires you enter your password, and your program is run as root.

    sudo apt update[sudo] password for hope:

    Updates download, but nothing is installed or upgraded yet. To upgrade all available packages, run:

    sudo apt upgrade

    Sudo will not ask you for your password this time, unless more than five minutes have elapsed since the last sudo command.

    The size of the upgrades is calculated, and you will be prompted to continue. Type y and press . The upgrades download and install, which might take a while, depending on the speed of your computer and Internet connection.

    When the upgrade is complete, you will be returned to the bash prompt. Your Linux system is now up-to-date.

    At any time, you can exit bash using the exit command.


    The Windows and WSL filesystems

    WSL has its own filesystem. This Linux filesystem is installed to your Windows filesystem at the following location:


    For instance, if your Windows username is Owner and Windows is installed on your C: drive, your WSL filesystem is located at:


    It's good to know that this is where it's located, but you shouldn't move or make any changes to the files it contains.

    When you're using WSL, you might be wondering how you can access your Windows files. Your C: drive is located at:


    The name mnt stands for "mount," which is where your Windows drives are mounted within WSL. For instance, your D: drive would be /mnt/d/, etc.

    Creating links to Windows folders

    For convenience, it's a good idea to create symbolic links to your Windows home folder. A symbolic link is similar to a shortcut in Windows: it's a file that points to another file or directory. When you refer to the symbolic link, the system will dereference the link, and behave as if you had specified the actual "target" file or directory.

    Using symbolic links can save you a lot of typing, and remembering of obscure directory names.

    To create a symbolic link in Linux, use the ln command. The syntax for creating a symbolic link is ln -s targetnamelinkname.

    For instance, to create a symbolic link in your WSL home folder called winhome that refers to C:\Users\Owner\, follow these steps.

    First, change the working directory to your home directory, which is located at /home/username/. You can do this with the cd command:

    cd /home/hope/

    In bash, "~" (a tilde) is an alias for your home directory, so you can also type:

    cd ~

    Next, use ln -s to create the symbolic link. For instance, if your Windows home folder is C:\Users\Owner\, the command would be:

    ln -s /mnt/c/Users/Owner/ winhome

    Now there's a symbolic link called winhome in your WSL home directory, which acts like a shortcut to your Windows home directory. So, you can change to your Windows home directory using:

    cd ~/winhome/

    Or, to change to your Windows desktop folder:

    cd ~/winhome/Desktop/

    More information about Linux commands

    Enjoy your new Linux subsystem! Make sure to visit our overview of Linux commands for more information about tools and programs you can use.

    Sours: https://www.computerhope.com/issues/ch001879.htm

    Working powershell wsl command not


    WSL 2 Mainline Linux Kernel + 🐞 9pnet transport virtio + 🐞 VS Code command not found SOLVED


    You will also be interested:


    37 38 39 40 41