Question: I recently switched over to WSL (Ubuntu). Now when I create a virtual env using

`python -m venv venv`

It is not detected in vs code automaticaly.

My settings.json

```
{
    "python.pythonPath": "C:\\Users\\ankus\\AppData\\Local\\Programs\\Python\\Python37-32\\python.exe",
}

```

I have tried to change it to this

```
{
    "python.pythonPath": "/mnt/c/Users/ankus/OneDrive/Documents/Main Projects/project_folder/venv/bin/python"
}

```

but nothing seems to work.

[Also, I can see only 1 python interpreter](https://i.stack.imgur.com/JHFck.png)

Answer: 
I was having this problem because I wasn't opening the folder through the WSL- Remote extension on VSC.

Try downloading the VSC extension 'Remote - WSL' by Microsoft.
Then go to the folder containing your virtual environment and use 'Ctrl + Shift + P' and search for 'Remote WSL: Reopen folder in WSL'

When I did this and opened one of the python files, the venv was found automatically by VSC. You might still need to select an interpreter, but the virtual env should be available this time. I didn't need to change any python.Path settings to make this happen.
Try to set `python.venvFolders`:

```
"python.venvFolders": [
    "/mnt/c/Users/ankus/OneDrive/Documents/Main Projects/project_folder/venv"
],

```

If you use "Remote - WSL" then venv should be created inside WSL. It still might not work under `/mnt/c/` or any other windows volume. Try moving your project to some folder inside `/home` and create venv there.

You can type `\\wsl$` in windows explorer to get access to your WSL files.