Don't quote me but it is my understanding this was a MS update issue. All was fine up until last Thursday and then they started to get this issue.

So I assume one of the MS updates buggered something up and MS released this fix which obviously fixed the issue.