I don't recall this being reported again, or a solution being mentioned, so (as above) you should email support with a description of the problem and maybe a link to this topic.