Skip to main content

How to fix PowerShell script error: "The script is not digitally signed. You cannot run this script on the current system."

Every now and then, when I attempt to run a PowerShell script, I encounter the following error. This error prevents me from running the scripts necessary for tasks such as setting up a local development environment.

PowerShell script error

.\node-environment-setup.ps1 : File
D:\git\repos\ProjectName\Website\ProjectName.Shared.Frontend\build_utilities\node-environment-setup.ps1 cannot be loaded. The
file D:\git\repos\ProjectName\Website\ProjectName.Shared.Frontend\build_utilities\node-environment-setup.ps1 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 https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ .\node-environment-setup.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess

A quick fix: Updating the ExecutionPolicy of the Process Scope

Below are the four steps to fix this error:
  1. Run Windows PowerShell as an Administrator.
  2. Run your PowerShell script and see the error mentioned above.
  3. Run Get-ExecutionPolicy -List command to display the execution policies for each scope in the order of precedence. See that Process scope's ExecutionPolicy is set to Undefined.
  4. Run Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass command to update the ExecutionPolicy of Process scope to Bypass. Type A to select the "Yes to All" option.
  5. Run Get-ExecutionPolicy -List command again to check that the Process scope's ExecutionPolicy is set to Bypass.
  6. Run your PowerShell script again, you shouldn't see the same error message again.
  7. Once you're done with running your script, set the Process scope's ExecutionPolicy to back to Undefined again by running this command: Set-ExecutionPolicy -Scope Process -ExecutionPolicy Undefined


Labels:

Comments

Post a Comment

Popular posts from this blog

How to fix Git push error: "RPC failed; curl 56 HTTP/2 stream 7 was reset send-pack: unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly"

Problem Today I saw the following problem when I tried to push my changes to a Git server after doing some work for upgrading an Umbraco v7 project to v8.18.8.  Possible reasons After some investigations, it seems like this could be because of the following reasons; Git is not happy with the amount of changes that are being pushed into the server.  There are possible limitations on the server about the size/amount of files that you can push. Your internet connection is not good and stable enough. Your Git client's version is old. Solution options For me, the easiest option was connecting to another Wifi and trying again. Apparently, this option helped quite a few people, so it is worth giving it a try. Unfortunately, it didn't work for me. A bad internet connection wasn't an option for me either, as my internet is pretty fast (500 Mbps). Similarly, my Git client version was the latest version (git version 2.41.0.windows.3).  On StackOverflow, there were a lot of recommend...
Post a Comment
Read more

How to fix "Microsoft SQL Error SQL71564: Error validating element [USERNAME]: The element [USERNAME] has been orphaned from its login and cannot be deployed."

I needed to export a database in BACPAC format today in order to restore it somewhere else, and I encountered the following error. To resolve this issue, I deleted all of the users mentioned in the error log. After successfully creating the BACPAC file, I used it to create a new database with no problems. Error: TITLE: Microsoft SQL Server Management Studio ------------------------------ One or more unsupported elements were found in the schema used as part of a data package. Error SQL71564: Error validating element [USER1]: The element [USER1] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER2]: The element [USER2] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER3]: The element [USER3] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER4]: The element [USER4] has been orphaned from its login and cannot be deployed. Error SQL71...
Post a Comment
Read more

How to use JQuery Ajax Methods for Async ASP.NET MVC Action Methods

Making repeatedly calls to async methods can be a nightmare. In this case, it makes sense to use 2 ajax methods, instead of one. Here is a simple solution to overcome this problem. See that  ajaxcalls   is emptied after the success response for the first ajax call and then the second ajax method is used to make one single call to the async action method. Hope it helps. View: @section Scripts{     < script type ="text/javascript">         var smartDebitObject = new Object();         smartDebitObject.MembershipNumber = $( "#MembershipNumber" ).val();         smartDebitObject.ProfileId = $( "#ProfileId" ).val();         smartDebitObject.FirstName = $( "#FirstName" ).val();         smartDebitObject.LastName = $( "#LastName" ).val();     ...
Post a Comment
Read more