Location:
State:
Carrier
Country
Status

Cannot Set Execution Policy in Powershell


Did not experience this problem until this build (10130) but it may have occurred in the build before that also. As you can see in the attachment, I am in Administrator mode but cannot run a script which installs a dozen or so programs. The programs install if I type a "one-liner" (install-package audacity cyberfox malwarebytes etc.).
Anyone else experiencing same problem? Any suggestions?

Rich

Edit: This was a clean install from ISO downloaded from Microsoft site.

Rich, have a look here and see if it helps


Did you try running the command through an elevated command prompt?

Rich, have a look here and see if it helps

Kari helped me out previously - that is how I got started with Powershell. Thanks for response!

Did you try running the command through an elevated command prompt?
Yup but thanks.........


try using a capital U as in Unrestricted

try using a capital U as in Unrestricted
No dice

No dice
That's how I saw it in a TechNet tutorial and thought maybe it was a case sensitive letter problem. Sorry it wasn't it.

Kari helped me out previously - that is how I got started with Powershell. Thanks for response!
Sorry about that, didn't read through and see you have already posted there. Maybe try reducing the number of apps will help as that has caused an error before.

One reminder though, after you set the ExePol to unrestricted and have run your script don't forget to reset it to either Remote Signed(to execute simple everyday scripts such as powershell"(Get-WmiObject -query ‘select * from SoftwareLicensingService’).OA3xOriginalProductKey"
Or better yet if you don't use it often,, set it back to restricted. There is malware that can get access to PowerShell and then it'll have total access to your system.

Cannot Set Execution Policy in Powershell