This happened with my library too but they fixed it a few updates ago, all I had to do was let the scheduled full scan run.