Visual Studio 2013/2015 Package Manager Console not initialized

Today I have installed Visual Studio 2015 and .Net 4.6 on my Win7 machine.

After starting Visual Studio 2013 and 2015, the Package Manager Console gives the following error:

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."

      

And nothing can be entered into the console.

I tried to change the policy but nothing changed. My current policy:

For x86 and x64

                         Scope                                             ExecutionPolicy
                         -----                                             ---------------
                 MachinePolicy                                                Unrestricted
                    UserPolicy                                                Unrestricted
                       Process                                                   Undefined
                   CurrentUser                                                   AllSigned
                  LocalMachine                                                   AllSigned

      

How can I fix this so I can use the Package Manager Console?

+3


source to share


2 answers


Hotfix available, download links available. They also become available this week in the Visual Studio Gallery



https://github.com/NuGet/Home/issues/974#issuecomment-124774650

+2


source


The workaround https://blog.nuget.org/20150720/nuget-3.0.0.html worked - temporarily - for me:

Delete the registry key at: HKEY_LOCAL_MACHINE \ SOFTWARE \ Policies \ Microsoft \ Windows \ PowerShell



The effect seems to be the same as Set-ExecutionPolicy Undefined -scope MachinePolicy

so it was a little invasive. Plus I think it got canceled the next time I opened the PowerShell console.

0


source







All Articles