How to solve this issue, failed to load due to software restriction?

Question

0.00/5 (No votes)

See more:

Hi team

I have an issue almost 2 weeks and want to share this problem perhaps i could get an insight of it. The issue is when i try to launch my IDE visual studio either as Admin nor normal. Nu-get console get this weird exception and dont know if its an administration issue or software related problem like virus.

C#

<pre>& : File C:\Users\gcobanim\source\repos\eNtsaRegistrationTraining\packages\Microsoft.EntityFrameworkCore.Tools.3.1.3\tools\init.ps1 cannot be loaded because its operation
is blocked by software restriction policies, such as those created by using Group Policy.

What I have tried:

Update-Database;
Install-Microsoft.EntityFrameworkCore.Tools;
-Failed to run as console states its already running.

Posted 2-Jun-20 2:34am

gcogco10

Updated 2-Jun-20 2:42am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

phil.o · Answer 1 · 2020-06-02T02:43:00

Solution 1

Maybe a PowerShell execution policy issue. Try to issue the following command on a PowerShell window:

PowerShell

Set-ExecutionPolicy Unrestricted -Scope CurrentUser

You might have to logout/login to see the change applied to your user session.

Posted 2-Jun-20 2:43am

phil.o