I installed VS2015 Update 2 and now nuget package manager does not find any packages outside of the \"Microsoft and .net\" package source. It looks like the nuget package so
I am using Visual Studio 2015 Update 2 and had the Original Poster's issue. My package source config file was not deleted but the nuget source was set to https://api.nuget.org/v3/index.json
. I had to manually open the config file and change the URL to http://api.nuget.org/v3/index.json
in order to get packages to appear. However, I got errors when attempting to download the package I needed. So finally I checked for updates, saw Visual Studio 2015 Update 3, installed it, and now I can finally see the packages, download and install them (using the http address - the https did not work)!
I tried both updating to vs2015 update 3 and changing from https:// to http:// but they did not fix the issue.
In my case it was a local folder permissions error but looked from the error message as a download error. When I looked deeper in the output window I could see it was a permission error.
In my setup vs2015 is running on windows 10 and it appears the cause was that some recent microsoft security update had changed security on my home folders so that visual studio could not create c:\users\myname.nuget\packages
Once I created c:\users\myname.nuget\packages and gave myself full control over that folder it worked.
Weirdly, although I changed the config to http, the download actually came via https. The download URL shows as http in tools\options\nuget package manager\package sources but the output window tells a different story.
After Upgrading Visual Studio 2015 in September 16, my NuGet.config had been renamed as NuGet_temp.config. I deleted the NuGet.config file and renamed the _temp version as NuGet.Config.
After that all of my packages are showing again.
I am on Visual Studio 2015 Community Update 3. I had this problem. What worked for me is: open the Nuget.config file, and change the https to http.
Open Visual Studio as administrator.
For me it was a genuine temporary network problem. IVe tried again a bit later, and the error disappeared.