Set-ExecutionPolicy : Windows PowerShell updated your execution policy successfully, but the setting is overridden by a policy defined at a more specific scope!!!

  • Article

You have reached to this blog post probably after hitting into the below issue on executing:

Set-ExecutionPolicy "RemoteSigned"

 

Error thrown may be as follows:

Set-ExecutionPolicy : Windows PowerShell updated your execution policy successfully, but the setting is overridden by a policy defined at a more specific scope. Due to the override, your shell will retain its current effective execution policy of "Unrestricted". Type "Get-ExecutionPolicy -List" to view your execution policy settings. For more information, please see "Get-Help Set-ExecutionPolicy.

"Set-ExecutionPolicy" cmdlet is used for changing the user preference for the Windows PowerShell execution policy. details can be found here.

If the current logged-in user is an administrator on the system with proper access but still getting the above issue, following blogpost instruction may be helpful in re-setting group policy.

However, if the issue persists and "Get-ExecutionPolicy -List" command shows something similar as shown below:

    MachinePolicy = RemoteSigned
    UserPolicy       = Undefined
    CurrentUser = Unrestricted
    LocalMachine  = RemoteSigned

Execute the below commands in powershell commandline as an administrator:

Set-ExecutionPolicy "RemoteSigned" -Scope Process -Confirm:$false

Set-ExecutionPolicy "RemoteSigned" -Scope CurrentUser -Confirm:$false

This will set the execution policy for the given scope.

On executing "Get-ExecutionPolicy -List", we should now see the below:

    MachinePolicy = RemoteSigned
    UserPolicy       = Undefined
    Process           = RemoteSigned
    CurrentUser     = RemoteSigned
    LocalMachine  = RemoteSigned

Comments

  • Anonymous
    November 28, 2012
    Thank you! This has been vexing me for about an hour before I finally Googled it. Came right to this page.

  • Anonymous
    April 09, 2014
    Thanks , it came as a reliever to me , had been struggling for last 30 mins

  • Anonymous
    May 20, 2014
    The comment has been removed

  • Anonymous
    July 01, 2014
    Wow, Much thanks, this has been a thorn in my side for days on end!

  • Anonymous
    January 19, 2015
    The comment has been removed

  • Anonymous
    February 18, 2015
    Olaf Engelke  - removing the reg entry worked for me.  Thank you so much!!

  • Anonymous
    May 10, 2015
    I cannot find the powershell reg key.

  • Anonymous
    August 25, 2015
    Removing the RegEntry worked for me. Thanks

  • Anonymous
    October 13, 2015
    This didn't work for me - but this fixed it: fiveesoft.wordpress.com/.../vs-2015-package-manager-console-failed