That's a mistake by Microsoft, see for example our news from May 25th and June 21st. Microsoft has now released knowledge base article 902956 that describes this problem of theirs.