Thanks for checking into this Matt. I think there is a good chance that the issue started with Build 458, as I'm certain that this wasn't the case before the update.