VS2015 - The 'NuGetPackage' package did not load correctly

Just opened up VS 2015 Enterprise RTM, opened up an existing working project, getting the following error:


Microsoft Visual Studio


The 'NuGetPackage' package did not load correctly.

The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file C:\Users\REDACTED\AppData\Roaming\Microsoft\VisualStudio\14.0\ActivityLog.xml.

Restarting Visual Studio could help resolve this issue.

Continue to show this error message?


[Yes] [No]


Restarting didn't help. I've examined the log file, and found the following sections relevant to nuget:

<entry>
  <record>555</record>
  <time>2015/07/20 16:06:34.364</time>
  <type>Error</type>
  <source>Extension Manager</source>
  <description>Extension will not be loaded because an extension with the same ID 
     &apos;Microsoft.Dev14.VsixTemplatesPackage.443cca91-ec20-41e5-a165-f28e56b89650&apos; 
     is already loaded at C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 14.0\COMMON7\IDE\
     EXTENSIONS\G2URSPAC.VAZ\...</description>
  <path>C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 14.0\COMMON7\IDE\EXTENSIONS\
     NUGETIFIEDEXTENSIBILITYTEMPLATES\</path>
</entry>
<entry>
  <record>556</record>
  <time>2015/07/20 16:06:34.364</time>
  <type>Error</type>
  <source>Extension Manager</source>
  <description>Extension will not be loaded because an extension with the same ID
     &apos;Microsoft.VisualStudio.TeamFoundation.TeamExplorer.Extensions&apos; is already
     loaded at C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 14.0\COMMON7\IDE\EXTENSIONS\
     B1NUOYPH.H2N\...</description>
  <path>C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 14.0\COMMON7\IDE\COMMONEXTENSIONS\
     MICROSOFT\TEAMFOUNDATION\TEAM EXPLORER\</path>
</entry>

Which would suggest a duplicate extension, but this doesn't seem to be the case in the extensions manager.

This is on a machine that also has VS2013 installed. It has not had any of the preview/RC builds of VS2015 installed ever.


Completely removing NuGet via Extensions and Updates, restarting VS then re-installing NuGet via Extensions and Updates solved the issue for me. A full VS reinstall was not necessary.


Updating Nuget to the latest version seems to have solved the problem.

  1. Tools > Extensions and Updates

  2. Updates > Visual Studio Gallery

  3. Click Update on the Nuget Package Manager option


After a completely clean install of Visual Studio Professional 2015 from the MSDN Website, I ran VS2015 as Administrator, opened up the Package Manager Console from Tools -> NuGet Package Manager... -> Package Manager Console and I received this 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"

By following the above steps to

1) Use Tools -> Extensions and Updates... to uninstall NuGet Package Manager for Visual Studio 2015.

2) Restart Visual Studio.

3) Use Tools -> Extensions and Updates... to re-install NuGet Package Manager for Visual Studio 2015.

4) Restart Visual Studio.

Now when I open up the Package Manager Console, Powershell loads correctly and every thing is good. Thanks so much for this!


Bear in mind

A reinstall of the NuGet Package Manager does NOT seem to remove the existing NuGet.Config file held in c:\users\name\AppData\Roaming\NuGet!

Mine had a missing 'packageSources' section (why, I don't know) but since this file was not recreated NuGet still didn't work!

So either manually enter this section or remove this config file, then reinstall NuGet through the Extensions and Updates which will recreate a brand new one!


Deleting all the files from this folder C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\imf5jbeu.eak seem to have worked for me.