It seems as if this problem has been encountered by a number of people.

I suspect that MS rushed the deployment of the software?