{"id":13931,"date":"2026-06-13T20:28:51","date_gmt":"2026-06-13T20:28:51","guid":{"rendered":"https:\/\/savethevideo.net\/blog\/?p=13931"},"modified":"2026-06-13T20:39:07","modified_gmt":"2026-06-13T20:39:07","slug":"how-to-reopen-wsl-previously-created-in-powershell","status":"publish","type":"post","link":"https:\/\/savethevideo.net\/blog\/how-to-reopen-wsl-previously-created-in-powershell\/","title":{"rendered":"How to Reopen WSL Previously Created in PowerShell"},"content":{"rendered":"

If you created a Windows Subsystem for Linux environment from PowerShell and later wondered how to get back into it, you are not alone. WSL can feel slightly different from a normal application because a Linux distribution is not always reopened from the same place where it was created. The good news is that once a WSL distribution exists, Windows remembers it, and you can reopen it from PowerShell, Windows Terminal, the Start menu, File Explorer, or even a desktop shortcut.<\/p>\n

TLDR:<\/strong> To reopen a previously created WSL instance, open PowerShell and run wsl<\/code> or wsl -d DistroName<\/code>. Use wsl -l -v<\/code> to see the exact names of your installed distributions. If you imported a custom distro, it may not appear like a normal app, but it is still available through the wsl<\/code> command. For regular use, Windows Terminal profiles and shortcuts make reopening WSL much easier.<\/p>\n

Understanding What \u201cReopen WSL\u201d Really Means<\/h2>\n

When people say they \u201ccreated WSL in PowerShell,\u201d they may mean one of several things. They might have installed Ubuntu using wsl --install<\/code>, imported a custom Linux root filesystem with wsl --import<\/code>, or enabled WSL features and then launched a distribution for the first time. In all cases, WSL works as a lightweight Linux environment managed by Windows, not as a traditional virtual machine that you open from a separate hypervisor window.<\/p>\n

That means reopening WSL is usually as simple as launching the distribution again. You do not need to reinstall it, recreate it, or repeat the original command unless something was removed. Your Linux files, packages, users, and shell configuration should still be there.<\/p>\n\"\"\n

Step 1: Open PowerShell<\/h2>\n

The most direct way to reopen WSL is through PowerShell, especially if that is where you originally created it. You can use either Windows PowerShell<\/strong> or PowerShell 7<\/strong>. For most basic WSL commands, both work the same way.<\/p>\n

    \n
  1. Press Windows<\/strong> on your keyboard.<\/li>\n
  2. Type PowerShell<\/strong>.<\/li>\n
  3. Open Windows PowerShell<\/strong> or PowerShell<\/strong>.<\/li>\n
  4. At the prompt, type wsl<\/code> and press Enter<\/strong>.<\/li>\n<\/ol>\n
    wsl<\/code><\/pre>\n
    If you have only one WSL distribution installed, this command usually opens it immediately. You should see a Linux prompt, often ending with a dollar sign such as $<\/code>. That means you are now inside your Linux environment.<\/p>\n
    Step 2: List Your Installed WSL Distributions<\/h2>\n
    If typing wsl<\/code> does not open the distribution you expected, you may have more than one installed. To see all registered WSL distributions, run:<\/p>\n
    wsl -l -v<\/code><\/pre>\n
    This command lists your distributions, their current state, and which WSL version they use. The output may look similar to this:<\/p>\n
      NAME            STATE           VERSION\n* Ubuntu          Stopped         2\n  Debian          Running         2\n  MyCustomLinux   Stopped         2<\/code><\/pre>\n
    The asterisk marks the default distribution<\/strong>. When you run wsl<\/code> without extra options, Windows opens that default distro. If your previously created WSL environment is listed under a different name, you can launch it directly.<\/p>\n
    Step 3: Reopen a Specific Distribution<\/h2>\n
    To open a particular WSL distribution, use the -d<\/code> option followed by its name:<\/p>\n
    wsl -d Ubuntu<\/code><\/pre>\n
    For a custom imported distribution, the command might look like this:<\/p>\n
    wsl -d MyCustomLinux<\/code><\/pre>\n
    Names are important. Use the exact name shown by wsl -l -v<\/code>. If the name contains spaces, wrap it in quotation marks:<\/p>\n
    wsl -d \"Ubuntu 22.04\"<\/code><\/pre>\n
    This is one of the most useful commands to remember because it works even if the distribution does not have a Start menu icon or Windows Terminal profile.<\/p>\n
    What If the Distribution Says \u201cStopped\u201d?<\/h2>\n
    Seeing Stopped<\/code> in the distribution list is normal. It does not mean the Linux system is broken. WSL distributions automatically stop when they are not being used, which helps save memory and CPU resources. When you run wsl -d DistroName<\/code>, Windows starts the distribution again and opens a shell.<\/p>\n
    Think of it like waking a laptop from sleep rather than reinstalling an operating system. Your files, installed tools, shell history, and configuration are still available.<\/p>\n
    Setting the Right Default Distribution<\/h2>\n
    If you want a specific WSL distribution to open every time you type wsl<\/code>, set it as the default:<\/p>\n
    wsl --set-default Ubuntu<\/code><\/pre>\n
    After that, simply running:<\/p>\n
    wsl<\/code><\/pre>\n
    will open Ubuntu. This is especially handy if you created multiple distributions for testing, development, or experimentation but mainly use one of them day to day.<\/p>\n
    Opening WSL from Windows Terminal<\/h2>\n
    PowerShell is reliable, but Windows Terminal<\/strong> is often more comfortable for daily WSL use. It supports tabs, profiles, themes, split panes, and better font rendering. If your WSL distribution was installed normally from the Microsoft Store or with wsl --install<\/code>, Windows Terminal may automatically create a profile for it.<\/p>\n
    To open WSL from Windows Terminal:<\/p>\n
      \n
    1. Open Windows Terminal<\/strong>.<\/li>\n
    2. Click the small dropdown arrow next to the tab button.<\/li>\n
    3. Select your Linux distribution, such as Ubuntu<\/strong> or Debian<\/strong>.<\/li>\n<\/ol>\n
      If your distribution does not appear, you can still open a PowerShell tab and run wsl -d DistroName<\/code>. For imported distros, Windows Terminal does not always create a profile automatically, but you can add one manually in the Terminal settings.<\/p>\n\"\"\n
      Opening WSL from the Start Menu<\/h2>\n
      Many standard WSL distributions appear in the Windows Start menu as regular apps. For example, if you installed Ubuntu, you may be able to press Windows<\/strong>, type Ubuntu<\/strong>, and launch it directly.<\/p>\n
      This method is convenient, but it is not universal. A distribution imported using wsl --import<\/code> may not create a Start menu entry. That does not mean it is missing. It simply means Windows registered it as a WSL distribution without adding an app shortcut. In that case, PowerShell remains the most dependable way to reopen it.<\/p>\n
      Opening WSL in a Specific Windows Folder<\/h2>\n
      Sometimes you do not just want to reopen WSL; you want it to start in a particular project directory. WSL can open from the current Windows path when you run it from PowerShell.<\/p>\n
      For example:<\/p>\n
      cd C:\\Users\\YourName\\Projects\\myapp\nwsl<\/code><\/pre>\n
      Inside WSL, that Windows folder appears under \/mnt\/c<\/code>. You can also run a specific command when launching WSL:<\/p>\n
      wsl -d Ubuntu -- pwd<\/code><\/pre>\n
      Or start in a Linux home directory:<\/p>\n
      wsl -d Ubuntu --cd ~<\/code><\/pre>\n
      This is useful for developers who move between Windows tools and Linux command line workflows. You can edit code in Windows, run scripts in Linux, and keep both environments connected.<\/p>\n
      Reopening an Imported WSL Distribution<\/h2>\n
      Imported distributions deserve special attention because they are often created entirely from PowerShell. A typical import command looks like this:<\/p>\n
      wsl --import MyCustomLinux C:\\WSL\\MyCustomLinux C:\\Images\\rootfs.tar --version 2<\/code><\/pre>\n
      After importing, you reopen it with:<\/p>\n
      wsl -d MyCustomLinux<\/code><\/pre>\n
      The folder used during import, such as C:\\WSL\\MyCustomLinux<\/code>, stores the virtual disk and supporting files. You normally should not manually edit those files from Windows while WSL is running. Instead, access your Linux filesystem from inside WSL or through the special Windows path:<\/p>\n
      \\\\wsl$\\MyCustomLinux<\/code><\/pre>\n
      You can paste that path into File Explorer to browse the Linux files safely.<\/p>\n
      Creating a Shortcut to Reopen WSL Quickly<\/h2>\n
      If you reopen the same distribution often, create a shortcut. On your desktop, right-click and choose New<\/strong> > Shortcut<\/strong>. For the location, enter something like:<\/p>\n
      wsl.exe -d Ubuntu<\/code><\/pre>\n
      Give it a name such as Ubuntu WSL<\/strong>. Double-clicking the shortcut will open the distribution. For a custom distribution, replace Ubuntu<\/code> with the exact distro name:<\/p>\n
      wsl.exe -d MyCustomLinux<\/code><\/pre>\n
      You can also pin Windows Terminal to the taskbar and configure its default profile to your preferred WSL distribution for an even smoother setup.<\/p>\n
      Checking Whether WSL Is Still Installed<\/h2>\n
      If wsl<\/code> is not recognized, WSL may not be installed or enabled correctly. First, check the command:<\/p>\n
      wsl --status<\/code><\/pre>\n
      If Windows reports that the command does not exist, you may need to install or enable WSL again. On modern Windows 10 and Windows 11 systems, this command usually installs WSL and the default Linux distribution:<\/p>\n
      wsl --install<\/code><\/pre>\n
      However, be careful: reinstalling WSL is different from reopening an existing distribution. Before making changes, run wsl -l -v<\/code> if possible to verify whether your distributions are still registered.<\/p>\n
      Troubleshooting Common Reopening Problems<\/h2>\n
      Here are some common issues and practical fixes:<\/p>\n