What does this Package Manager Console Message mean?
-
I'm getting this message, and the console window won't let me type any commands. I checked the execution policy and they're all set to "RemoteSigned". The admin tried running VS as admin and he gets it too. I do not have and cannot get admin rights on the box.
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 RemoteSigned. Type "Get-ExecutionPolicy -List" to view your execution policy settings. For more information please see "Get-Help Set-ExecutionPolicy".".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
I'm getting this message, and the console window won't let me type any commands. I checked the execution policy and they're all set to "RemoteSigned". The admin tried running VS as admin and he gets it too. I do not have and cannot get admin rights on the box.
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 RemoteSigned. Type "Get-ExecutionPolicy -List" to view your execution policy settings. For more information please see "Get-Help Set-ExecutionPolicy".".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Sounds like it's being overridden by Group Policy.
Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Windows Powershell
Turn on Script Execution = ...Issues With Configuring Powershell ExecutionPolicy via Group Policy[^] Set-ExecutionPolicy : Windows PowerShell updated your execution policy successfully, but the setting is overridden by a policy defined at a more specific scope!!! – Paresh's blog[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
"These people looked deep within my soul and assigned me a number based on the order in which I joined" - Homer
-
Sounds like it's being overridden by Group Policy.
Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Windows Powershell
Turn on Script Execution = ...Issues With Configuring Powershell ExecutionPolicy via Group Policy[^] Set-ExecutionPolicy : Windows PowerShell updated your execution policy successfully, but the setting is overridden by a policy defined at a more specific scope!!! – Paresh's blog[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
It seems that the IT idiots propagated a new group policy across the DoD that (I assume) turns off all ability to execute powershell scripts (among other pointless changes).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Sounds like it's being overridden by Group Policy.
Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Windows Powershell
Turn on Script Execution = ...Issues With Configuring Powershell ExecutionPolicy via Group Policy[^] Set-ExecutionPolicy : Windows PowerShell updated your execution policy successfully, but the setting is overridden by a policy defined at a more specific scope!!! – Paresh's blog[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Richard Deeming wrote:
Sounds like it's being overridden by Group Policy.
ExecutionPolicy in registry is set to "RemoteSigned". When my admin runs the tool to change the local policy, he set all five(?) of the execution policies to "RemoteSigned". I can understand that even though the registry policy is the same , it thinks, "Hey I have a policy set in the registry, so it must be an override of whatever is set locally" (without actually checking to see what the override is), so it displays that message. But WHY does it preclude me from doing anything in the console window after the message is displayed?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Richard Deeming wrote:
Sounds like it's being overridden by Group Policy.
ExecutionPolicy in registry is set to "RemoteSigned". When my admin runs the tool to change the local policy, he set all five(?) of the execution policies to "RemoteSigned". I can understand that even though the registry policy is the same , it thinks, "Hey I have a policy set in the registry, so it must be an override of whatever is set locally" (without actually checking to see what the override is), so it displays that message. But WHY does it preclude me from doing anything in the console window after the message is displayed?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Not sure, but you're not the only one: Visual Studio Extension appears to fail to run PowerShell if execution policy set in GPO, 2.8.6 and 3.0 · Issue #974 · NuGet/Home · GitHub[^] Towards the bottom, there's a link to a NuGet hotfix (v3.1.1 for VS2015; v2.8.7 for VS2013) which is supposed to solve the problem.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
