Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Pourquoi my locally-created script not allowed vers exécuter under the RemoteSigned execution policy?

ayi

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:
<ul>
<li>
This is not a "Why won’t my default installation of PowerShell run scripts?" question.
</li>
<li>
This is not a "Why won’t my installation of PowerShell run scripts downloaded from the internet?" question.
</li>
<li>
The question is why the <code>RemoteSigned</code> execution policy is preventing script execution when it shouldn’t.
</li>
<li>
<code>RemoteSigned</code> 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.
</li>
<li>
The execution policy is already set to <code>RemoteSigned</code>. Changing it from <code>RemoteSigned</code> to <code>RemoteSigned</code> is not a solution.
</li>
<li>
The script file is created and stored locally.
</li>
<li>
The script file is not blocked. The script file was never blocked (see previous point).
</li>
<li>
The script file cannot be unblocked because there is nothing to unblock (see previous point).
</li>
<li>
The script file is (attempted to be) executed by an administrator.
</li>
<li>
Windows PowerShell is the only application involved. Not Windows PowerShell ISE nor Command Prompt nor any other tools or 
editors are relevant.
</li>
<li>
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.
</li>
</ul>
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:
<pre><code class="lang-auto">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 <<<<
- CategoryInfo : NotSpecified: (🙂 [], PSSecurityException
- FullyQualifiedErrorId : RuntimeException

</code></pre>
I am both a domain administrator and a local administrator, and if I run <code>Get-ExecutionPolicy -List</code>, I can see that the Group Policy Object I created to configure PowerShell is correctly applying the <code>RemoteSigned</code> execution policy at the machine level:
<pre><code class="lang-auto"> Scope ExecutionPolicy

MachinePolicy RemoteSigned
UserPolicy Undefined
Process Undefined
CurrentUser Undefined
LocalMachine Undefined

</code></pre>
I created the script myself in Notepad, and used the <a href="https://www.sysinternals.com/" rel="noopener nofollow ugc">Sysinternals</a>’ <a href="https://learn.microsoft.com/sysinternals/downloads/streams" rel="noopener nofollow ugc">Streams</a> 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 <code>Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope LocalMachine</code> then the local script is still not allowed to execute, which makes sense since the execution policy at the <code>MachinePolicy</code> scope will take precedence.
As documented by <code>about_Execution_Policies</code>(<a href="https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_execution_policies" rel="noopener nofollow ugc">current</a>; <a href="https://technet.microsoft.com/library/dd347641.aspx" rel="noopener nofollow ugc">at time of question</a>), the <code>RemoteSigned</code> policy means:
<ul>
<li></li>
</ul>
Scripts can run.
<ul>
<li></li>
</ul>
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).
<ul>
<li></li>
</ul>
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).
<ul>
<li></li>
</ul>
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…
<ul>
<li>
Why is my script not being allowed to run?
</li>
<li>
Why does PowerShell complain that my script "is not digitally signed" when that requirement should only apply to files from the Internet?
</li>
<li>
Why does PowerShell no longer care about the script not being signed when it’s run from a network share?
</li>
</ul>
<hr>
Source : <a href="https://www.sysinternals.com/" rel="noopener nofollow ugc">Stack Overflow</a>’)

ayi_2

Some things to check:
Can you change to unrestricted?
<pre><code class="lang-auto">Set-ExecutionPolicy Unrestricted

</code></pre>
Is the group policy set?
<ul>
<li>
<code>Computer Configuration\Administrative Templates\Windows Components\Windows PowerShell</code>
</li>
<li>
<code>User Configuration\Administrative Templates\Windows Components\Windows PowerShell</code>
</li>
</ul>
Also, how are you calling Script.ps1?
Does this allow it to run?
<pre><code class="lang-auto">powershell.exe -executionpolicy bypass -file .\Script.ps1

</code></pre>