

The short answer is I fixed VS2015 and VS2017 Package Manager Console errors by adding dependent assembly references for PowerShell, along with Version Information to the Visual Studio configuration files.

I tried several different suggestions that didn’t fix the issue, but when I tried the solution suggested in this discussion the Package Manager Console starting working. While searching Google I came across a number of different discussions where users were experiencing the same issue. Since this was a newer version of Windows I didn’t believe that was the issue.

There are known bugs with Visual Studio 2015 and PowerShell running on earlier versions of Windows 10 see here. It was a brand new Windows 10 machine running build 3 version 1607. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. The term 'Set-Location' is not recognized as the name of a cmdlet, function, script file, or operable program. The term 'Get-ExecutionPolicy' is not recognized as the name of a cmdlet, function, script file, or operable program.

The following error occurred while loading the extended type data file:, C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(3035) : Error in type "": Exception: The getter method should be public, non void, static, and have one parameter of type PSObject. The following error occurred while loading the extended type data file:, C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(3028) : Error in type "": Exception: The getter method should be public, non void, static, and have one parameter of type PSObject. The following error occurred while loading the extended type data file:, C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(3021) : Error in type "": Exception: The getter method should be public, non void, static, and have one parameter of type PSObject. The following error occurred while loading the extended type data file:, C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(3014) : Error in type "": Exception: The getter method should be public, non void, static, and have one parameter of type PSObject. The following error occurred while loading the extended type data file:, C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(3007) : Error in type "": Exception: The getter method should be public, non void, static, and have one parameter of type PSObject. These are the errors that were being display on the console: I assisted a co-worker today with an issue where the Package Manager Console would not start in Visual Studio 2015 or Visual Studio 2017.
