This was corrected in an update released last night, please ensure you have the most current update installed, and you should no longer see this issue occurring.  (I'm doing the same now to confirm)