prijon.net

script.ps1 is not digitally signed. The script will not execute  on the system. Please see “get-help about_signing” for more details.

To solve the problem, you can just change the Execution policy to “RemoteSigned” with the folowing command (as Administrator):
Set-ExecutionPolicy RemoteSigned   -   Note that this option is not recomanded!

The more secure way is to digitaly sign the script.

1. Navigate to the location of your code signing certificate (like “Set-Location cert:\CurrentUser\my\” for Personal certificates).
2. Type Get-CilldItem to get a list of all certificates in thihs location and copy the Thumbprint of the right certificate.
3. Set the ”$cert” with the certificate location:

$cert = Get-Childitem -Path cert:\CurrentUser\My\A4309AD8067D6AC70E36B578A890A1EFC3FB -CodeSigningCert

    4.    Now with the folowing command digitaly sign the file
            (ex.: Powershell profile)

Set-AuthenticodeSignature -FilePath C:\…\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 -cert $cert

If you want that Powershell remember your aliases (and other commands) like “gh for Get-Help”,
you can create a Powershell profile script, which is automaticali executed at Powershell startup

1. First test if a profile exist with the folowing command:
   test-path $profile
   
2. If the resulte is false, use the folowing command to create a new profile
   new-item -path $profile -itemtype file -force
   
3. Type notepad $profile to edit the pprofile
4. Now you can write down all yours commands (ex. Set-Alias gh Get-Help)
   

To view the location of the profile script type $profile