From eec631192232a0079698ea27255e84fee46485ad Mon Sep 17 00:00:00 2001
From: Austin Rognes <acrognes@iastate.edu>
Date: Sat, 29 Feb 2020 02:02:00 -0600
Subject: [PATCH] Add instructions for PowerShell execution policy access

---
 Shell-aliases.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/Shell-aliases.md b/Shell-aliases.md
index c7c44b8..26809ba 100644
--- a/Shell-aliases.md
+++ b/Shell-aliases.md
@@ -51,6 +51,22 @@ Add this line **before** the line above in your Powershell `$PROFILE` on Windows
 $env:PYTHONIOENCODING="utf-8"
 ```
 
+To overcome PowerShell not running scripts, for which the error looks as such:
+
+```
+. : File C:\Windows\System32\WindowsPowerShell\v1.0\profile.ps1 cannot be loaded because running scripts is disabled
+on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
+At line:1 char:3
+```
+
+You could set execution policy to unrestricted through the PowerShell command:
+
+```
+Set-ExecutionPolicy unrestricted
+```
+
+[Click here](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-7) to read more about Microsoft's execution policies.
+
 # tcsh
 
 ```tcsh