Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security, Veeam & DevOps

  • Home
  • About
  • Advertise With US
  • Reviews
  • Tech News
  • Contact
  • Toggle search form

How to set the PowerShell Execution Policy via Windows Registry

Posted on 04/02/202017/08/2026 IT Expert By IT Expert No Comments on How to set the PowerShell Execution Policy via Windows Registry
  1. Home
  2. Windows Server
  3. How to set the PowerShell Execution Policy via Windows Registry
PowerShell

In this article, we will discuss “How to set the PowerShell Execution Policy via Windows Registry”. PowerShell is a cross-platform task automation and configuration management framework, consisting of a command-line shell and scripting language. Please see Determine the execution policy configured on Windows PC, and How to install and update PowerShell version 7 on Windows and Linux.

Unlike most shells, which accept and return text, PowerShell is built on top of the .NET Common Language Runtime (CLR), and accepts and returns. NET objects. PowerShell is configured to prevent the execution of PowerShell scripts on Windows systems by default.

To run commands, one of the following systems must be taken into consideration.

HKEY_CURRENT_USER\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell

Set the string value ExecutionPolicy to one of the following values:

  • Restricted
  • AllSigned
  • RemoteSigned
  • Unrestricted and
  • Undefined. 

To change the execution policy for the LocalMachine scope, Navigate to the path as shown below.

Execution Policy

Currently, no value is set and none is currently available. To set the string value ExecutionPolicy to one of the following values:

Moreover, Create a new string and enter any ExecutionPolicy value you desire as below. Restricted, AllSigned, RemoteSigned, Unrestricted, Undefined. 

Nonetheless, Create a new string and name it ExecutionPolicy. Now enter the desired value.

Screenshot of Windows Registry Editor showing the path to Microsoft PowerShell with the ExecutionPolicy value being set to 'Unrestricted'.

Press okay afterwards and that is all. Please see how to Mitigate Windows Print Spooler Remote Code Execution Vulnerability, and how to Prevent Automatic Driver Updates in Windows and Xen-Orchestra

FAQs on PowerShell Execution Policy

Is it possible to bypass the PowerShell execution policy for a specific script?

You can bypass the execution policy for a specific script by adding the -ExecutionPolicy Bypass parameter when running the script in the PowerShell command line.

How can I change the PowerShell execution policy on my system?

To change the PowerShell execution policy, open PowerShell as an administrator and use the Set-ExecutionPolicy cmdlet followed by the desired policy, such as RemoteSigned or Unrestricted.

What is the default execution policy in PowerShell, and how can I check it?

The default execution policy is typically set to Restricted. You can check the current execution policy by running the command Get-ExecutionPolicy in a PowerShell window.

Can I make changes to the execution policy permanently, or do they apply only for the current session?

Changes to the execution policy can be made permanently using the Set-ExecutionPolicy cmdlet with the -Scope parameter set to MachinePolicy. This ensures that the policy is applied globally and persists across sessions.

Furthermore, I hope you found this blog post on how to set the PowerShell Execution Policy via Windows Registry helpful. However, please let me know in the comment session if you have any questions.

5/5 - (1 vote)

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Windows Server Tags:change PowerShell execution policy Windows, configure PowerShell execution policy registry key, disable PowerShell execution policy registry, enable PowerShell scripts via registry, how to modify PowerShell policy in registry, How to set PowerShell execution policy via Windows Registry, PowerShell, PowerShell execution policy registry path, PowerShell registry execution policy bypass, PowerShell version 7, RegistryEditor, set execution policy machine level registry, set PowerShell execution policy registry, Windows 10, Windows Registry, Windows registry PowerShell script policy settings

Post navigation

Previous Post: How to set Execution Policy via Windows PowerShell
Next Post: How to set up System Insights on Windows Admin Center

Related Posts

  • Screenshot 2021 03 16 at 21.14.05
    Unable to locate the account: Fix call to DsGetDcNameWithAccount failed with return value 0x0000054B Windows Server
  • windows server 1
    In-place upgrade for Windows Server 2012 to Windows Server 2019 Windows Server
  • WindowsTerminalServerRDS
    Remove a Remote Desktop Service collection Windows Server
  • Disable and Enable USB in Windows
    Disable and Enable USB Usage for Certain Users in Windows Windows
  • Windows Deployment Services
    How to migrate WDS and MDT to a new Windows Server Windows Server
  • Explorer Error
    How to fix an attempt was made to reference a Token that does not exist Network | Monitoring

More Related Articles

Screenshot 2021 03 16 at 21.14.05 Unable to locate the account: Fix call to DsGetDcNameWithAccount failed with return value 0x0000054B Windows Server
windows server 1 In-place upgrade for Windows Server 2012 to Windows Server 2019 Windows Server
WindowsTerminalServerRDS Remove a Remote Desktop Service collection Windows Server
Disable and Enable USB in Windows Disable and Enable USB Usage for Certain Users in Windows Windows
Windows Deployment Services How to migrate WDS and MDT to a new Windows Server Windows Server
Explorer Error How to fix an attempt was made to reference a Token that does not exist Network | Monitoring

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • image 63
    What to do when your Remote Desktop Licensing Manager Server Crashes Windows
  • images copy
    How to clean packages lying around in Linux Linux
  • Hyper V Virtual Switch
    How to Create Hyper-V Virtual Switch Network | Monitoring
  • windows update 03
    How to automate Windows Update with PowerShell Scripts
  • exchange 2016 1
    Remove Microsoft Exchange Server: Using ADSIEdit Tool Network | Monitoring
  • Object First OOTBI Appliance Configuration
    How to Configure Object First OOTBI Appliance Backup
  • Troubleshooting Synology NAS Domain Join 2
    Synology NAS Domain Join: The Importance of DNS Configuration Reviews
  • picture1 101
    Can’t Sign In: Domain Unavailable & 169.254 IP Address Issue Windows Server

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,762 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2026 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.