Share this article
This article is translated in
Improve this guide
How to Fix PowerShell is Not Digitally Signed Error: 5 Ways
Changing the Execution Policy is the easiest way to fix this issue
3 min. read
Updated onJuly 30, 2024
updated onJuly 30, 2024
Share this article
This article is translated in
Improve this guide
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
Resolve multiple Windows PC issues and speed up your PC effortlessly with specialized software.
If you have tried to run a PowerShell script that isn’t signed, you’ve likely stumbled upon the followingerror is not digitally signed. You cannot run this script on the current system.
Windows PowerShell is a shell initially developed by Microsoft fortask automationand 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
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
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
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.
4. Update Powershell
5. Use Group Policy Editor to allow scripts
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 knowhow 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
Radu Tyrsina
Radu Tyrsina has been a Windows fan ever since he got his first PC, a Pentium III (a monster at that time).
For most of the kids of his age, the Internet was an amazing way to play and communicate with others, but he was deeply impressed by the flow of information and how easily you can find anything on the web.
Prior to founding Windows Report, this particular curiosity about digital content enabled him to grow a number of sites that helped hundreds of millions reach faster the answer they’re looking for.
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Radu Tyrsina
