The problem you are describing has been resolved in the 453 build. You should have been notified about a new update being ready for you.
After updating, if the problem still persist, please read up on the bug-report I linked to and try the workarounds mentioned in the comments by Lummox JR.
Then come back here and report your findings.