Powershell execution setting is overridden by a policy

Question

Boopathi S 3,736

Hi,
I am getting the below message when i run any powershell command. Please let me know which policy is blocking to run the powershell command

Hamdou Rabi Wane 5 Reputation points

2024-01-31T19:33:23.39+00:00

I am still having issue with this
Sachith Lakmal 126 Reputation points

2024-01-31T19:43:18.6166667+00:00
Try below steps. Open Group Policy Editor: Press Win + R, type gpedit.msc, and press Enter to open the Local Group Policy Editor. Navigate to Execution Policy Settings:

Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell.

Look for settings related to "Turn on Script Execution" or "Execution Policy". Adjust Policy: Double-click on the appropriate policy setting and adjust it to a less restrictive setting (e.g., "Allow all scripts"). Apply Changes: After modifying the policy, close the Group Policy Editor and run gpupdate /force in an elevated Command Prompt to apply the changes immediately.
Andrej Nikolov 0 Reputation points

2024-02-22T15:00:10.32+00:00

in my case, i wanted to run a powershell from microsoft. but it didn't work. after hours of research, i simply copied the content from the script and pasted it onto an empty .txt file and then converted it into a .ps1 script. i also deleted the signature at the end of the script

3 answers

Hamdou Rabi Wane 5 Reputation points

2024-01-31T19:33:23.39+00:00

I am still having issue with this
Sachith Lakmal 126 Reputation points

2024-01-31T19:43:18.6166667+00:00

Try below steps. Open Group Policy Editor: Press Win + R, type gpedit.msc, and press Enter to open the Local Group Policy Editor. Navigate to Execution Policy Settings:

Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell.

Look for settings related to "Turn on Script Execution" or "Execution Policy". Adjust Policy: Double-click on the appropriate policy setting and adjust it to a less restrictive setting (e.g., "Allow all scripts"). Apply Changes: After modifying the policy, close the Group Policy Editor and run gpupdate /force in an elevated Command Prompt to apply the changes immediately.
Andrej Nikolov 0 Reputation points

2024-02-22T15:00:10.32+00:00

in my case, i wanted to run a powershell from microsoft. but it didn't work. after hours of research, i simply copied the content from the script and pasted it onto an empty .txt file and then converted it into a .ps1 script. i also deleted the signature at the end of the script

Answer 1

SUNOJ KUMAR YELURU 15,006 MVP

You must set the PowerShell Execution Policy from Restricted to RemoteSigned or Unrestricted to allow local PowerShell scripts to run.

For more information about PowerShell Execution Policy, type help about_signing or help Set-ExecutionPolicy at the PowerShell command prompt.

Procedure

Select Start > All Programs > Windows PowerShell version > Windows PowerShell.
Type Set-ExecutionPolicy RemoteSigned to set the policy to RemoteSigned.
Type Set-ExecutionPolicy Unrestricted to set the policy to Unrestricted.
Type Get-ExecutionPolicy to verify the current settings for the execution policy.
Type Exit.

If the Answer is helpful, please click Accept Answer and up-vote, this can be beneficial to other community members.

Rich Matheisen 47,766 Reputation points

2021-08-10T15:09:41.393+00:00

Your example only changes the LocalMachine policy. The MachinePolicy supersedes that (as it does when the scope was "Process").
Zarate, Martin 5 Reputation points

2025-01-08T17:52:24.44+00:00

It is disappointing that this is the "most helpful" answer because it is very wrong in ways that are trivially visible from the post.

The MachinePolicy shown as "AllSigned" and the user has already set an execution policy demonstrating that they cannot override the MachinePolicy. Even a cursory reading of the user's actual question would've made that clear.

Answer 2

Rich Matheisen 47,766

Execution policies are hierarchical. See here: about_execution_policies or "help about_Execution_Policies"

Your "MachinePolicy" is "AllSigned". That takes precedence over "Process".

Answer 3

Boopathi S 3,736

Hello RichMatheisen and Learn2Skills,

Thank your for your help. I changed the registry settings as per below command and it worked.

Set-ItemProperty -Path HKLM:\Software\Policies\Microsoft\Windows\PowerShell -Name ExecutionPolicy -Value ByPass