Quantcast
Channel: The Official Scripting Guys Forum! forum
Viewing all articles
Browse latest Browse all 15028

PowerShell Scripts No Longer Working - Execution Policy Set to RemoteSigned

$
0
0

Hello all,

I have something weird going on that I have noticed in the last few days or so.  I have quite a few .ps1 scripts that I have created that I have stored in a folder on my desktop.  The execution policy for my system has been set to remotesigned for both current user and local machine for a while now.  I guess about a week ago I noticed that when I tried to run one of these scripts (that I have already ran several times before), it gives me an error about it not being digitally signed. 

Naturally, the first thing I verified was the execution policy, which is still set to remotesigned. 

I am running from the same elevated prompt that I always have.  If I just run commands from the ISE without saving it works, but as soon as I save, it stops working saying not digitally signed.

I did make an attempt to create my own signing certificate but gave up after it seemed to be to much trouble than I had to time to address.  Could this half-way attempt be the cause for my scripts to stop working all of a sudden?

Also, is there a way to verify whether it is a GPO that is preventing me from running them?

EDIT: Just ran Get-Item -Stream on script folder path.  All scripts contained in the folder have $DATA stream.

ERROR I RECEIVE:

File C:\Users\MyName\Desktop\PowerShell_Scripts\ScriptAssortment.ps1 cannot be loaded. The file C:\Users\MyName\Desktop\PowerShell_Scripts\ScriptAssortment.ps1is not digitally signed. The script will not execute on the system. For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.

Thanks in advance.



    + CategoryInfo          : SecurityError: (:) [], ParentContainsErrorRecordException

    + FullyQualifiedErrorId : UnauthorizedAccess


Viewing all articles
Browse latest Browse all 15028

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>