Activating an environment fails because running powershell scripts is disabled by default on Windows

[qubitron]

Environment data

• VS Code version: 1.27.1 (user setup)
• Extension version (available under the Extensions sidebar): 2018.8.0
• OS and version: Windows 10
• Python version (& distribution if applicable, e.g. Anaconda): Python 3.7..0
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
• Relevant/affected Python packages and their versions: N/A

Actual behavior

Creating a new terminal in a fresh Windows install results in a powershell error

PS C:\dev\loadtest> & c:/dev/loadtest/env/Scripts/activate.ps1
& : File C:\dev\loadtest\env\Scripts\activate.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:3
+ & c:/dev/loadtest/env/Scripts/activate.ps1
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess

Expected behavior

I don't need need to disable running scripts in able to use VS code

Steps to reproduce:

1. Fresh install of windows
2. install python
3. create virtual environment
4. try to activate it in VS Code

[d3r3kk]

Hmmm.. this feels like it might be a VSCode problem.

To fix the issue, you can simply open a Powershell window as administrator and type the following:

Set-ExecutionPolicy RemoteSigned

And hit enter, respond y to any prompts that appear.

[d3r3kk]

I take it back - we are running an activate.ps1 file from a .venv!

Hmmm... not sure what we can do about this from the extension's perspective. @DonJayamanne can we inject some powershell code prior to running activate.ps1 when we launch a python terminal?

[DonJayamanne]

can we inject some powershell code prior to running activate.ps1 when we launch a python terminal?

Yes we can.
Changing the label, as this isn't a bug. we're trying to improve the UX for users of the extension.

@d3r3kk
Your original suggestion works, changing the policy will work, however @qubitron doesn't want to have to do it manually.
Basically we should do what ever we can to remove/reduce such road blocks.

[d3r3kk]

Yep, that's pretty standard Powershell behaviour/expected workflow on a new machine. Not sure we should usurp that is what I'm getting at.

However, if we choose to do so, it shouldn't be too difficult to put a quick popup and ask the user if doing so will be ok with them first (much like the powershell cmdlet Set-ExecutionPolicy does).

[DonJayamanne]

However, if we choose to do so, it shouldn't be too difficult to put a quick popup and ask the user if

Agreed.
After all, we're executing some script that we have no control over.

@qubitron thoughts

[qubitron]

1. This will require elevation to set the execution policy correct? Not all users have admin rights on the system
2. What if the user doesn't want this execution policy set for security reasons, it's off by default for a reason?

Why do we even need powershell cmdlet to do this, why can't we run a batch file or something else that doesn't require admin privileges/execution policies to be set?

[brettcannon]

It's a PowerShell script because that's how you get the prompt updated to list the virtual environment's name: https://github.com/python/cpython/blob/master/Lib/venv/scripts/nt/Activate.ps1

[brettcannon]

The other option any notification could have is offer to switch off the automatic activation on top of providing instructions on how to change the policy.

[qubitron]

OK, so really this is an issue because we're using a powershell cmd prompt instead of CMD (which is what I use outside of VS Code and just lets me activate without having to set any policies).

Since I assume we can't change the default from powershell to cmd, detecting the issue and prompting users to set the execution policy (with a button) seems like the right solution.

[DonJayamanne]

Well, we could do the following:

• If shell is powershell
• If batch file exists, then shell into CMD and execute bath file
• Else if, powershell script exists, excute powershell script, with the prompts to elevate if necessary.

I.e. where possible use batch files.
This would be better as we wouldn't have to display prompts for powershell script exec elevation...

[brettcannon]

It might also be easier for us to contribute upstream to Python an Activate.ps1 that isn't automatically generated and thus can be signed as necessary.

[JayKayAce]

Just to add to the description of the issue at hand I had same problem using Pipenv virtual environment. Pipenv version: 2018.11.14
VSCode version : 1.29.1

Worked after updating my execution policy from using the following PS cmdlet:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

Here is the link to the documentation on ExecutionPolicy from Microsoft

Cheers

[burakcank]

Not sure if this happens after the latest update but when I execute "Run current file in terminal", it tries to activate the environment that resides in the same directory with the script itself, it fails and afterwards it executes the script with the python interpreter that is inside my environment. How come ?

[d3r3kk]

@burakcank Is the problem due to Powershell permissions not being set? If so, please run (as admin on your system) the Set-ExecutionPolicy as defined above if that is satisfactory for you and your IT department.

If that is not the problem you are seeing, please feel free to open another issue with the specific details of your situation.

[dlech]

I was able to work around this problem by adding the following to my VS Code settings:

"terminal.integrated.shellArgs.windows": ["-ExecutionPolicy", "Bypass"]

[CodeOnYT]

OPEN POWERSHELL IN ADMINISTRATER MODE AND USE THIS COMMANDS
REFERENCE : https://docs.microsoft.com/da-dk/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-5.1

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

`Try the new cross-platform PowerShell https://aka.ms/pscore6`

PS C:\WINDOWS\system32> cd..
PS C:\WINDOWS> cd..
PS C:\> cd d:
PS D:\> Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose
you to the security risks described in the about_Execution_Policies help topic at
https:/go.microsoft.com/fwlink/?LinkID=135170. Do you want to change the execution policy?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "N"): A
PS D:\> Get-ExecutionPolicy
RemoteSigned
PS D:\> Get-ExecutionPolicy -LIST

        Scope ExecutionPolicy
        ----- ---------------
MachinePolicy       Undefined
   UserPolicy       Undefined
      Process       Undefined
  CurrentUser    RemoteSigned
 LocalMachine       Undefined


PS D:\>

I hope your problem is solved
if not then just follow the reference link

[brettcannon]

If https://bugs.python.org/issue37354 can be solved then Activate.ps1 can be signed and thus acceptable in a stricter execution policy.

[saldisucipto]

OPEN POWERSHELL IN ADMINISTRATER MODE AND USE THIS COMMANDS
REFERENCE : https://docs.microsoft.com/da-dk/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-5.1

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

`Try the new cross-platform PowerShell https://aka.ms/pscore6`

PS C:\WINDOWS\system32> cd..
PS C:\WINDOWS> cd..
PS C:\> cd d:
PS D:\> Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose
you to the security risks described in the about_Execution_Policies help topic at
https:/go.microsoft.com/fwlink/?LinkID=135170. Do you want to change the execution policy?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "N"): A
PS D:\> Get-ExecutionPolicy
RemoteSigned
PS D:\> Get-ExecutionPolicy -LIST

        Scope ExecutionPolicy
        ----- ---------------
MachinePolicy       Undefined
   UserPolicy       Undefined
      Process       Undefined
  CurrentUser    RemoteSigned
 LocalMachine       Undefined


PS D:\>

I hope your problem is solved
if not then just follow the reference link

This Work on my windows 10

[d3r3kk]

Watch python/cpython#14967, may even make it into 3.8.

[brettcannon]

@d3r3kk it won't make it into 3.8.

[qubitron]

@luabud @brettcannon we should evaluate other solutions since this won't be fixed within the next 1-2 years on the Python side then. At a minimum, let's make sure to include this step in our getting started docs.

[ozmen1]

This solution worked for me :

1. Start VSCode as Administrator
2. Open the Integrated Terminal
3. Type

> Set-ExecutionPolicy –ExecutionPolicy RemoteSigned

and that's it !

Works like a charm! Thanks!

[kartikpunjabi111]

Checkout https://stackoverflow.com/questions/4037939/powershell-says-execution-of-scripts-is-disabled-on-this-system

[Lamarcke]

This is not a VS Code issue. Powershell blocks any kind of script by default, not only Python's.

[mkoohafkan]

I think this may actually be a working solution via a terminal profile, since it mimics the specifications of the Anaconda PowerShell Prompt shortcut that gets placed in the start menu when Anaconda is installed. Here I've made a "Conda" profile, but you could also add the "args" entry to your default PowerShell profile.

        "Conda": {
            "source": "PowerShell",
            "icon": "terminal-powershell",
            "overrideName": true,            
            "args": ["-ExecutionPolicy",  "ByPass", "-NoExit", "-Command",  "& 'C:\\Anaconda3\\shell\\condabin\\conda-hook.ps1' ; conda activate 'C:\\Anaconda3' "]
        }

EDIT We can create a new configuration setting "python.condaHome" : "C:\\Anaconda3" and insert it into the Conda terminal profile arguments via ${config:python.condaHome}.

This appears to work for non-admin users with "restricted" execution policy.

[karrtikr]

We have a new activation mechanism #11039 which does not require executing any script, hence does not run into this issue, give it a try:

• Use latest version of VS Code and Python extension
• Add the following to User settings and reload window:

  "python.experiments.optInto": ["pythonTerminalEnvVarActivation"]

[Tyriar]

Verification covered by #11039 TPI