On some machines (don't know why) the Package Manager splits the list of packages into multiple pages apparently without regard to the dialog size. In this case there is another package on the next page but given the free space there is no need to split it. The page numbers are not immediately obvious and the empty space meant some time was wasted looking for the missing package before they were noticed.
See attachment.
Comments: I've noticed that this has started happening to my solution as well. In my case, it's because my local packages directory has a whole bunch of packages that used to belong to the project, but which don't anymore. Clearing out the packages directory and then downloading them from scratch (e.g., during build) seems to have fixed it. Still, it would be nice to have it fixed in NuGet.
See attachment.
Comments: I've noticed that this has started happening to my solution as well. In my case, it's because my local packages directory has a whole bunch of packages that used to belong to the project, but which don't anymore. Clearing out the packages directory and then downloading them from scratch (e.g., during build) seems to have fixed it. Still, it would be nice to have it fixed in NuGet.