Putting this as an answer so that others can find it, although you seem to have found the answer yourself. I went through this problem, so I understand your problem.
Close all instances of Visual Studio first. This is generally a good idea when you do something outside of VS that will affect what VS thinks.
As you saw, you need to use the nuget command line version to clear the cache. Your first problem is to find this, as it is not obvious. The second problem (if you are looking for it) is that you will find many of them: one in the .nuget folder in each solution.
The easiest way to get around this is to download the latest version of nuget.exe from your website. Keep it somewhere away from any projects if you need it.
At this point, you wonβt be able to run the command to clear the cache, since you need to update nuget first. I agree that this seems strange given that you just downloaded the latest version, but you will need to do the following ...
nuget update -self
Once you do this, you can clear the cache as jessehouwing pointed out ...
nuget.exe locals all -clear
The next time you start Visual Studio, you should find that everything is working as expected. You may need to uninstall and reinstall the packages so that they all work, but with a cleared cache that should work without problems.
Hope everything is clear.
Avrohom Yisroel
source share