How to Fix PowerShell is Not Digitally Signed Error: 3 Ways

Changing the Execution Policy is the easiest way to fix this issue

Reading time icon 3 min. read

Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

Key notes

  • If you are troubled by the PowerShell script is not digitally signed issue, it might be because your Execution Policy is restricted.
  • You can get past this error by unblocking the downloaded script using a command.
  • Another effective solution is to change your Execution Policy to Unrestricted.
powershell not digitally signed

If you have tried to run a PowerShell script that isn’t signed, you’ve likely stumbled upon the following error <PowerShell Script file> is not digitally signed. You cannot run this script on the current system.

Windows PowerShell is a shell initially developed by Microsoft for task automation and configuration management. There’s no wonder that its Execution Policy is set to Restricted, which protects from running malicious scripts.

If you’d like to sign the script and solve this, here are a few methods that may help.

How do I make a PowerShell script digitally signed?

1. Check and change the Execution Policy

  1. Press the Windows key, type powershell, and click Run as administrator under Windows PowerShell.
    powershell powershell not digitally signed
  2. Next, type the command below and hit Enter to check your Executions policy: Get-ExecutionPolicy
  3. Check if your policy is set to Restricted.
  4. Now, type the command below and press Enter to set it to unrestricted: Set-ExecutionPolicy -ExecutionPolicy unrestrictedset
  5. Finally, press Y to confirm the change and wait for the command to finish running.

The first thing to do if your PowerShell script is not digitally signed is to change your Execution. This removes the restrictions preventing your script from running and lets you run all types of scripts.

2. Bypass the current PowerShell session

  1. Press the Windows key + X and select Windows PowerShell (Admin).
  2. Type the commands below and hit Enter to run it: Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypassbypass powershell not digitally signed
  3. Wait for the command to finish running.

Another quick fix for the PowerShell script file is not digitally signed issue is to set the execution policy to bypass the current PowerShell session. Even better, these settings will be lost once you close this PowerShell session.

3. Unblock the file that was downloaded

  1. Right-click the Start icon and select Windows PowerShell (Admin).
  2. Type the command below and hit Enter: PS C:> Unblock-File -Path C:Downloadsscript1.ps1unblock
  3. Finally, wait for the command to finish running and run the script again.

When the Execution Policy is RemoteSigned, this requires that all scripts and configuration files downloaded from the Internet or emails are signed by a trusted publisher.

If you trust the script’s contents are safe, you can unblock it to run on your session. The easiest way to do this is to use the Unblock-File cmdlet, as shown above.

There you have it. With the three solutions in this guide, you should be able to get rid of the PowerShell script not digitally signed error.

If you want to know how to stop PowerShell from closing after running a script, check our detailed guide to do it easily.

Feel free to let us know the solution that helped you fix this issue in the comments below.

More about the topics: error, Microsoft PowerShell