Windows 7 / Getting Started

PowerShell Execution Policy

Microsoft has embraced a secure-by-default mindset, and this is reflected in the PowerShell Execution Policy. This policy has several settings that you can modify to allow or disallow the execution of different types of scripts.

If you don't modify the policy, you'll find that each attempt to execute a PowerShell script will result in an error that says, "The execution of scripts is disabled on this system." This message is telling you that the Execution Policy is set to Restricted, the default setting. There are several possible settings for the Execution Policy:

Restricted The Restricted setting prevents any scripts from being executed and is the default setting. You can still execute individual PowerShell commands.

RemoteSigned It's common to change the Execution Policy to RemoteSigned. This will let you execute any scripts on your local system but will prevent scripts that don't have a digital signature from being executed remotely, such as over an Internet connection.

Signed scripts have a digital signature added to them, which is associated with a code-signing certificate from a trusted publisher. The idea is that if a script is signed with a certificate, you can identify the writer. Since malicious scriptwriters don't want to be known or identified, they won't sign their scripts.

AllSigned This is a little more secure than RemoteSigned. While RemoteSigned will allow the execution of unsigned local scripts, AllSigned will not allow the execution of any unsigned scripts. All scripts must be signed.

Unrestricted Just as it sounds, Unrestricted allows the execution of any scripts. This setting will warn you before running scripts that are downloaded from the Internet.

Bypass This is similar to Unrestricted in that it allows the execution of any scripts; however, it does not give any warnings. This would be used when an application is using scripts, and it wouldn't be able to respond to any warnings.

You can use the following script to determine the current setting for the Execution Policy:

Get-ExecutionPolicy

You can change the policy using the Set-ExecutionPolicy cmdlet with the name of the policy. You must be running Windows PowerShell with administrative permissions to change the Execution Policy. How to change the Execution Policy.

[Previous] [Contents] [Next]

In this tutorial:

  1. Working with the Command Prompt
  2. Starting and Ending a Command Prompt Session
  3. Easy ways to invoke administrator Command Prompt sessions
  4. Starting Command Prompt at a Particular Folder
  5. Strings with Spaces Need Quotes
  6. Cmd.exe vs. Command.com
  7. Commands Are Not Case Sensitive
  8. Starting Command Prompt and Running a Command
  9. Cmd.exe and Other Command Prompts
  10. Using AutoRun to Execute Commands When Command Prompt Starts
  11. Using Cmds Command-Line Syntax
  12. Using Commands
  13. Type /? for help
  14. Starting Programs
  15. Open Windows Explorer at the current Command Prompt folder
  16. Using File-Name and Folder-Name Completion
  17. Use a different completion character
  18. Using Wildcards
  19. Editing the Command Line
  20. Using Command Symbols
  21. The Redirection Symbols
  22. The Pipe Symbol
  23. The Command Combination Symbols
  24. Pausing or Canceling Commands
  25. Simplifying Command Entry with Doskey Macros
  26. DOSKEY Saves Typing
  27. System Variables Identify the Environment
  28. Viewing Environment Variables
  29. Modifying Environment Variables
  30. Predefined Environment Variables
  31. Customizing Command Prompt Windows
  32. Setting the Window Size and Position
  33. Setting the Window Size and Position Visually
  34. Selecting a Font
  35. Setting Colors
  36. Setting Other Options
  37. Copy and paste in the command prompt window
  38. Navigating from the command prompt
  39. Printing a list of filenames
  40. Commands Use Paths
  41. Identifying Executables
  42. Modifying the Path to Executables
  43. Modifying the Path with the GUI
  44. Changing the Current Path with CD
  45. Changing the Current Path with Windows Explorer
  46. Capturing the Output
  47. A Sampling of Commands
  48. Dir
  49. Copy
  50. XCopy
  51. SET
  52. NET USE
  53. SystemInfo
  54. DriverQuery
  55. Echo
  56. Advanced Shell Commands
  57. Creating a Batch File
  58. Scheduling a Batch File
  59. Creating Scheduled Tasks with a Script
  60. Using Windows PowerShell and the PowerShell ISE
  61. Windows PowerShell ISE
  62. PowerShell Commands
  63. Verbs and Nouns
  64. Sending Output to a Text File
  65. PowerShell Syntax
  66. Variables Created with a $ Symbol
  67. Comparison Operators
  68. Parentheses, Brackets, and Braces
  69. Running PowerShell Scripts
  70. PowerShell Execution Policy
  71. Changing the Execution Policy
  72. Looping
  73. Collections
  74. Creating a PowerShell Script
  75. Documenting Scripts
  76. Using PowerShell Commands
  77. Getting Help on PowerShell
  78. Using WMI_Cmdlets
  79. Getting Details on an Object
  80. Querying Information on Specific Objects
  81. Terminate Applications with Win32_process
  82. Formatting Output with the -f Format Operator
  83. Filtering the Output with the Where-Object Command
  84. Using the IF statement
  85. Using the Switch Statement
  86. Script Reusability