Due to the override, your shell will retain its current effective execution policy of Restricted.

When I ran that command, it returned: Scope ExecutionPolicy MachinePolicy Undefined UserPolicy Undefined Process Undefined CurrentUser Restricted LocalMachine Unrestricted PowerShell contains multiple scopes.

But ifa more specific scope is configured, that scopes execution policy wins.

Fix Windows PowerShell setting is overridden To fix Windows PowerShell setting is overridden, I had to set the ExecutionPolicy of the CurrentUser to Unrestricted (or Undefined).

To do so, run this cmdlet in Powershell: Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope CurrentUser or Set-ExecutionPolicy -ExecutionPolicy Undefined -Scope CurrentUser Problem solved.

Error Windows PowerShell updated your execution policy successfully, but the setting is overridden by a policy defined at a more specific scope didnt show up anymore.

For example: Set-ExecutionPolicy -ExecutionPolicy Undefined -Scope Process A final note about winning policies The most specific scope wins, but it also overrides the less specific scope.

In NTFS, a combination of Deny Access on a user, and Allow Access to a group, will result in a Deny.

In Powershells execution policy, a combination of CurrentUser Unrestricted, and LocalMachine Restricted, will result in an Unrestricted policy.

The default setting of ExecutionPolicies is Undefined for all, except for LocalMachine.

Which can then lead to other errors as I described in a previous post Setting the LocalMachine policy only would be my advice.

Powershell Set Execution Policy