'virtualenv' won't activate on Windows

Question

Essentially I cannot seem to activate my virtualenv environment which I create.

I'm doing this inside of Windows PowerShell through using

scripts\activate

but I get an error message:

"cannot be loaded because the execution of scripts is disabled on this system".

Could this be because I don't carry administrator privileges on my computer?

According to [Microsoft Tech Support](http://social.technet.microsoft.com/Forums/windowsserver/en-US/964636ad-347e-4b23-8f7a-f36a558115dd/error-file-cannot-be-loaded-because-the-execution-of-scripts-is-disabled-on-this-system), setting Execution Policy to unrestrictred should help. How to do that: `Set-ExecutionPolicy Unrestricted -Force` — Kamiccolo, Sep 10 '13 at 07:47
@Kamiccolo AWESOME! You nailed it. Thanks for you help. Great first experience for me on stackoverflow. Thankyou! — SScode, Sep 10 '13 at 08:07
Or, if you have git bash (or mingw) installed, you could just activate it there instead in command windows powershell/command prompt — quasoft, Sep 21 '15 at 18:36
@Kamiccolo this worked for me on Windows 7 running Python 3. Thanks! — Mona Jalal, Jul 18 '16 at 17:48
@MonaJalal With Python3 you should use built-in `venv` which doesn't have this issue at all. — Franklin Yu, Sep 17 '18 at 19:45

score 224 · Accepted Answer · edited Apr 17 '21 at 15:16

224

According to Microsoft Tech Support it might be a problem with Execution Policy Settings. To fix it, you should try executing Set-ExecutionPolicy Unrestricted -Scope Process (as mentioned in the comment section by @wtsiamruk) in your PowerShell window. This would allow running virtualenv in the current PowerShell session.

There is also another approach that is more unsafe, but recommended by MS Tech Support. This approach would be to use Set-ExecutionPolicy Unrestricted -Force (which do unleash powers to screw Your system up). However, before you use this unsafe way, be sure to check what your current ExecutionPolicy setting is by using get-ExecutionPolicy. Then, when you are done, you can revert back to this ExecutionPolicy by using Set-ExecutionPolicy %the value the get-ExecutionPolicy command gave you% -Force.

edited Apr 17 '21 at 15:16

Peter Mortensen

30,030
21
100
124

answered Sep 10 '13 at 08:15

Kamiccolo

6,709
3
37
44

19

(for new readers) Also make sure you use Scripts\Activate.PS1 – mak Jan 13 '15 at 19:24
This worked for me. Wanted to point out that I tried the directions in the embed at this link unsuccessfully: https://virtualenv.pypa.io/en/stable/userguide/#activate-script. I wonder if its just wrong or is there a difference somewhere. – ThatsAMorais May 31 '16 at 17:19
3

Or Set-ExecutionPolicy Unrestricted -Scope CurrentUser to use a non-administrative PowerShell. – mijiturka Jun 13 '18 at 15:13
7

most safe aproach is probably to run "Set-ExecutionPolicy Unrestricted -Scope Process", that would allow you to run virtualenv in current powershell session – wtsiamruk Jun 20 '19 at 18:28
I really think @wtsiamruk's comment should be selected as the answer. Consindering opening up your Windows for all scripts could be a serious security flaw. – pojda Nov 03 '20 at 10:04
updated the original answer. Thanks for the heads up and sorry for taking too long ;) – Kamiccolo Nov 04 '20 at 21:56
Is there any way to do this permanently? Every new powershell I open I have to lookup this command to get started. – Meekohi Feb 10 '21 at 16:09
@Meekohi I was also looking for this info. You can use `Set-ExecutionPolicy Unrestricted -Scope CurrentUser` to allow running of all scripts, but it is a security risk... the available options are listed here under the `-Scope` section. https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-7.1#parameters – Dan Apr 10 '21 at 11:43
1

If `Set-ExecutionPolicy Unrestricted -Scope Process` works for you I think you should also run `Set-ExecutionPolicy Default -Scope Process` after activating the environment to change the execution policy back to avoid any potential issues – raresm Jul 01 '21 at 06:30

score 49 · Answer 2 · edited Apr 17 '21 at 16:00

49

In PowerShell use

Scripts\activate.ps1

instead of activate.bat which doesn't work in PowerShell any more.

Also deactivate it by just typing

deactivate

at the command prompt.

edited Apr 17 '21 at 16:00

Peter Mortensen

30,030
21
100
124

answered Mar 01 '19 at 23:28

Matt N

631
5
6

1

This is the best way to do it when you don't have any admin previlages. Life saver. thanks Matt – Satinder Sidhu Apr 01 '20 at 15:35
9

got the same error. Scripts\Activate.ps1 cannot be loaded because running scripts is disabled on this system. – LiorH Apr 12 '20 at 15:04
1

Works without admin privileges. It's insanely frustrating though. – Sebi Dec 02 '20 at 17:00
This doesn't work since it gives me the error described by the OP. – cbrnr Apr 05 '22 at 08:01

score 25 · Answer 3 · edited Apr 17 '21 at 16:42

25

On Windows, open Windows PowerShell as Administrator

Set-ExecutionPolicy Unrestricted -Force

Create a virtual environment:

pip install virtualenv
virtualenv foo
cd .\foo
.\Scripts\activate

edited Apr 17 '21 at 16:42

Peter Mortensen

30,030
21
100
124

answered Feb 13 '20 at 15:03

James Graham

39,063
41
167
242

score 9 · Answer 4 · edited Apr 23 '21 at 11:13

9

Set the excution policy for the process scope. After Yes [y], type the script/activate:

Enter image description here

edited Apr 23 '21 at 11:13

Peter Mortensen

30,030
21
100
124

answered Jan 10 '17 at 08:32

Adil Siddiqui

91
1
3

score 9 · Answer 5 · edited Apr 17 '21 at 17:02

9

Open another PowerShell window as administrator and then type:

set-executionpolicy remotesigned

Then press Y and then Enter.

Now close this PowerShell window and go back to the shell you were working with. This will solve the issue.

edited Apr 17 '21 at 17:02

Peter Mortensen

30,030
21
100
124

answered Aug 20 '20 at 12:25

Abhishek Chauhan

135
1
8

score 6 · Answer 6 · edited Apr 17 '21 at 15:18

6

Another quick solution I have found here (it is applicable for Windows PowerShell only) is like this:

First run

Scripts\cmd

Then run

Scripts\activate.bat

At this position, your Virtualenv is activated. Now if you deactivate it and want to activate it again later in the same session of PowerShell, you just need to run:

Scripts\activate

There isn't any need to use cmd or activate.bat command later.

edited Apr 17 '21 at 15:18

Peter Mortensen

30,030
21
100
124

answered May 23 '15 at 13:41

ni8mr

1,635
2
33
54

11

There is no `Scripts\cmd` for me. – renatov Jan 27 '16 at 16:04

score 2 · Answer 7 · edited Apr 17 '21 at 16:34

Follow these steps to the letter.

Step 1. Use Windows PowerShell as ADMINISTRATOR. (VERY IMPORTANT) and cd into the project folder. Run

virtual env

Step 2. Check in the scripts folder if you have your activate.bat file

\env\Scripts\activate.bat # It has to be there.

Step 3. If it is not, here make sure you have an Internet connection and run this again

virtual env

step 4. If the activate.bat file is there in the script folder, proceed.

step 5. Run this in your shell:

Set-ExecutionPolicy Unrestricted -Force

Step 6. To activate virtualenv on Windows, activate script is in the Scripts folder:

env\Scripts\activate.bat

Step 7. Check for the (env) at the start of each line. This shows you are on the virtual environment.

Step 8. To reactivate when you come back to the project the second time, run:

.\\env\Scripts\activate

score 1 · Answer 8 · edited Apr 17 '21 at 15:27

To install a virtual environment in Windows PowerShell only, but to activate, you'll need to run Windows PowerShell as an Administrator:

pip install virtualenv
virtualenv %Name of virtual environment%

It is installed now to activate it. Run PowerShell in as an administrator

Set-ExecutionPolicy Unrestricted -Force
.\env\Scripts\activate

To deactivate the environment

.\env\Scripts\deactivate

For more help, do visit the official page: https://pypi.org/project/virtualenv/1.8.2/

score 1 · Answer 9 · edited Apr 17 '21 at 15:29

1

If you don't want to change your computer's execution policy on Windows like I do, you can use a Windows command prompt instead of Windows PowerShell and just need to run

`Scripts\activate`

to activate your environment.

edited Apr 17 '21 at 15:29

Peter Mortensen

30,030
21
100
124

answered Nov 11 '18 at 17:06

ianNg

11
1

This doesn't solve the OP's problem because that's what the OP was originally trying... – Joel Nov 11 '18 at 17:31
@Joel Uhm, cmd and powershell are two different environments. the execution rights that is limited in powershell doesn't get the same restriction when being used in cmd prompts. well at least for this "scripts\activate" – ianNg Nov 11 '18 at 18:51
This worked for me. You can also go straight into the cmd environment from Powershell just by typing "cmd". – RobinP Aug 24 '21 at 11:56

score 1 · Answer 10 · edited Apr 17 '21 at 16:39

1

For me on Windows 10 64 bit:

Open cmd as an Administrator
powershell
Type Set-ExecutionPolicy Unrestricted -Force

Voilà, reopen Visual Studio Code and start pythoninnngg.

edited Apr 17 '21 at 16:39

Peter Mortensen

30,030
21
100
124

answered Feb 11 '20 at 05:44

Sami Kalammallah

23
7

score 1 · Answer 11 · answered Jan 24 '22 at 10:08

1

Below steps are working -

Set python path like C:\Program Files\Python310\Scripts\ in Environment Variable
Open PowerShell in Admin mode , and execute the below command -
Set-ExecutionPolicy Unrestricted -Force
Close PowerShell and repoen in Admin mode
Execute the below command -
venv\scripts\activate

answered Jan 24 '22 at 10:08

Koustav

399
2
6

tnx for answer. it's helpfull – Hassan Naghibi May 06 '22 at 10:11

score 0 · Answer 12 · edited Apr 23 '21 at 11:18

In Windows you should activate the virtual environment by the following command in cmd

E:\your_environment\Scripts> activate.bat

If the environment is activated then it shows your environment name enclosed with a bracket like this:

(your_environment) E:\your_environment\Scripts>

Also we can ensure by checking with where.exe it will list our active Python environment with order of hierarchy

 (your_environment) E:\your_environment\Scripts>where.exe python

 E:\your_environment\Scripts\python.exe

 C:\Python27\python.exe

If you need to deactivate then do:

(your_environment) E:\your_environment\Scripts>deactivate.bat

OP explicitly mentioned PowerShell, not CMD. – Franklin Yu Sep 17 '18 at 19:47 — Franklin Yu, Sep 17 '18 at 19:47

score 0 · Answer 13 · edited Apr 17 '21 at 15:24

This worked for me:

You can simply open a normal (you do not need elevated access) cmd or PowerShell session (I use the embedded PowerShell terminal in Visual Studio Code) and type the following from the folder where the script file is, e.g.: .venv\Scripts\Activate.ps1:

powershell.exe -executionpolicy unrestricted -command .\Activate.ps1 -Scope CurrentUser

And then you can run the activate command after that.

Note: This will only allow that specific script to run, and only by your logged-in user.

score 0 · Answer 14 · edited Apr 17 '21 at 15:59

0

If the machine 64 bit, open the x86 instance of PowerShell as Administrator and check (set) the execution policy.

Try this

Set-ExecutionPolicy Unrestricted

or

Set-ExecutionPolicy Unrestricted -Force

edited Apr 17 '21 at 15:59

Peter Mortensen

30,030
21
100
124

answered Feb 23 '19 at 16:06

yas

1

score 0 · Answer 15 · edited Apr 17 '21 at 16:44

0

Based on the answers found here, I created a short tutorial for this with screenshots.

Python 3.7
Windows 10 64bits
PowerShell

I hope it can help: How to setup Python 3 virtual environment on Windows 10

edited Apr 17 '21 at 16:44

Peter Mortensen

30,030
21
100
124

answered Feb 15 '20 at 21:36

dami.max

323
2
15

score 0 · Answer 16 · answered Mar 04 '20 at 03:51

0

Delete the directory for that venv you created. And create a new one using the command:

python -m venv myvenv

Then see if the activate command works.

answered Mar 04 '20 at 03:51

Emerson Araujo

1
1

score 0 · Answer 17 · edited Apr 17 '21 at 16:55

0

C:\path> Set-ExecutionPolicy - Scope CurrentUser

cmdlet Set-ExecutionPolicy at command pipeline position 1 Supply values for the following parameters: ExecutionPolicy: Unrestricted

C:\path> Scripts\activate.ps1

(new env)

C:\path> deactivate

C:\path>

This worked.

edited Apr 17 '21 at 16:55

Peter Mortensen

30,030
21
100
124

answered Apr 15 '20 at 06:43

HarshaV92

1

score 0 · Answer 18 · edited Apr 17 '21 at 16:58

In Windows PowerShell the ExecutionPolicy is set to 'restricted' by default. This does not allow scripts to be run in PowerShell.

We can only run scripts when the ExecutionPolicy is set to 'RemoteSensing' from 'Restricted' You can follow the video "PowerShell 08 - Changing the execution policy so you can run scripts" to do that!

After the above step, you can directly type "Scrits/activate" (while being in the directory of the virtual environment that you want to activate) to activate the virtual environment that you wish to activate!

Example

score 0 · Answer 19 · edited Apr 17 '21 at 17:00

0

If you have used pipenv in creating your virtual environment, you should run pipenv shell before executing any command in the Visual Studio Code terminal.

edited Apr 17 '21 at 17:00

Peter Mortensen

30,030
21
100
124

answered Aug 11 '20 at 07:35

Gimnath

518
5
11

'virtualenv' won't activate on Windows

19 Answers19

Linked

Related