I have not seen this issue reported before, and after checking, neither has QA. Hopefully it was just a weird glitch that reinstalling will have cleared up.