It seems that the nuget used by the nuget packager is not the last. After testing locally with the latest nuget.exe, everything worked, so I added a new powershell release step. This solution is suitable for VSTS, for TFS, where you have access to the server, I recommend updating nuget.exe on the server itself:

This script loads the nuget.exe file into the artifact directory (and displays the path to the nuget.exe file so you can see where it is placed.).
Then I changed the build step of Nuget Packager to use the just downloaded nuget.exe file. 
source share