Microsoft has now acknowledged the issue, however, it says the problem was introduced by the update delivered back in May.