Windows 10: Can't change setting developer for powershell to run unsigned scripts?

I tried that and it did not work. Even when I flipped the switch to ON it remains grayed out, but I don't know why. I also tried to do it through the Group Policy Settings on Computer Configuration / Administrative Templates / Windows Components / Windows PowerShell / Turn On Script Execution, enabling Allow all scripts. Then forced update with gupdate /force.That didn't work either. In PowerShell, Get-ExecutionPolicy displays as Unrestricted. I still get "The file you are trying to run is 'Not-signed'...you cannot run this script on the current system." I'm trying to install PSTree from the P

:)

 

PowerShell scripts not working with Call operator

Hi,



Thank you for writing to Microsoft Community Forums.



I understand that you are facing issues while developing a PowerShell script using the Call operator. I would suggest you to refer the articles

The Windows PowerShell ISE.



However, as the issue is related to developing PowerShell scripts, I would suggest you to post your query on

MSDN forums, where we have expertise and developers who are well equipped with the knowledge of developing PowerShell scripts in Windows.



Regards,

Prakhar Khare

Microsoft Community – Moderator

 

Powershell / Batch scripts do NOT run!

Please help me. I have written some powershell and batch scripts, yet when I run those files, they don't run. At most the powershell script just does step #1 but not all the other steps (lines of code / instructions). The batch script .bat file doesn't do anything. Both just pop up for like 2 seconds and then they disappear, Task Manager says nothing's being done.

 

Run PowerShell Script As An Administrator

Of course, there is always the elevating shortcut method. This requires one extra step compared to setting up such a shortcut for a batch file.

1 Create a shortcut to your PS1 file [by, for example, dragging it with the Alt key pressed]
2 Right click on the shortcut & select Properties
2.1 At the start of the target field, type in powershell.exe then a space to separate it from the script's path-name
2.2 Click on the Advanced button & set the Run as Admin checkbox.
2.3 OK, OK
{you will notice the shortcut's icon change when you do this}

You can now double-click on the shortcut instead of your original script and it will run as Admin [after the normal Admin challenge].

The extra step compared to doing this for batch files is 2.1. Batch files can be set to run as Admin without having to job the Target field.

Denis