the beta build is 1485.

the build of latest retail release is 1483. so in 2 builds they would have corrected this problem? unlikely.

this problem persists since earliest of version 7. this problem was not corrected with a major version release, from 7 to 8. why would it be ever corrected in 2 builds after the latest retail release? unlikely.

the most important thing. did you try to change any of those actions?