Why is my locally-created script not allowed to run under the RemoteSigned execution policy

Question

Since this question continues to attract responses that are either   refuted by the question body or don t address the actual problem    please read this simple summary of what you need to know          This is not a  Why won t my default installation of PowerShell run scripts   question    This is not a  Why won t my installation of PowerShell run scripts downloaded from the internet   question    The question is why the RemoteSigned execution policy is preventing script execution when it shouldn t    RemoteSigned is the only execution policy I want to use   I am aware that other  less-restrictive policies are available   If   those policies were acceptable substitutes I would have just used them   instead and this question wouldn t exist    The execution policy is already set to RemoteSigned   Changing it from RemoteSigned to RemoteSigned is not a solution    The script file is created and stored locally    The script file is not blocked   The script file was never blocked  see previous point     The script file cannot be unblocked because there is nothing to unblock   see previous point     The script file is  attempted to be  executed by an administrator    Windows PowerShell is the only application involved   Not Windows PowerShell ISE nor Command Prompt nor any other tools or   editors are relevant    The cause of the problem has already been identified  see accepted answer    After nearly 8 years  I think all other obvious   explanations  whether applicable or not  have been posted  too   If   you think otherwise then please read the question and existing   answers in their entirety before adding yours         I am using Windows PowerShell 2 0 on 64-bit Windows 7 Professional  I have a script on my Desktop that causes the following error when I try to run it   File C  Users UserName Desktop Script ps1 cannot be loaded  The file C  Users UserName Desktop Script ps1 is not digitally signed  The script will not execute on the system   Please see  get-help about signing  for more details   At line 1 char 54   C  Users UserName Desktop TestGetWindowsUpdateLog ps1  lt  lt  lt  lt        CategoryInfo            NotSpecified          PSSecurityException       FullyQualifiedErrorId   RuntimeException   I am both a domain administrator and a local administrator  and if I run Get-ExecutionPolicy -List  I can see that the Group Policy Object I created to configure PowerShell is correctly applying the RemoteSigned execution policy at the machine level           Scope ExecutionPolicy         ----- --------------- MachinePolicy    RemoteSigned    UserPolicy       Undefined       Process       Undefined   CurrentUser       Undefined  LocalMachine       Undefined   I created the script myself in Notepad  and used the Sysinternals  streams utility and the file Properties dialog to confirm that the script is not being treated as having come from the internet  If I copy the script to a network share on a domain server  then it s allowed to execute  If I run Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope LocalMachine then the local script is still not allowed to execute  which makes sense since the execution policy at the MachinePolicy scope will take precedence   As documented by about Execution Policies current  at time of question   the RemoteSigned policy means         Scripts can run    Requires a digital signature from a trusted publisher on scripts and configuration files that are downloaded from the Internet    including e-mail and instant messaging programs     Does not require digital signatures on scripts that you have run and that you have written on the local computer  not downloaded from   the Internet     Risks running unsigned scripts from sources other than the Internet and signed  but malicious  scripts       My script is not signed  but since it is both created and executed locally  it should satisfy the third bullet point above   Therefore      Why is my script not being allowed to run  Why does PowerShell complain that my script  is not digitally signed  when that requirement should only apply to files from the Internet  Why does PowerShell no longer care about the script not being signed when it s run from a network share

User · Answer

Select your terminal Command prompt instead of Power shell  That should work

User · Answer

Please make a backup for the script bs1 file  What works for me was deleting the script bs1 file and running the execution command

User · Answer

I finally tracked this down to  NET Code Access Security   I have some internally-developed binary modules that are stored on and executed from a network share   To get  NET 2 0 PowerShell 2 0 to load them  I had added a URL rule to the Intranet code group to trust that directory   PS gt   amp    Env SystemRoot Microsoft NET Framework64 v2 0 50727 caspol exe  -machine -listgroups Microsoft  R   NET Framework CasPol 2 0 50727 5420 Copyright  c  Microsoft Corporation   All rights reserved   Security is ON Execution checking is ON Policy change prompt is ON  Level   Machine  Code Groups   1   All code  Nothing     1 1   Zone - MyComputer  FullTrust         1 1 1   StrongName -      FullTrust         1 1 2   StrongName -      FullTrust     1 2   Zone - Intranet  LocalIntranet         1 2 1   All code  Same site Web         1 2 2   All code  Same directory FileIO -  Read  PathDiscovery          1 2 3   Url - file   Server Share Directory WindowsPowerShell Modules    FullTrust     1 3   Zone - Internet  Internet         1 3 1   All code  Same site Web     1 4   Zone - Untrusted  Nothing     1 5   Zone - Trusted  Internet         1 5 1   All code  Same site Web   Note that  depending on which versions of  NET are installed and whether it s 32- or 64-bit Windows  caspol exe can exist in the following locations  each with their own security configuration  security config      Env SystemRoot Microsoft NET Framework v2 0 50727   Env SystemRoot Microsoft NET Framework64 v2 0 50727   Env SystemRoot Microsoft NET Framework v4 0 30319   Env SystemRoot Microsoft NET Framework64 v4 0 30319    After deleting group 1 2 3      PS gt   amp    Env SystemRoot Microsoft NET Framework64 v2 0 50727 caspol exe  -machine -remgroup 1 2 3  Microsoft  R   NET Framework CasPol 2 0 50727 9136 Copyright  c  Microsoft Corporation   All rights reserved   The operation you are performing will alter security policy  Are you sure you want to perform this operation   yes no  yes Removed code group from the Machine level  Success      I am left with the default CAS configuration and local scripts now work again   It s been a while since I ve tinkered with CAS  and I m not sure why my rule would seem to interfere with those granting FullTrust to MyComputer  but since CAS is deprecated as of  NET 4 0  on which PowerShell 3 0 is based   I guess it s a moot point now

User · Answer

Is the file being blocked  I had the same issue and was able to resolve it by right clicking the  PS1 file  Properties and choosing Unblock

User · Answer

Run below 2 commands in PowerShell window    Set-ExecutionPolicy unrestricted Unblock-File -Path D  PowerShell Script ps1

User · Answer

I have found out when running a PS1 file for a Mapped drive to Dropbox that I m always getting this error   When opening up properties for the PS1 there is no  Unblock    The only thing that work for me is  powershell exe -executionpolicy bypass -file   Script ps1

User · Answer

What works for me was right-click on the  ps1 file and then properties  Click the  UNBLOCK  button  Works great fir me after spending hours trying to change the policies

User · Answer

Try running the Powershell GUI as Administrator

User · Answer

This is an IDE issue  Change the setting in the PowerShell GUI  Go to the Tools tab and select Options  and then Debugging options  Then check the box Turn off requirement for scripts to be signed  Done

User · Answer

If the file is copied from a network location  that is  another computer  Windows might have blocked that file  Right click on the file and click on the unblock button and see if it works

User · Answer

this code line was working in Ubuntu with virtualbox and with Win 10 as a virtual os   inside of the powershell Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser  If it is not working I recomand to read this resources below   Set-ExecutionPolicy Module  Microsoft PowerShell Security Sets the PowerShell execution policies for Windows computers  https   docs microsoft com en-us powershell module microsoft powershell security set-executionpolicy view powershell-7 1    text To 20change 20the 20execution 20policy Get 2DExecutionPolicy 20with 20no 20parameters  https   docs microsoft com en-us powershell module microsoft powershell security get-executionpolicy view powershell-7 1 Get-ExecutionPolicy -List  https   devblogs microsoft com scripting hey-scripting-guy-how-can-i-sign-windows-powershell-scripts-with-an-enterprise-windows-pki-part-2-of-2

User · Answer

Some things to check   Can you change to unrestricted   Set-ExecutionPolicy Unrestricted   Is the group policy set    Computer Configuration Administrative Templates Windows Components Windows PowerShell User Configuration Administrative Templates Windows Components Windows PowerShell   Also  how are you calling Script ps1   Does this allow it to run   powershell exe -executionpolicy bypass -file   Script ps1

User · Answer

I was having the same issue and fixed it by changing the default program to open  ps1 files to PowerShell  It was set to Notepad

User · Answer

When you run a  ps1 PowerShell script you might get the message saying     ps1 is not digitally signed  The script will not execute on the system     To fix it you have to run the command below to run Set-ExecutionPolicy and change the Execution Policy setting  Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

[powershell] Why is my locally-created script not allowed to run under the RemoteSigned execution policy?

Examples related to powershell

Examples related to powershell-2.0

Examples related to code-signing

Examples related to executionpolicy