There was an issue with an earlier build which caused this, it might be the same problem?
The solution was to update again.
There was an issue with an earlier build which caused this, it might be the same problem?
The solution was to update again.