Is Not Digitally Signed Powershell

Other Programming Languages

Have you ever encountered the error message “This script is not digitally signed” when running a PowerShell script? If so, you’re not alone. This is a common issue that many PowerShell users face, and it can be quite frustrating. In this article, I will explain what it means for a script to be digitally signed, why PowerShell displays this error message, and how you can resolve it.

Firstly, let’s talk about what it means for a script to be digitally signed. When a script is digitally signed, it means that a cryptographic signature has been applied to the script file. This signature is generated using a digital certificate, which verifies the authenticity and integrity of the script. In simple terms, it provides a way to ensure that the script has not been tampered with and that it comes from a trusted source.

Now, let’s delve into why PowerShell displays the “This script is not digitally signed” error message. PowerShell has a security feature called Execution Policy, which determines what scripts can be run on a system. By default, the Execution Policy is set to “Restricted,” which means that no scripts are allowed to run. This is done to protect the system from running potentially malicious scripts.

When you try to run a script that is not digitally signed, PowerShell considers it to be a potential security risk and blocks its execution. This is why you see the error message. PowerShell wants to ensure that you are aware of the potential risks before running an unsigned script.

So, how can you resolve this issue and run your PowerShell script? There are a few options available to you:

Option 1: Change the Execution Policy

The most straightforward solution is to change the Execution Policy to allow the execution of unsigned scripts. However, it is important to note that this may introduce security risks, as any script on your system, including potentially malicious ones, will be allowed to run. To change the Execution Policy, open a PowerShell console with administrative privileges and run the following command:

Set-ExecutionPolicy Unrestricted

This will set the Execution Policy to “Unrestricted,” allowing the execution of unsigned scripts. Use this option only if you trust the scripts that you are running.

Option 2: Digitally Sign the Script

If you have created the script yourself or have access to the source code, you can digitally sign the script. This involves obtaining a digital certificate and using it to sign the script file. Once the script is signed, PowerShell will recognize it as a trusted script and allow its execution. There are several resources available online that provide guidance on how to sign PowerShell scripts.

Option 3: Bypass the Execution Policy

If you encounter this error message while running a script that you trust, and you don’t want to change the Execution Policy or sign the script, you can bypass the Execution Policy for a single session. To do this, open a PowerShell console and run the following command:

powershell -ExecutionPolicy Bypass

This will open a new PowerShell session with the Execution Policy bypassed. You can then run your script within this session without encountering the “This script is not digitally signed” error.


The “This script is not digitally signed” error message in PowerShell can be an obstacle when running scripts. However, by understanding the concept of digital signatures and the purpose of the Execution Policy, you can take appropriate measures to address this issue. Whether you choose to change the Execution Policy, digitally sign the script, or bypass the Execution Policy for a single session, it is important to consider the security implications and make an informed decision.