PowerShell script is not digitally signed
- When you try to run a PowerShell script that has not been signed by Trusted Publisher, you may get the following security error.
<PowerShell Script file> is not digitally signed. You cannot run
this script on the current system. For more information about running scripts and setting execution policy, see
about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.
2. How to resolve the error PowerShell script is not digitally signed?
There are some resolutions for this issue. You can sign the PowerShell script that you want to run, change the execution policy, bypass the policy or unblock the file so that it can run once on that session.
- Change Execution Policy Permanently
Set-ExecutionPolicy -ExecutionPolicy unrestricted
- Change Execution Policy Temporarily
Set-ExecutionPolicy -ExecutionPolicy ByPass
Below is the detail of the acceptable values for -ExecutionPolicy parameter:
- Restricted. Does not load configuration files or run scripts. Restricted is the default execution policy.
- AllSigned. Requires that all scripts and configuration files be signed by a trusted publisher, including scripts that you write on the local computer.
- RemoteSigned. Requires that all scripts and configuration files downloaded from the Internet be signed by a trusted publisher.
- Unrestricted. Loads all configuration files and runs all scripts. If you run an unsigned script that was downloaded from the Internet, you are prompted for permission before it runs.
- Bypass. Nothing is blocked and there are no warnings or prompts.
- Undefined. Removes the currently assigned execution policy from the current scope. This parameter will not remove an execution policy that is set in a Group Policy Scope.
You need to login in order to like this post: click here