Warm tip: This article is reproduced from stackoverflow.com, please click
asp.net-mvc nuget powershell

Nuget give this error "ps1 cannot be loaded because running scripts is disabled"

发布于 2020-04-11 22:46:14

I have a new empty MVC 5 project, and I try to install Nuget packages. When I insert in the Nuget Console the command :Update-Package I got the following asnwer: 

File E:\WebApp\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.0\tools\uninstall.ps1 cannot be loaded because running scripts is 
disabled on this system. For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.At line:1 char:3
+ & 'E:\WebApp\packages\Microsoft.CodeDom.Providers.Dot ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess

then I start to install some new packages and got again this message:

WebApp\packages\Modernizr.2.8.3\tools\install.ps1 cannot be loaded because running scripts is disabled on this system

I saw some posts related with this message, but not related with MVC projects.

My question is:

Why I get those messages?

What can I do to fix this issue?

This issue, can appear on the server where my application will run? Some scripts to not run as expected?

Questioner
Lucian Bumb
Viewed
60
分享
♦ 2019-12-31 03:33

I guess the specific package you are trying to install needs to run a Powershell script and for some reason, Powershell execution is disabled on your machine. You can search google on "how to enable Powershell" for a complete guide but generally, it goes like this:

  • Open up a Powershell command window (just search for Powershell after pressing windows start button)
  • Check out current restrictions by typing Get-ExecutionPolicy
  • Enable PowerShell by typing Set-ExecutionPolicy remotesigned

This issue does not affect the server you are planing to install your application on.

JayPex 2016-11-06 07:19:13

@RosdiKasim Same here, solution did not work for me. Any idea hot to tackle this?

Richard Marskell - Drackir 2018-02-17 00:25:31

Running VS as administrator worked for me. Same issue as Rosdi above.

Claire Furney 2018-05-16 23:47:47

I had to run PowerShell (x86) version in order for VS to pick up the new policy.

Related issues

1
Error-Handle powershell command in Batch File
2
Powershell accessing multiple parameters in a for loop
3
Checking a cell in a spreadsheet for blank values
4
Call Python script per PowerShell & passing PSObject and return the parsed data
5
Move subfolder elsewhere and rename based on parent using PowerShell
6
Using WPF to populate a data grid and adding checkboxes to apply a filter
7
How to get the process start time in PowerShell
8
I cant format the output of this command correctly
9
Nuget.exe push **\*.nupkg & Azure DevOps Artifacts
10
PowerShell 7.1, How do I Get Aliases from a List of Functions Names