Issue with virtualenv - cannot activate

source is a shell command designed for users running on Linux (or any Posix, but whatever, not Windows).

On Windows, virtualenv creates a .bat/.ps1 file, so you should run venv\Scripts\activate instead (per the virtualenv documentation on the activate script).

Just run activate, without an extension, so the right file will get used regardless of whether you're using cmd.exe or PowerShell.

---

I was also facing the same issue in my Windows 10 machine. What steps i tried were:

Go to andconda terminal Step 1

pip3 install -U pip virtualenv

Step 2

virtualenv --system-site-packages -p python ./venv

or

virtualenv --system-site-packages -p python3 ./venv

Step 3

.\venv\activate

You can check it via spider tool in anaconda by typing import tensorflow as tf

---

I had the same problem. I was using Python 2, Windows 10 and Git Bash. Turns out in Git Bash you need to use:

 source venv/Scripts/activate

---

For activation you can go to the venv your virtualenv directory by cd venv. Then on Windows, type dir (on unix, type ls). You will get 5 folders include, Lib, Scripts, tcl and 60 Now type .\Scripts\activate to activate your virtualenv venv.

Your prompt will change to indicate that you are now operating within the virtual environment. It will look something like this (venv)user@host:~/venv$.

And your venv is activated now.

---

Ensure venv is there and just follow the commands below. It works in Windows 10.

Go to the path where you want your virtual enviroments to reside:

> cd <my_venv_path>

Create the virtual environment named "env":

> python -m venv env 

Add the path to the git ignore file (optional):

> echo env/ >> .gitignore

Activate the virtual env:

> .\env\Scripts\activate

---

source command is officially for Unix operating systems family and you can't use it on windows basically. instead, you can use venv\Scripts\activate command to activate your virtual environment.

https://i.stack.imgur.com/fLMlT.png

---

https://i.stack.imgur.com/uymhn.png

---

if you already cd your project type only in windows 10

Scripts/activate

That works for me:)

---

Tried several different commands until I came across:

source venv/Scripts/activate

This did it for me. Setup: Win 10, python 3.7, gitbash. Gitbash might be the culprit for not playing nice with other activate commands.

---

Open your powershell as admin Enter "Set-ExecutionPolicy RemoteSigned -Force Run "gpedit.msc" and go to >Administrative Templates>Windows Components>Windows Powershell Look for "Activate scripts execution" and set it on "Activated" Set execution directive to "Allow All" Apply Refresh your env

---

I have a hell of a time using virtualenv on windows with git bash, I usually end up specifying the python binary explicitly.

If my environment is in say .env I'll call python via ./.env/Scripts/python.exe …, or in a shebang line #!./.env/Scripts/python.exe;

Both assuming your working directory contains your virtualenv (.env).

---

You can run the source command on cygwin terminal

---

A small reminder, but I had my slashes the wrong way on Win10 cmd. According to python documentation the activate command is: C:\> <venv>\Scripts\activate.bat When you're browsing directories it's e.g. cd .env/Scripts

So to create my venv I used python -m venv --copies .env and to activate .env\Scripts\activate.bat

---

open the folder with any gitbash console. for example using visualCode and Gitbash console program: 1)Install Gitbash for windows

2) using VisualCode IDE, right click over the project open in terminal console option

3) on window console in Visualcode, looking for a Select->default shell and change it for Gitbash

4)now your project is open with bash console and right path, put source ./Scripts/activate

btw : . with blank space = source

https://i.stack.imgur.com/TnmBM.png

---

For windows Microsoft Tech Support it might be a problem with Execution Policy Settings. To fix it, you should try executing Set-ExecutionPolicy Unrestricted -Scope Process

---

Finally Worked on Windows 10 by using:

activate myvenv

where myvenv is the name the virtual environment I want to activate.

So basically, the command is:

activate <<your_venv_name>>

All the best!

---

If you see the 5 folders (Include,Lib,Scripts,tcl,pip-selfcheck) after using the virtualenv yourenvname command, change directory to Scripts folder in the cmd itself and simply use "activate" command.

---

If you’re using Windows, use the command "venv\Scripts\activate" (without the word source) to activate the virtual environment. If you’re using PowerShell, you might need to capitalize Activate.

---

If wants to open virtual environment on Windows then just remember one thing on giving path use backwards slash not forward.

This is right:

D:\xampp\htdocs\htmldemo\python-virtual-environment>env\Scripts\activate

This is wrong:

D:\xampp\htdocs\htmldemo\python-virtual-environment>env/Scripts/activate

---

The steps for activating virtualenv using Python3 on windows are:

python3 -m venv env .\env\bin\activate

---

Use These it worked for meenv\Scripts\activate

---

if .\venv\Scripts\activate does not work neither and you find this error

\Activate.ps1 cannot be loaded because running scripts is disabled on this system

you can simple type set-executionpolicy remotesigned in powershell and the error must be gone.

powershell should run as administrator

---

If you are using windows OS then in Gitbash terminal use the following command $source venv/Scripts/activate. This will help you to enter the virtual environment.

---

Open your project using VS code editor . Change the default shell in vs code terminal to git bash. now your project is open with bash console and right path, put "source venv\Scripts\activate" in Windows

---

Navigate to your virtualenv folder eg ..\project1_env> Then type

source scripts/activate

eg ..\project1_env>source scripts/activate

---

The best way is, using backward slahes and using .bat at the end of activate

C:\Users>your_env_name\Scripts\activate.bat

---

:: location of bat file
::C:\Users\gaojia\Dropbox\Projects\free_return\venv\Scripts\activate.bat 
:: location of the cmd bat file and the ipython notebook
::C:\Users\gaojia\Dropbox\Projects\free_return\scripts\pre_analysis
source ..\..\venv\Scripts\activate
PAUSE
jupyter nbconvert --to html --execute consumer_response_DID.ipynb
PAUSE

Above is my bat file through which I try to execute an ipython notebook. But the cmd window gives me nothing and shut down instantly, any suggestion why would this happen?

---

If you are using windows, just run .\Scripts\activate. Mind that the backslash plays the trick!

---

Some people are having trouble with vscode i assume as all the above methods dont work.

Its simply because by default vscode uses powershell not cmd... click on the little arrow beside it and select cmd and run the command.

---

It's been a while without usign Django, so when I got back to my old project I run into the same issue on Windows 10 and this worked for me:

venv/Scripts/activate

---